I found solution with this address
0x000000000000000000000000000000000000dead
Answer from Руслан Миров on Stack OverflowWho can burn Base tokens?
It depends on the burn method and token implementation:
- Classic 0xdead burn - Any holder can burn their own tokens this way. It's just a standard ERC-20 transfer to the 0xdead address.
- Native burn() method - Also, almost always any holder can do it unless custom blockage was injected inside the burn method
The 20lab tool detects if burn method is available for your specific token and only allows native burn if it exists.
How do I burn Base tokens?
To burn Base tokens with 20lab:
- Connect the wallet holding the tokens you want to burn
- Enter the token's contract address
- Choose your burn method:
- Native burn() (recommended if available) - Properly reduces total supply
- Classic 0xdead burn - Sends to inaccessible address, works for any ERC-20 token
- Enter the amount to burn
- Confirm the transaction
The tool automatically detects which methods are available for your token. The action is irreversible and is recorded on the block explorer. Double-check the amount before confirming - there is no recovery for burned tokens.
Will burning Base tokens increase the token price?
Burning reduces supply, which can support price - but it's not automatic:
- Burns work best when paired with sustained demand - reducing supply with no buyers does little
- Large announced burns sometimes cause short-term price spikes from speculation
- Continuous fee-based burns create gradual long-term deflationary pressure that may compound over time
- Burning tokens already in the team treasury (vs. buying from market and burning) has weaker market impact - the supply was already inactive
Burns are most effective as part of a broader tokenomics strategy with utility, demand drivers, and clear communication. Burning alone rarely moves price meaningfully without those.
Videos
I found solution with this address
0x000000000000000000000000000000000000dead
I would suggest to
Crete a smart contract called
BurnerAny tokens send to this contract would be forwarded to 0x0 by the smart contract itself
Burner contract can also emit events that signal that token supply has been reduced and has a function
getCirculatingTokenSupply(), so that it is easier for the users to check how many tokens are out there
The internet suggests that in all EVM networks, it is customary to transfer tokens to the address 0x000000000000000000000000000000000000dEaD for burning.
However, dexscreener ignores this address; if tokens are transferred to it, it does not display a lock next to the liquidity. Yet, if LP tokens are transferred to 0x0000000000000000000000000000000000000000, it marks them as burned.
When I try to transfer tokens to 0x0000000000000000000000000000000000000000 in the Base network, MetaMask gives an error stating that it is not an Ethereum address. Can you please explain why this is the case and how to correctly burn LP tokens in Base?