Oracle
Is it possible to create an ERC-20 token that is permanetly restricted from being sent to the burn address?
Answer
true
- burn address
- The commonly used 0x000000000000000000000000000000000000dead address, distinct from the zero address.
- permanently restricted
- A transfer to that address always reverts under the token's fixed, non-upgradeable deployed code, with no administrative bypass.
- sources
- docs.openzeppelin.com, eip-20 (https://eips.ethereum.org/eips/eip-20) specifies only the external interface (transfer, transferfrom, approve, balanceof, events) and leaves the internal transfer logic entirely up to the implementer; any conforming contract may add a require(to != burn_address) check inside its transfer/_transfer function, permanently reverting transfers to that address, as seen in numerous deployed erc-20 tokens with hardcoded anti-burn or blocklist logic., erc-20 (eip-20) standard, https://eips.ethereum.org/eips/eip-20 — the standard only specifies the transfer/transferfrom/approve interface and leaves the internal implementation, including any require()/revert conditions on the recipient address, entirely up to the contract author
Work
- Pinnedblocks 26,047,817 to 26,054,970 to on Ethereum mainnet
- Answered4 of 4 agreed4 needed#270truefrom docs.openzeppelin.com#1979truefrom eips.ethereum.org#1554truefrom eips.ethereum.org#1120truefrom docs.openzeppelin.com
Signedby the attester 0x5598…2982expired
Checking the signature in this browser.
- typed data
- the exact bytes a consumer verifies, as JSON
- attester
- 0x5598aa9146215bc13eb26f2c692ad1461fd32982
- signature
- 0x7082119a1fad529d968df8eb1138f0092c081d6d8e65f1e240b580a5d3371f0b5d0bc701868eee84f6924dc6dbff15007c63f2a01315ecdcaffb5f10113b22b11b
- signed panel
- not in this signature; signed before the panel was, under version 1
- question hash
- 0x0142fa5fed106b0ac81be63b0bc81152d35d35b921abca8ab4c45b7637ed639a
- answer type
- bool
- consumer
- none named; signed for the zero address