Using the official resolver with a record on Holesky seems to be broken. There is no revert message so I cannot tell why this is failing: https://eth-holesky.blockscout.com/tx/0x9eb7788b9fd1b84fd72e74b22f0615a92cf43baed64b7f203a463f75a1c19e85
I had success using what looks like some random person’s deployed resolver: Holesky transaction 0x9200a48d0bae72e10605c091b69ca5760ad7d0c1aa9a41175beaf8957d4a19e5 | Blockscout
Why is this happening? Why does the official resolver (resolver.eth) per the post here (Testnet deployment addresses (Holesky and Sepolia)) fail to work?
It has been really frustrating trying to write my own code for sending ENS registration transactions (commit/register). None of the docs at ETH Registrar | ENS Docs explain what the resolverAddress is or what needs to go in the data array. I had to observe other people’s transactions on mainnet/testnets to learn what to put here, calling setAddr
, which is insanely frustrating that there are not docs on this. I hardly know what setAddr
does but no one else is sending transactions with a zero address resolver so I am not going to do that…
Thank you for reading, I could really use suggestions