Bugs in the Vercel ens-resolution app?

[0xc0de4c0ffee]

it’s most likely same old Universal resolver bug reading first 32 bytes of revert message as address “0x0000000…20”. displaying “0x20” as address is certainly bad decoder.

Universal Resolver Bug

I was doing final tests for our *.ipfs2.eth gateway resolver, ethers.js(v6) works ok (code below) but ens app is showing No Content Hash, * we only support ipfs/ipns hash as <subdomain>.ipfs2.eth to ens contenthash decoding in this service resolver. let wallet = new ethers.InfuraProvider("goerli");// goerli testnet let resolver = await wallet.getResolver("bafybeiee2lzvemjxesych64jw75cypjvce7nzvcyznbl3ogrztrmz2vnii.ipfs2.eth"); let content = await resolver.getContentHash(); console.log(content)…