Burn tokens.
Once you sign, the supply is gone for good. Read the whole page first, because this is the one action on HoodLock with no way back.
Burning cannot be reversed. The tokens go to an address nobody holds the key to. There is no recovery, no support path and no admin override, because there is nobody to ask. Burn the amount you mean to burn.
Decide first#
Burning and locking answer different questions, and the choice is easier before you sign.
| Goal | Use |
|---|---|
| Remove supply permanently and prove it | burn |
| Show commitment but keep the option to migrate later | lock |
| Release supply gradually to people | vesting |
For LP positions specifically, burning vs locking liquidity lays out the trade-off. A burn needs no trust at all, while a lock keeps the option to move the pool.
Burn it#
- Open the burn form. Burning lives on the lock page. Go to the lock form, connect the wallet holding the tokens and tap the FOREVER · BURN chip under the unlock date. The heading changes to Burn forever and a warning takes the place of the date field. Tapping any duration preset switches the form back to locking.
- Pick the token. From your balances or by contract address.
- Enter the amount. The form shows how much of the total supply your wallet holds, not the share this burn removes. Work that share out before you sign, because it is the number people will quote. The proof page shows it afterwards.
- Read the confirmation. It states the amount, says the burn cannot be undone and shows the full dead address. This is the last point at which stopping costs nothing.
- Approve, then burn. Most wallets ask for two confirmations, some combine them into one, and if you already approved enough there is only the burn. The summary shows the HoodLock fee before you sign. The tokens move from your wallet straight to the dead address in a single transfer. They never sit in our contract.
- Share the proof link. The page states the amount, the share of supply and the transaction.
What gets recorded#
The registry writes who burned, which token, how much and when, and exposes a running total per token
through totalBurnedOf. That is the difference between burning through the registry and sending
tokens to the dead address yourself: both destroy the supply, but only one produces something a reader can
check without knowing how to read a block explorer.
Common mistakes#
- Burning the wrong token. Symbols repeat across contracts. Verify the address, not the ticker.
- Burning LP you did not mean to. Burning an LP token removes liquidity permanently, and the pool shrinks. That is sometimes the intent and sometimes a very expensive misunderstanding.
- Trying to burn LP that is no longer yours. If your LP was already locked or burned when the pool was set up, it is not in your wallet. You cannot burn a position you no longer hold, and you should not need to.
- Treating a burn as a substitute for distribution. Removing supply does not fix a concentrated holder list. The distribution is a separate question.
After burning#
Total supply drops by the burned amount, so every percentage derived from it shifts. If you publish tokenomics, update them. A burn that makes your own documentation wrong undercuts the point of doing it.
How to check if liquidity is burned shows what a reader will do with your claim.
Burn tokens
Permanent by construction, with a proof page and a transaction anyone can verify. Open the lock form and tap FOREVER · BURN.
Open the lock form →