Potatchi Burns

Our indexer reads every POTATCHI transfer straight from the Robinhood Chain node, waits 30 blocks before trusting one, rolls back if the chain reorganises, and publishes the result here. A burn shows Confirmed after those 30 blocks and Final once its block is final on Ethereum, which Robinhood Chain settles to, usually within about 15 minutes. Each burn links to its transaction on Blockscout, so you can check it yourself, and the burned total is checked against the drop in total supply.

Only the token’s own burn: a transfer to the zero address, which also lowers total supply. Tokens sent to a dead address still count in total supply, so they’re listed separately and never called burns. Every burn is identified by its transaction and log position, so none is counted twice.

A burn is scheduled when it comes from the commitment contract together with that contract’s own record of the installments it burned; the record labels the burn, it never adds a second one. Installment n becomes eligible 24 hours after installment n − 1, starting at the time fixed when the contract was deployed. Anyone can execute a due installment; late ones burn together; none can burn early. The time in the history is when a burn was executed; the time it became eligible is shown next to it.

Funded

The 100,000,000 arrived in the contract. Moving tokens in burned nothing.

Committed

Held by the contract, burnable only, not burned yet.

Eligible

An installment’s time has come. It waits for someone to execute it; a countdown reaching zero burns nothing.

Submitted

An execution was sent and isn’t confirmed yet.

Confirmed

Burned, and 30 blocks deep on Robinhood Chain. Only confirmed burns count in the totals.

Final

Its block is final on Ethereum.

The 20 levels are the contract’s own records of every fifth installment (LevelCleared). They show progress; the burned totals above are the numbers that count. The project’s keeper checks every 5 minutes, and anyone can also execute a due installment: it gives the caller nothing and costs them the network fee.

A burn is matched when it comes from the matching vault together with the vault’s own Burn + Match record in the same transaction; the record labels that burn, it never adds a second one. Putting tokens into the vault’s reserve is funding, not a burn. The vault has no owner and no way to send tokens anywhere except into the token’s own burn: no withdrawal, no rescue, no upgrade, no pause. Switching this page’s card off doesn’t stop anyone from calling the vault directly. With a wallet connected, the card reads the reserve straight from the vault before every burn and asks for an approval of exactly the amount you chose.

POTATCHI is the Pons launchpad’s standard token: no owner, no pause, no mint and no upgrade, and any holder can burn their own tokens. We rebuilt its published source: the executable code matches the code on chain.

The indexer runs every minute while its computer is awake. This page refreshes every minute while you’re looking, slows down if the data service doesn’t answer, and keeps the last good numbers with a clear Delayed label instead of showing zeros. Nothing is stored in your browser except, once you send a transaction from this page, its hash for this tab, so the page can follow it.