ENSIP Proposal: Contract Metadata Standard and Text Records

[nischal.eth]

Hello ENS community,

We at Enscribe have submitted a new ENSIP proposal that extends ENS functionality for smart contracts by establishing a comprehensive metadata standard. The proposal defines standardized text records and a new compiled-metadata resolver profile specifically designed for smart contract information.

What this ENSIP addresses:

Currently, ENS is primarily used for EOA naming and user profiles, with limited adoption for contract-related metadata. While ENSIP-4 allows storing ABIs, smart contracts need much more comprehensive metadata including source code verification, audit reports, documentation links, and licensing information.

We need your feedback:

We hope to refine this specification based on community input and move toward implementation. Your technical insights and use case feedback will be valuable in shaping the final standard.

Please review the full proposal - New ENSIP: Contract Metadata Standard and Text Records by NickSneo · Pull Request #50 · ensdomains/ensips · GitHub and share your thoughts.

Looking forward to the discussion.

[imrulo.eth]

You’re welcome.

[nischal.eth]

This is a sample contract with metadata records set - v0.enscribe.named.eth on ENS

Since the ENS manager app does not yet render contract metadata correctly, I’m adding couple of screenshots of a mock screen from the Enscribe App showing how we envision displaying that contract metadata: