☎️ ENS Ecosystem – 2026 Bi-Weekly Meetings: Thursday at 11am EST (Starting 22 Jan)

🌱 ENS Ecosystem Meetings
17

1. ENS Labs Updates

  • ENS turned 9 two weeks ago. :partying_face:
  • V2 contracts are done
  • Audits found no critical or high bugs
  • The ENS app and ENS Explorer are moving along
    • Preparing to move from alpha to beta stage soon
  • Labs proposed changes to ETH pricing in V2, currently in vote.
    • TLDR: base price of 5+ character names increasing to $8
  • More posts on the blog.
  • 2 hackathons since the last call:
    • ETH Global Open Agents and ETH Prague.
    • Over 200 projects submitted to ENS.

2. Project Highlights

  • /

3. Review Upcoming Events

4. ENSIP Updates

  • A couple of new ENSIPs were merged related to agent text records
  • ENSIP-26: Agent Text Records

5. Space for Service Providers

5.1. Namehash

  • Full presentation + Lucidchart for reference
  • Building ENS Node as a Full Stack Development Platform
  • Apps can integrate with ENS Node to be ENSV2 ready at launch.
  • Current Methods for Apps to Get ENS Data
    • ENS resolutions generally go straight to RPCs, using libraries like Viem.
    • Index DNS data requires querying indexed ENS data.
    • When a CCIP read gateway is involved, apps query off-chain resolver records to CCIP read offchain gateway servers.
  • In ENSv1 people used Graph Node to index the data, producing the ENS subgraph data model inside a database.
  • This caused complexity and bugs for developers.
  • ENS Subgraph was a single chain only, and left data from other chains unindexed.
    • For example Basenames, Lineanames, ccip-read offchain subnames, etc.
  • ENS Node is composed of multiple services, including ENS Indexer and ENS API
  • ENS Indexer is a multi-chain indexer that unifies name tables across multiple chains into a single, backwards-compatible ENS subgraph data model.
  • ENSv2 indexing
    • ENSv2 doesn’t replace ENSv1; both will coexist
    • The data model for ENSv2 names is different from ENSv1.
    • ENSv2 data model is referred to as “name graph”.
    • ENS Indexer has a new plugin called the Unigraph Plugin
    • The Unigraph Plugin unifies name tables and name graphs into a single data model for both ENSv1 and v2.
    • ENS API exposes the Unigraph data model as the ENS Omnigraph, an API-level data model.
    • ENS Omnigraph API exposes resolutions for ENS, allowing users to query all ENS state through one API.
    • There’s also ENS SDK (TypeScript client) and ENS Kit (React library) for faster implementation.
  • ENSDb
    • ENSDb is an open standard for building custom services on top of ENS
    • ENS Analytics and API are being built on top of ENSDb.
    • ENS Engine will be built on ENSDB
  • Built to be extensible with ENS indexer plugins so anyone can create their own custom plugins which creates their own custom state models and their own extensions to the Omnigraph API.
  • It takes a massive amount of RPC calls that costs a lot of time and money to fully build an index of ENS.
  • There is a close relationship with the ENS Labs team, with regular sync-up calls.

6. Open Space for Additional Topics

  • A proposal for a new working group structure will be published based on feedback, with a tight timeline.
  • The current plan is to have a single working group with an extended mandate
1 Like