🔥Burn Addresses

These are all the BlockBurns public Burn Addresses in list form. Note that these addresses might not appear on external services such as DexScreener as Burn Addresses yet.

EVM Burn Addresses

Blockchain	Address
Ethereum (ERC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Binance Smart Chain (BRC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Polygon (Matic)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Avalanche (ERC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Arbitrum (ERC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Optimism (ERC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
Fantom (ERC20)	0xd60774160Ff8Acd95057aab6490c1a35E48195c8
All Other Chains (EVM)*	0xd60774160Ff8Acd95057aab6490c1a35E48195c8

*You may use the same Ethereum Burn Address for all EVM-based Blockchains.

If you require an address that is marked on all external services by default as an ERC20/EVM Burn Address please use the Public Null Address: 0x000000000000000000000000000000000000dEaD

Other Burn Addresses

Blockchain	Address
Bitcoin (BRC20) (Native Segwit)	bc1qyyp263aaqjar4ydae2krn4qg4j2dnwsssee6an
Tron (TRC20)	TMerfyf1KwvKeszfVoLH3PEJH52fC2DENq
Cardano	addr1q9ru0840w7q7wnrgsdl8mnjk5rttnxnjapp224z3cqu8qlk04ecllemn02u4zf4u2ww73c0aq6ycjhy8ysk364xvlvtqsl6wa0
Solana	DyYVwW4rRwNf5QgRF2gMXBfWgqcW6yjWET8kLMabsHHN
Polkadot	5ECn2EnyqTjgaqPW8pXRnJTpufQAhoi8vdni7PuNM1kyT1Lc
Cosmos (Cosmos Hub)	cosmos1syc7ymc9v3umrwseaqzpg95vv6gw20j2pls2mu
Aptos	0x634166b91829f78bedd71aaeccc56f179a8451c43ebbfa4aff7207af95051f58
Sui	0x9716a65b4ed415a043aa2b927fa73bcee0ecd2426b4f360fc05a9c0a0413b356

---

If you are a project developer you might want to consider using the Burn feature programmatically that is built into the given Blockchain (assuming it exists) instead of sending to an address. This option is not available for normal users.

---

Whitelisted Addresses

One of the advantages (in addition to added functionality and ease of use) of using our Burn Addresses is that in some justified scenarios relaying is possible to select Whitelisted Addresses:

• Origin Address

• Dominant Burn Address

Reasons might include: obvious mistakes, preferred programmatic burning, or lack of third-party support.