NFT 'Showcase' ENS record and record standardization

[isX]

@broke.eth

The wildcard resolution is very cool. I’ve read it before but never really realised the full implications and possibilities I guess. Super exciting!

In hindsight, it will be the thing in plain sight that should have been built on sooner

@broke.eth

Just to confirm, so if I can do anything I want and these gasless ccip2 records will show up anywhere without any sort of extra integration (besides ensip10), dapps can choose to resolve part of the records and users can set any sort of record?

Correct. Off-chain resolution is already integrated in ethers.js and there is no additional integration required. Standard ENS integration used by dApps comes with CCIP-Read feature. That’s why CB.ID works seamlessly for Coinbase users.

@broke.eth

Address, avatar, socials, any custom text record basically?

Anything.

@broke.eth

Take the showcase for example? Wouldn’t there still need to be some standard? Especially as different addresses will use different resolvers. And content is set in different places. Or is something like

@jefflau.eth

"1.nft": "<NFT Contract Address A>:<TokenID A1>"
"2.nft": "<NFT Contract Address A>:<TokenID A2>"
"3.nft": "<NFT Contract Address B>:<TokenID B1>"

Currently, setting a text record of this nature will cost you $30 at 50 GWEI gas with only 2 NFTs in the showcase. It is unusable. With CCIP2, you can go crazy and add hundreds probably.

@broke.eth

And would it kinda be an ‘informal’ standard?

We plan to propose this as an ENSIP standard. Here is the work-in-progress draft: https://github.com/namesys-eth/ccip2-resources/blob/main/docs/ENSIP-15.md

@0xc0de4c0ffee already teased it before here in the forum: Support IPLD Contenthash - #6 by 0xc0de4c0ffee

@broke.eth

(simple info)

Absolutely. That’s all it is: securely hosted info, and ENS is no more than an on-chain database. On-chain secures this info with gas, we’ll secure this info with signatures.