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!
People taking off .eth out of protest due to some issues with Ethereum and Ethereum Foundation and it’s nice to see that Ethereum-aligned individuals and projects are showing support by updating their X name with their .eth name.
@mely.eth did a good job on X highlighting those who publicly support Ethereum by adding .eth as their X name.
Each individual AI agent has its own Ethereum address.
AI agents can engage with DeFi through IPFS prompts
ENS agents can talk to each other
AI agents will have up-to-date data from the Web3 world, indexed from various sources like Mirror, Farcaster, ENS Website, etc.
After Nick, next AI agent is Greg.
3. Review upcoming events
ETH Denver – cool announcement
We have a date - Feb 28th!
Partnering with Linea!
4. Space for Service Providers
Namestone:
Update on indexing off-chain names and making them publicly available.
New API route for accessing names hosted by Namestone.
When you call getNames so far names have been private and from now it they will be publicly accessible.
Namehash Labs
Rleasing some updates soon on the Indexer and ENS Node.
Backwards compatible GraphQL API
Integration with Ponder for improved ecosystem compatibility
5. ENSIP Updates
ENSIP-16 - @blockful proposed an improvement around this IP to improve Offchain subnames.
Regarding ENSIP Blockful has been working on - the idea is to enable one unique standard for managing offchain subnames from all providers including cb.id, namestone, namespace, etc.
Just Name is an off-chain subname provider that allows applications to issue subnames.
Features:
Dashboard to add ENS names.
SDKs (core, React, widget) for integration.
Widget for easy integration into DApps or platforms.
Demo of the widget:
Generates an API key.
Connects ENS names to the account.
Claims subnames with signed messages.
Plugin concept to extend the widget with other protocols (EFP, Talent Protocol, POAP).
Integrations with XMTP and JustVerified.
JustVerified: Open-source infrastructure to generate verifiable credentials for ENS names, proving ownership of socials (Twitter, Telegram, Discord, GitHub, email) and soon, proof of personhood.
SIWENS
SIWENS is an extension of SIWE (Sign-In with Ethereum), with an added sentence in the message: “I’m signing in using my ENS name.”
Combining SIWENS with LLMs gives context about the ENS name to the AI.
Allows the AI to access the user’s name, addresses, and socials, completing the identity journey.
ENS TOOLS
The solution was to store tools inside ENS name records and execute them in a sandbox environment to decentralize tool calling.
The AI can check if a subname is available using tools like “tools.just.id” by resolving the ENS name, extracting the tools record, and performing the check in a sandbox.
ENS functionalities added, such as getting voting power, ENS token price, and ENS balance.
For example, to get Vitalik’s ENS balance, the AI resolves the ENS name to an address and passes it to the ENS tool.
Chrome Extension
A Chrome extension resolves ENS names or any name on Twitter ending with ETH or any TLD.
It allows users to see all the records and profiles of ENS names on Twitter.
Space for Service Providers
4.1 NameHash Labs @lightwalker.eth
4.2 Wildcard
ENSIP Updates
Open Space for Additional Topics
—
1. ENS Labs Updates
Added Spanish and Portuguese translation and improved Chinese.
Registering a name gave you a wrapped name by default, now it will intelligently choose whether to wrap or unwrap the name during registration to be the most efficient gas-wise.
Dark mode is live.
No updates on the L2 primary names yet
2. Project Highlights
/
3. Review Upcoming Events
3.1 ETH Denver
No calls next week because of ETH Denver
If you’re at ETH Denver join the ENS x Linea event
An early prototype of an admin dashboard is already built and will be shared in the coming weeks.
Working to improve ENS for devs and app builders.
This will lead to improved user experiences for the whole ENS ecosystem.
More documentation is coming soon.
Subgraph Compatibility
Goal: Ensure the ENS Node represents the same data as the subgraph.
Focus on data equivalency – having the same data as on the subgraph.
Serving the data in the same API format that client libraries expect.
Zero difference as of yesterday.
ENS JS tests pass 100% after switching out the subgraph for the ENS node.
Next steps: Onboarding, tidying up, and making it more accessible.
Considering backward compatibility, this enables free subgraph queries!
Wildcard
Records xyz: manage ENS profiles on different L2s
Decentralized identity should be available to everyone,
Challenge is fragmentation of records and different L2s
Records.xyz allows users to manage ENS profiles across different L2s
Separate records ledgers were built for each L2 to store profile information, giving users the freedom to choose the L2
Interoperability via Ethereum’s Open Intents Framework offers a solution by streamlining cross-chain transactions, allowing users to trigger updates from any supported L2 with records saved on a unified L2 for storage, reducing fragmentation.
The long-term vision is for Records.xyz to scale and support hundreds of L2s, providing seamless management of ENS profiles.
5. ENSIP Updates
Strategy Discussion Calls
Bi-weekly opt-in call for deep dives into specific topics
New Meeting Link for 2025 
Please reach out to 
Reach out to 
