Does XMTP support ENS subdomain resolution via CCIP-Read (EIP-3668)?

XIPs (XMTP Improvement Proposals) XIP Stage 0: Ideas
1

Hi, I’m building https://ensub.org — a platform that lets ENS domain owners issue subdomains to their community (e.g. alice.pixelgoblins.eth). Subdomains are resolved either offchain via Namestone (CCIP-Read) or onchain via Durin’s L1Resolver pointing to an L2Registry.

I tested on xmtp.chat and raw wallet addresses work fine, but addressing a message to alice.pixelgoblins.eth returns

“Invalid address, inbox ID, ENS name, or Base name.”

My question: Does XMTP’s ENS resolution support subdomains whose resolver implements EIP-3668 CCIP-Read? If not, is thison the roadmap?

The use case: our subdomain holders would love alice.pixelgoblins.eth to work as their XMTP address — it’s their primary onchain identity. Since the subdomain correctly resolves to a wallet address via the ENS registry + CCIP-Read, it seems like it should be supportable with the right resolver lookup.

Happy to share resolver contract addresses and test subdomains if useful for debugging.

6 Likes
2

Hi Mate, XMTP’s ENS resolution in xmtp.chat does not currently support CCIP-Read (EIP-3668) for subdomains like ‘alice.pixelgoblins.eth’. i believe this just to be a gap in their implementation at the moment, not a fundamental protocol limitation.

4 Likes
3

Thanks for the reply :slightly_smiling_face: , would be cool to know if there is any plan to make it accessible or if it’s in the roadmap! :crossed_fingers:t2:

3 Likes
4

Great thinking. I believe this will be very useful for official situations

4 Likes