Ikuzo行くぞ

Trading fees, divided among the people holding the token.

Ikuzo is a token launched on the pons launchpad on Robinhood Chain. Every trade pays a creator fee in ETH, and those fees are divided among the people still holding at the end of each cycle.

Two rules decide it. Who: an address is paid for a cycle only if it still holds when the cycle closes and never reduced its position during it. Holding flat qualifies, buying more qualifies, selling any part does not — and the share of everyone who sold is divided among those who did not, rather than carried forward. How much: among those who qualify, the split is by average balance across several snapshots taken at times nobody knows in advance, so what counts is how much of the cycle an address actually held for, not what it held at one guessable moment.

When a cycle settles, every balance, every share and every payment is published together with a hash of the whole calculation, and any of it can be recomputed from those published inputs in your own browser.

Snapshots are taken about every thirty minutes and cycles settle about every six hours, each at a moment drawn at random inside its window and never announced. The rhythm is public; the clock is not. If the times were known, holding across a dozen known instants would beat holding at all — which is the behaviour the averaging exists to remove.

Claiming is automatic, and worth understanding rather than taking on trust. pons credits creator fees to an escrow whose claim function pays whoever calls it — so the key that claims can pull that credit into the treasury it already controls, and nowhere else. It cannot redirect the fee stream, name a different recipient, or reach anything but its own balance. That is the whole of what automating it grants.

What it costs is that a key which can move money now runs on a server. The exposure is bounded on purpose: a settlement is refused outright if it would distribute more than a published ceiling, if the cycle has too few snapshots, or if any snapshot failed the check that every token is accounted for. Those limits live in the same config row the payouts are computed from, so they are as checkable as everything else here.

token0x616acb71b9ff11d99ffc9abc4fb7ce8ff7c47075explorer
distributed to date1.035274ETHread 2026-09-19 05:56 UTC · 4h ago
fees awaiting claim0.068424ETHread 2026-09-19 10:04 UTC · 15s ago
holders, last snapshot298read 2026-09-19 09:47 UTC · 17m ago
cycles settled1read 2026-09-19 05:56 UTC · 4h ago

“Distributed to date” counts only payments confirmed on chain, summed from the payout rows themselves. “Fees awaiting claim” is read live from the pons escrow: it has accrued but has not been pulled into the treasury yet, so it is real money that no cycle can divide until it is claimed — which now happens automatically, ahead of each settlement. “Holders” is the count in the most recent snapshot, which is a moment, not a running total.

A cycle is opened by the first snapshot and closed when the operator settles it.

cycle #2 open
opened
2026-09-19 05:56 UTC
snapshots taken
7
dust carried in from the last cycle
0.000026 ETH
held in the treasury right now
0.009831 ETH
share of fees that goes to holders
100.00%
read 2026-09-19 10:04 UTC · 15s ago
snapshotblocktakenholdershash
#19668814102026-09-19 06:52 UTC310890bd156b220413a
#20668957982026-09-19 07:15 UTC307917b5d2860529877
#21669171622026-09-19 07:52 UTC299361c0f4f4091b914
#22669408582026-09-19 08:31 UTC294cb98791ed88b7518
#23669543822026-09-19 08:54 UTC296390bd65758cca8f3
#24669671812026-09-19 09:15 UTC292229f2a98cf332263
#25669866202026-09-19 09:47 UTC298d3f6654670e0fdf4

The treasury is 0x48b4f953fa38c63f55eea1d4d3b067f40136017c. It holds nothing but Ikuzo money, which is what makes the pot measurable as a plain balance.

Every snapshot and every settlement, as it was written down.

snapshot

cycle 2: snapshot 25 at block 66986620, 298 holders (1238 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 5 excluded), hash d3f6654670e0fdf4f42719fd06ce2bf9b2b12b6a094bea9dca44cce6be537fc4

snapshot

cycle 2: snapshot 24 at block 66967181, 292 holders (1231 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 5 excluded), hash 229f2a98cf332263eaa0c5d7e921f0385e9e2481fecc3f34f2e3c75c4ecf4960

snapshot

cycle 2: snapshot 23 at block 66954382, 296 holders (299 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 3 excluded), hash 390bd65758cca8f3076168005b5f8beb6e8cfbdb8f7cc6d803ac8cd3e5aa080f

snapshot

cycle 2: snapshot 22 at block 66940858, 294 holders (1225 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 5 excluded), hash cb98791ed88b7518c334f55f9efabc23a4e0550b4efe7d5ef7ed9ebe440d0819

snapshot

cycle 2: snapshot 21 at block 66917162, 299 holders (303 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 4 excluded), hash 361c0f4f4091b9142557aae93e0d6ab49e84e0a08a79b1aab7c0d35c5b94f7e3

snapshot

cycle 2: snapshot 20 at block 66895798, 307 holders (1219 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 5 excluded), hash 917b5d28605298772c7805d74f1a38375e0f75c1e9fed70b36ebce395e2801cc

snapshot

cycle 2: snapshot 19 at block 66881410, 310 holders (314 candidates from union(blockscout(https://api.blockscout.com, chain 4663) + transfer-logs(from 66553501)), 4 excluded), hash 890bd156b220413a18bda8dcad22db4b24c04dd77f0bea351338162cf25d937a

feed

cycle 1 settled: fees-in 1035300917178669254, dust-in 0, gas-reserve 10000000000000000, pot 1035300917178669254, retained 0, allocated 1035274406041445387, dust-out 26511137223867, proof 7e9e571ba1c249db20ee32fa4043204daf7e133a830d1096cff99a58c77b03d7