The ENS Ecosystem Working Group holds weekly calls. The calls are open to community members and the general public.
The ENS Ecosystem Working Group calls are led by the lead steward of the working group. The current lead steward is slobo.eth. If you need to get in touch with slobo.eth, please message him on the forum, or on X.
How to Add to Weekly Agenda
If you have items that you would like to add to the weekly agenda please message any of the ENS Ecosystem stewards (@slobo.eth, @Limes, or @don.nie ) through the messaging feature on this forum.
How to Apply for Grants
Ecosystem WG supports builders with grants of up to 50,000 USDC per year based on retroactive value created for ENS, as determined by the stewards. To apply, fill out this form. For examples, see Term 5 Grants.
How to Use this Thread
Agenda will be posted along with call summaries. Please do not post in this thread unless requested by one of the Stewards.
Please provide any and all feedback or if want to get involved!
@nxt3d on twitter
Looking forward to improving the process over 2025, especially with implementation of ENSIP 19
Need to resolve if ENSIPs are canonical or not over 2025
Greg: I would say ENSIPs are canonical but that doesn’t mean people can experiment outside of them. experimentation is what should inspire ENSIPs
ENSIPs for library developers and dApp developers, but things such as text records for a larger audience; powerful primitive of ENS
Full-time job to get downstream adoption of libraries with all different communities/ecosystems (especially with large projects that are closed-source); teams don’t have tons of incentive to update
Need to consider when building out/promoting Namechain
6. Open Space for Additional Topics
Eskender from Labs
Few companies forking ENS for own purposes/create agents, lose network effects of ENS
Working on metadata standard so have a registry of agents
A lightweight standard for defining AI agent identities across platforms
Devs please review and provide feedback
Will work with projects/launchpads to try and get them to adopt/enforce standard
Launchpads (e.g. pump.fun) create the metadata for projects, make sense to target launchpads so projects created there will automatically have the metadata
@premm.eth and @thecap.eth also working on agents in 2025, will present work in the future
@premm.eth: ENSIPs important to rapidly propose new standards/ full community investment
Fixed Dune dashboard error for calculating .eth registration revenue
2. Project Highlights
No project highlights but Greg mentioned Ponder – a lightweight, open-source, and faster alternative to the Graph. Typescript backend framework for building crypto apps.
Greg built an ENS indexer on Ponder and did a quick demo. More about this project on Greg’s GitHub.
ENS Ideas website was mentioned as an example of an app that could use Ponder and Indexer — to view new name registrations and/or fetch all records from names/subnames. Or it could be integrated into ENS Dapp so all names and their records are fetched from an Indexer instead of an ENS Subgraph.
Comparison with Graph
The graph is more granular; the indexer is a simpler, self-hostable version.
Indexer provides access to data in a raw format via a Postgres database.
Allows for building custom REST endpoints.
3. Review Upcoming Events
No major updates on ETH Denver plans yet other than ENS will be there. Plans are in progress, more details will be released soon.
Full presentation by NamehashLabs can be found here.
NamehashLabs is looking for devs. Anyone interested should ping Lightwalker on TG (@lightwalker_eth).
5. ENSIP Updates
Current open questions:
Establish independent ENSIP editors?
A pull request has been approved by Nick to name three independent EIP editors.
If you’re interested in becoming an ENSIP editor, you should ping @Premm.eth.
Should ENSIPs be canonical or not?
ENSIPs are currently canonical, but Prem proposes making them non-canonical to potentially encourage greater innovation, experimentation, and contributions.
Suggestion to create a forum thread to discuss the canonical vs non-canonical issue.
6. Open Space for Additional Topics
None
Reminder for devs and builders – ENS Ecosystem Working Group offers grants!