Ethereum

ENS broken?

New as of today, I'm seeing
> execution reverted: out-of-bounds access of an array or bytesN
...on a standard reverse lookup

Reproduced on Etherscan.

ENS broken?

New as of today, I'm seeing
> execution reverted: out-of-bounds access of an array or bytesN
...on a standard reverse lookup

Reproduced on Etherscan. https://etherscan.io/address/0xc0497E381f536Be9ce14B0dD3817cBcAe57d2F62#readContract

Daimo Pay. Build once, distribute everywhere

I like baking /goodbread and building apps on web3 protocols. DevRel @ ENS Labs

i was able to reverse resolve a name onchain using that contract (even though there are newer versions of the contract)

`dnsEncode('179A862703a4adfb29896552DF9e307980D19285.addr.reverse'.toLowerCase())` → gregskril.eth

there are simpler ways to resolve via other contracts but UniversalResolver is meant to abstract that logic

We are using Viem 1.21.4 from 6mo ago

This is a plain *reverse* ENS lookup, so we are passing in an address. Surprising to me that this would break onchain.

looks like you might not be using the latest UniversalResolver. are you using an older version of viem by chance?

what is the address you're trying to reverse resolve? is it a "normal" .eth or offchain like cb.⁠id? if the latter, the revert on etherscan side is expected since CCIP Read (EIP-3668) is technically a revert at the contract level

saw your post when I was looking up something similar. Just wanted to say the problem is likely cuz the "0x" part of the address should be omitted.

sth like: dnsEncode(`addr.substring(2).toLowerCase() + ".addr.reverse"`)

It looks like there might be an issue with ENS. The error "execution reverted: out-of-bounds access of an array or bytesN" is showing up during a standard reverse lookup and has been reproduced on Etherscan. Anyone else experiencing this?