We have posted an article that gives a complete overview of the project thus far, which is a great starting point for people who are not already familiar with the project:
Article: Bringing Structured Data to ENS Names
The article also lists a number of things we’ve built so far, which I will also include here:
The ENSIP. A draft ENS Improvement Proposal formalizing the standard. It defines the class and schema record keys, and specifies how schemas are structured and published. The draft has been submitted as a pull request to the ENSIP repository and is open for community review.
Schemas. Ten curated schemas, with documentation, covering the most common use cases, including Organization, Person, Wallet, Contract, and Agent. The Agent schema integrates with ERC-8004, enabling ENS names to act as declarative identity for AI agents.
An SDK. A TypeScript SDK that can read metadata from any ENS name, validate metadata against its schema, and write updates to ENS.
A CLI. A command-line tool, designed with agents in mind, for managing metadata directly from the terminal.
A web interface. A fully-functional web app where users can browse the subname tree of any ENS domain, view and edit metadata in both tree and table views, and submit batch transactions to update records on-chain.
Documentation.A dedicated docs site with an explanation of the standard, reference pages for each schema, and how-to guides for common use cases.
We are now at the point of onboarding users and helping people decide what records make the most sense for their use cases. If you want to get involved, please reach out!