Everything here is read from Robinhood Chain. Protocol state from view calls against the deployed contracts, history from the hook’s Burned event logs. Nothing is estimated, smoothed, or backfilled. Fields that cannot be read yet show a dash rather than a zero, because “not deployed” and “nothing burned” are different statements.
supply
launch S(0)21,000,000
circulating—
burned R(t)—
burned share—
burn paths
via buys—
via sell buyback—
eth into buyback—
last event—
constants
β_in (buy)100 bps
β_out (sell)500 bps
asymmetry5.0×
lp fee—
venue
price (eth)—
ponzi per eth—
pool liquidity—
tick spacing—
realised supply, every burn eventon-chain
Read directly from the hook's
Burned event logs, which carrysupplyAfterin the payload — so each point is the token contract's own reported supply at that block, not a figure this site computed. Unsmoothed and uninterpolated. The line is a staircase because burn is discrete: it happens per swap, not per block.burn flow by originating pathon-chain
Each bar aggregates roughly one day of blocks (~7,200 on mainnet). Pink is Ponzi withheld from buy output and burned on the spot; violet is Ponzi acquired by the hook's buyback purchase — bought off the open book with ETH taken from sell proceeds — and then burned. The violet portion is the mechanism that makes selling into this pool generate bid rather than remove it.
reading logs…
The ledger is included because a claim about supply that cannot be audited line by line is a marketing claim. Every row links to the transaction that produced it, and every supplyAftervalue is the token contract’s own report at that block rather than a figure this site computed.
Continue reading/invariants»