Token burning.

Sending tokens to an address nobody holds the key to, with a permanent public record of it. Final from our side, though whether it truly reduces supply depends on the token.

Updated 2026-07-29 · HoodLock Team

What happens#

The burner moves tokens from your wallet to the dead address in a single transfer and writes a record: who burned, which token, how much, and when.

address
0x000000000000000000000000000000000000dEaD

The tokens never rest in the burner contract. There is no intermediate custody step where something could go wrong or where a privileged function could intervene — the transfer goes straight from you to an address nobody holds the key to.

Irreversible

We cannot undo this. There is no recovery, no support ticket and no admin override. The dead address has no owner, so there is no one to ask. Burn the amount you mean to burn.

What a burn does and does not prove#

This is the part worth reading carefully, because burning is routinely presented as stronger evidence than it is.

Careful

A transfer to the dead address does not reduce totalSupply. The tokens are parked at an unspendable address, not destroyed at the protocol level, so every "% of supply" figure still counts them in the denominator unless the token implements a real burn.

And the token decides whether they stay there. A mintable token can re-issue the same amount. An upgradeable token can add a function that moves the dead address's balance. Neither is visible from the burn record.

Careful

The recorded amount comes from the token itself. The registry measures the dead address's balance before and after, which means a token that reports whatever it likes can produce a burn record for far more than was actually sent. A burn of a token you did not verify is a claim, not proof.

Before treating any burn, including one shown to you — as supply reduction: check the token's contract address rather than its symbol, and check whether it is mintable or upgradeable. How to read a contract on Blockscout.

Why burn through a contract at all#

You could send tokens to the dead address yourself. The difference is the record.

Where the line falls#

A burn record establishesIt does not establish
That a transfer to the dead address happened, on a specific date, in a specific transactionThat totalSupply fell, unless the token burns rather than parks
That HoodLock cannot return those tokensThat the token cannot return them
That the burner gave up whatever they actually heldThat what they held was worth anything
An amount the token reportedThat the amount is true, if the token is not verified
Nothing about the remaining supplyNothing about the token contract or the team

On a verified, non-mintable, non-upgradeable token a burn is one of the strongest signals available — precisely because there is no way back. That qualifier is doing real work in that sentence, and it is why the checks above are worth the two minutes.

Burning versus locking liquidity#

For an LP position the two are genuinely different promises. A burn is permanent and needs no trust at all; a lock is temporary and keeps the option to migrate the pool later. Neither is strictly better — the comparison lays out when each fits.

Note

If you are considering burning LP to prove liquidity is permanent, check first whether your launchpad already did it at graduation. Several on this chain do, and you cannot burn a position you no longer control.

Cost#

A flat fee, currently 0.005 ETH, read live from the contract, plus gas. Overpayment is refunded. No percentage of the tokens. See fees.

Doing it#

Full steps in how to burn tokens. Two transactions: approve, then burn. The confirmation screen states the amount and the share of supply before you sign.

Burn tokens

A single hop to the dead address, with a proof page and a transaction anyone can check.

Open burn →