tags: Ecosystem
Ecosystem Meeting, April 10, 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
- Project Highlights [PizzaDAO]
- Review upcoming events
- ENSIP Updates
- Space for service providers
- Open space for additional topics
21 Participants in Call
1. Project Highlights [PizzaDAO]
-
Snax: Worked with Namespace team to create subdomains for members
- https://pizzadao.namespace.ninja
- Important feature: Be ruggable, if not a trusted contributor want to be able to take away
- Then, subname becomes sign they are trusted by PizzaDAO
- Want subname directory to browse community members onchain, currently google sheets: https://crew.pizzadao.xyz
- @slobo.eth: happy to share what have seen in the past
- @limes: https://ethid.org/ takes records from ENS to show off team
- Suggestions on best way to use ENS protocol
- Named multi-sigs
- Configure avatars to pizza toppings
- Want to do big roll-out and show people how using it, if interested in collaboration reach out:
-
Ted Liao demonstrating WIP governance with AI
- AI Agent gathering history in the forum
- Can chat with the agent about proposals
- Working with JustaName
2. Review upcoming events
- Next event https://ethcc.io
- More updates in June
3. Weekly ENSIP Update
- Discussion on [Temp Check] ENS Offchain Subname Publication Standard from @justghadi.eth
- @lightwalker.eth: exciting standards proposal, exciting because as offchain name provider has more and more names can take a long time to paginate through them
- In this standard can just listen to changes and be efficiently indexed
- Chose OrbisDB due to decentralized nature of Ceramic network, know who controller of gateways are and can easily verify them
- SQL database, easy for developers to write SQL queries
- Write any content to the data model
- Ceramic network not considered a chain, more like IPFS
- @slobo.eth: some customers like psuedo-privacy so not all names should be written somewhere, some customers should start offchain and move onchain, Need to understand from a time stamp perspective which one is canonical and how they change
- Need to prevent data collisions
- Need to think through edge cases that could get complicated
- Broader comment on indexing: Goal is for ENS to be a global identity service, might not be congruent with being super easy to index, need to serve customers of the world and think about what is best for them
- @lightwalker.eth: exciting standards proposal, exciting because as offchain name provider has more and more names can take a long time to paginate through them
4. Open space for service providers
None this week
5. Open Space for Additional Topics
None this week
Notes by @don.nie