☎️ ENS Ecosystem – Weekly Meeting: 11am ET, Thursday – Term 6

🌱 ENS Ecosystem
32

Details

Meeting Link: meet.google.com/iiw-tpmh-bmg

Agenda

  1. ENS Labs Updates
  2. Project Highlights
  3. Review Upcoming Events
  4. ENSIP Updates
  5. Space for Service Providers
    • NameHash Labs
  6. Open Space for Additional Topics

—

Notes

1. ENS Labs Updates

  • 2 new executable proposals are live
  • Deep into ENSv2 - lots of dev momentum right now
  • High-level activity overview on ENS GitHub
  • Working on Indexing standards
    • On the best way to help ecosystem developers and make it easy to have their names indexed

2. Project Highlights

ResolverENS

  • Shows a list of all 3rd party resolvers and:
    • supported interfaces
    • attached subnames to it
    • ENSIP support
  • Powered by ENSNode
  • Feedback – add latency check for different parts of the world
  • IPFS gateway latency shared by Greg
    • Checks from the local browser, not different geographical regions

ENSribe

  • Officially Live on Mainnet – Ethereum, Base, and Linea
  • Allows users to name their contracts deployed on those networks
  • Request to test it and provide feedback

3. Review Upcoming Events

  • FarCon – No official presence, but ENS people will be there
  • ethCC – Lots of ENS folks will be there

4. ENSIP Updates

  • /

5. Space for Service Providers

5.1. Namehash Labs – Progress update

  • Improving DevOps to make the release system production-ready.
  • Working on ENSAdmin to make it easier for new devs to launch ENS apps.
  • GraphQL AI generator / editor demo.
  • Test it here.

1600×948 132 KB

6. Open Space for Additional Topics

6.1. Information Finance Token

6. 2. Indexing standards

  • Problem: Users expect to see all their ENS names (L1, L2, offchain) in the Manager app
  • Categorization of names: L1, L2, and database names (offchain).

Indexing Database (offchain) names

  • An L1 contract should emit an event when a metadata URL is attached to a name.
  • Once an indexer establishes the connection between a name and a parent, they can start requesting updates.
  • The response includes an array of profiles with everything set on the profile
  • Solves the “My Names” page problem and detects text records and addresses without burdening a gateway.
  • When anything about a name is updated, a gateway can return the entire profile, and the indexer accepts it as the latest truth.
  • Resolution should always happen live through an RPC.
  • Subname records don’t change that often, so maintaining the latest state isn’t hard.
  • A backend service can make API calls without a problem.
  • This gives API operators some expectation of how many requests to expect.

Indexing L2 names

  • Indexing L2 names can differ due to the nature of smart contract events.
  • Different sets of events may exist for ENSv1, ENSv2, and third-party implementations.
  • It’s better to make things easier for subname providers than indexers.
  • The ENSNode can act as the metadata endpoint for ENSIP 16.
  • Subname providers can specify their own metadata URL for live data retrieval.
  • Indexing is still needed to solve the “My names” problem.
  • The goal is a Manager app displaying all ENS names (L1, L2, database names).
  • Users should be able to see all text and address records.
  • Combined with ENSIP 20, users should be able to edit all names and records.
2 Likes