Holesky ENS registration via resolver.eth completely broken?

Many thanks for the detailed information. I like the UI of your tool, too. I understand what wrapping means now.

So to reiterate this is a deployment issue, right? The ETH Registrar Controller specified by Testnet deployment addresses (Holesky and Sepolia) (0x179Be112b24Ad4cFC392eF8924DfA08C20Ad8583) should be equal to baseResolver.interfaceImplementer(namehash("eth"), "0x612e8c09") but that is currently set to 0xF404D2F84BC1735f7D9948F032D61F5fFfD9D3C3.

And my deployment here worked because this other resolver trusts 0xF404D2F84BC1735f7D9948F032D61F5fFfD9D3C3 but the “official” resolver (resolver.eth on Holesky) does not, right?

1 Like