The smart contract changes — Ethereum Name Service
Who can replace the code or create new tokens, and do the documents describe it?
For Ethereum Name Service, the documents we archive answer none of the 3 questions that matter for this event.
What the contract shows
| In the code: Replace the code | Not found by our check | block 26454386, read 20 Nov 2026, 06:02 UTC |
| In the code: Create new tokens | mint(address,uint256) | block 26454386, read 20 Nov 2026, 06:02 UTC |
| In the code: Hand over control | transferOwnership(address) | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Contract code can be replaced (proxy) | Not detected by our standard checks | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Owner | 0xfe89cc7abb2c4183683ab71653c4cdc9b02d44b7 | block 26454386, read 20 Nov 2026, 06:02 UTC |
| Delay before changes — Owner | 2 days | block 26454386, read 20 Nov 2026, 06:02 UTC |
Contract and documents side by side
In the code: mint(address,uint256). The documents we archive do not answer “Issuing new tokens”. This needs an explanation, not a conclusion.
Readings of who controls the contract changed 1 times since AsOf began reading them; last change seen 1 Nov 2026. See the passport.
What stays unknown
Questions about Ethereum Name Service
Can the ENS smart contract be changed?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.
Who can create new ENS tokens?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.
Can ENS be frozen, and by whom?
The archived documents do not answer this as of 20 Nov 2026; AsOf lists it as Unknown.