tags: Ecosystem
Ecosystem Meeting, January 9, 2025
Details
Time/Day – 11am ET (4pm UTC) every Thursday
Google Meet Link – http://meet.google.com/aqf-vrvq-kfw
Stewards: @slobo.eth (ENS | X), @limes(ENS | X), @don.nie (ENS | X)
Please reach out to @slobo.eth Warpcast l X if you would like to present on a future call
Agenda
- ENS Labs Updates
- Project Highlights
- Review upcoming events
- Space for service providers
- ENSIP Updates
- Open space for additional topics
21 Participants in Call
1. ENS Labs Updates
- Labs catching up from break
- Fixing bugs in manager app and preparing manager app for ENS v2 (design phase) to make future development faster
- Contracts: ENS v2 in progress
- 2025 Events planning, starting with ETH Denver
- Bug in Dune and Google Data Studio (showing spike in revenue) will be resolved over next day or two
2. Project Highlights
- GasHawk will present in Public Goods call
3. Review upcoming events
- Planning stages for ETH Denver event; will report when have more info
4. Open space for service providers
None this week
5. Weekly ENSIP Update
- ENSIP GitHub repo: GitHub - ensdomains/ensips: ENS Improvement Proposals
- 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
- GitHub - operatorlabs/manifest
- 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
- Brief discussion of possibility to add other ecosystems to Drips campaign: ENS Ecosystem Term 5 Grant | Drip List | Drips
-
Nischal Sharma from Web3j
- Ethereum Name Service - Web3j
- Requests feedback and merge of this PR (Greg to review): Added web3j code samples by NickSneo · Pull Request #364 · ensdomains/docs · GitHub
Notes by @don.nie