Live supply
—
Solana · Token-2022
A token that rewrites its own name as it is destroyed.
MOLT is one Token-2022 mint with its metadata stored inside itself. Every 100,000 tokens destroyed, it rewrites its own name, ticker and artwork on chain. Burn them from any wallet or any app — the mint only reads its own supply. Ten thousand names, none of them editable.
Specimen · live
reading chain…
—
—
Destroyed
—
Instar written
—
Shell
—
The mechanic
Three moving parts, all of them on chain.
Nothing here is a website feature. The name a wallet shows you is a field inside the mint account, and the only thing that can write to it is a program that first divides the destroyed supply by 100,000.
01
Metadata lives in the mint
The mint carries the MetadataPointer and TokenMetadata extensions and points at itself. Name, symbol and URI are fields in the account, not rows in a registry, so a wallet reads the new name the moment it changes.
ExtensionType::TokenMetadata
02
Burning is the only input
The mint authority was destroyed in the launch transaction, so supply can never rise. The program reads that one number and nothing else, which is why it does not care whose tokens burned, in which wallet, or through which app.
instar = burned / 100,000
03
The shell program holds the pen
Metadata update authority sits with a program PDA. Its one writing instruction recomputes the burn, refuses anything that is not due, and then writes the instar it has earned. There is no instruction that accepts a free-text name.
shell PDA · update_field
The rule
One number decides everything.
There are no percentage tiers and no schedule. Divide the tokens destroyed so far by one hundred thousand; that integer is the instar, and it is the name. Burn a million at once and the mint jumps ten instars in a single crank.
Tokens burned per name
100,000
Every 100,000 MOLT destroyed, the mint writes a new name into itself. 1,000,000,000 supply means up to 10,000 names.
instar = floor(burned / 100000)
Burn it anywhere
Your wallet, a trading bot, a router that burns on your behalf, a treasury, a stranger. The program never looks at who signed or where the tokens sat. It reads mint.supply, subtracts, divides.
A real burn, though
Only an actual burn instruction reduces supply. Sending tokens to a dead address moves them without destroying them, so it moves nothing here. If the supply number did not fall, no instar was earned.
The shell counts decades
Six rings cannot show ten thousand states, so a ring is an order of magnitude: one grows at instar 1, the next at 10, then 100, 1,000, 5,000 and 10,000. The numeral on the token image carries the exact count.
On chain
Read it yourself.
Everything below is fetched from a Solana RPC node in your browser and parsed out of the raw mint account. The right column is the byte-level state of the metadata extension right now.
Console
Destroy supply. Push the shell.
A burn is an ordinary Token-2022 burn from your own account, signed by you. Nothing is sent to a treasury and there is nothing to approve. Every 100,000 destroyed, from anywhere, earns one rename that anyone can crank.
Your position
1%5%
25%max
Connect wallet
Wallet not connected.
The crank
Nothing is due
When the cumulative burn crosses the next 100,000, this button sends the permissionless shed instruction. The transaction costs a fee and pays a few thousand lamports of rent, and gives the caller nothing but the rename.
Burning is irreversible. Tokens you burn are gone; you are buying a stage change with them, nothing else.
FAQ