Support CCIP Read and ENSIP-10

[gskril]

Offchain ENS names are becoming more popular (see Coinbase and Uniswap), so it’d be amazing to have them supported in go-ens. The relevant specs are ENSIP-10 (Wildcard Resolution) and EIP-3668 (CCIP Read).

At a high level:

• ENSIP-10 provides a mechanism to support resolution of ENS names even when the node doesn’t have a resolver.
• EIP-3668 provides a mechanism to allow a contract to fetch external data.

Test cases

• 331.moo.nft-owner.eth (onchain wildcard resolution)
  • ETH address: 0x51050ec063d393217B436747617aD1C2285Aeeee
  • description text record: Good Morning Cafe
  • avatar text record: https://gmcafe.s3.us-east-2.amazonaws.com/gmoo/original/331.png
• jesse.cb.id (wildcard resolution with CCIP Read)
  • ETH address: 0x849151d7D0bF1F34b70d5caD5149D28CC2308bf1
  • Decoded BTC address (cointype 0): 0x0014a8abf6d1989c0a209621ef2a1f4bf2843dfd153f
• gregskril.uni.eth (wildcard resolution with CCIP Read)
  • ETH address: 0x179A862703a4adfb29896552DF9e307980D19285
  • com.twitter text record: gregskril
• gregskril.com (CCIP Read at the TLD level for Gasless DNSSEC)
  • ETH address: 0x179A862703a4adfb29896552DF9e307980D19285

Compensation

The ENS DAO Ecosystem Working Group is sponsoring a 0.5 ETH bounty for a developer to implement ENSIP-10 and EIP-3668. Please reply to this issue, or on Farcaster, if you’re interested in working on this feature.

[yayashuxue]

looking into it

[yayashuxue]

Questions:

1. So this is just frontend implementation? And the js solution is already available
2. @gskril you mind pointing me to an entry point to look into in the mirrored .js file?

[alextnetto]

We'll start tomorrow. Can you assign the task to me?

[alextnetto]

ENSIP-10 implementation was done by @pikonha, from our team. Now working on CCIP Read

[pikonha]

The CCIP Read implementation is handling the offchain domain resolving by following the EIP-3668 standard. The given offchain stored addresses are being correctly resolved to their respective addresses.

However, the reading of multicoin addresses, texts, and contenthash is still in progress which is something I'll be working on today. My estimation is to have it fully implemented and update the #41 PR by the end of the day.

Feedback on the implementation is more than welcome.

[pikonha]

The implementation is now finished, both the Resolve and resolver.Address() can read offchain and subdomain addresses as well as text.