Who burned it
The signer of the transaction and the owner of the token account. Only the owner can authorise a burn, so the signature names them.
Issue No. 1 Receipts for the irreversible
Ashstamp burns tokens from your own wallet with Solana's checked burn instruction, writes a memo into the same transaction, and prints a certificate from what the chain recorded. Anyone can verify it from the signature alone.
I. What a receipt proves
The signer of the transaction and the owner of the token account. Only the owner can authorise a burn, so the signature names them.
The slot and block time the network finalised it in. A certificate is only issued once the transaction exists on mainnet.
The mint, the exact raw amount and the decimals, checked by the token program itself. Supply falls by the same amount in the same block.
II. The burn desk
Connect a wallet to see every token account it owns on mainnet, SPL Token and Token-2022 alike. Pick one, set the amount, read the review sheet, then sign in your own wallet. Ashstamp never touches the tokens; the token program destroys them.
No wallet connected.
Burning needs your own wallet's signature. Connect with the button at the top right, or open your sheet below.
III. The verifier
Any mainnet transaction that burns tokens, by anyone, with or without Ashstamp. The verifier reads it from the chain, finds every burn instruction (including ones run inside other programs), and engraves a certificate whose seal is the SHA-256 of what it found.
IV. Supply ledger
Give a mint. The ledger reads today's supply, walks the last 25 transactions that touched the mint, and rebuilds the supply line backwards through every burn and mint it finds. Then test a burn of your own size against it.
Plate II · supply line, newest on the right
Verify a burn above and its mint lands here, or paste any mint.
V. Anatomy of a burn
15, the raw amount as eight little-endian bytes, then the decimals the program must match.Built live with a fresh blockhash.
VI. Your album
The album reads the last 25 transactions of a wallet and keeps the ones where it burned tokens. Each one opens as a certificate. Works for your connected wallet or any address you paste.
VII. Procedure
getTokenAccountsByOwner lists every SPL Token and Token-2022 account your wallet owns, with balances and decimals.
Your browser builds one legacy transaction: BurnChecked under the account's own token program, plus a signed memo. The fee is quoted with getFeeForMessage.
Your wallet shows the transaction and asks you. Ashstamp only ever holds the unsigned bytes and your public key.
getSignatureStatuses is polled until the burn is confirmed, then the verifier reads it back and engraves the certificate.
VIII. Questions
No. The token program subtracts the amount from your account and from the mint's supply. There is no recovery path, which is why the review sheet asks you to confirm.
Never. A burn does not move tokens to an address; it destroys them. The only cost is the network fee, paid from your wallet to the network.
BurnChecked carries the mint's decimals, and the token program rejects the transaction if they do not match. It protects you from burning a thousand times more than you meant.
Yes. Ashstamp uses the program that owns your token account, so Token-2022 accounts are burned by the Token-2022 program and classic accounts by the SPL Token program.
No. It is an image generated in your browser from the transaction. Its proof is the signature: anyone can paste it here, or into any explorer, and see the same burn.
Burning everything leaves an empty token account that still holds its rent deposit. You can close it later from your wallet to get that SOL back.