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

1. ENS Labs Updates

2. Metagov Retro

  • Metagov has been leading a retro evaluation for ENS
  • They are looking at key challenges and making recommendations
  • Phase 2 of the work is finished, and preliminary recommendations have been made.
  • Final recommendations will integrate feedback and provide actionable implementation details.
  • The point of research is to inform decisions.
  • Governance is about optimized decision-making.
  • The research has identified 3 categories of decision-making that ENS is facing: 1) accountability, 2) transparency, and 3) structural reform.
  • Remedial actions should be phased to ensure decision-making is not premature and is based on adequate evidence and data.
  • Recommendations are divided into recommendations and action items for implementation
  • The first recommendation is a flexible, light-touch master plan.
  • Master plan should be an enabler, not a constraint.
  • Master plan helps ENS set transparent, cohesive objectives for every entity in the DAO.
  • For transparency infrastructure - setting up cohesive documentation practices.
  • Implementing standards and templates around reporting.
  • Standardized templates and reporting timelines that feed into master plans.
  • For accountability - Documenting expectations and performance metrics for delegates, conflict of interest structures, etc.
  • Treasury oversight - Standardizing capital allocation procurements (Labs, SPP)
  • Sanctions - ENS should correlate sanctions to different types of undesired behaviors
  • Holding office hours and additional workshops for feedback.
  • More details here.

3. Project Highlights [@clowes.eth]

  • Thomas from Unruggable created: https://enswhois.com/
  • You can enter a name, address, hash, or Label token ID to retrieve data about that name.
  • ENS Indexer website: https://ensindexer.com/
  • ENS Indexer is the product powering the ENSWhois product.
  • It’s an indexer for ENS, designed as “dRPC for indexing,” with a centralized entry point and a decentralized network of indexes.
  • It uses a RESTful API for querying data about ENS names
  • API-first integration is the future of ENS, according to Thomas.
  • There have been 24 ENS-related contracts since 2017
    • This makes it difficult for new entrants to parse the data.
  • Therefore, more integrations will happen through API due to simplicity.
  • Anyone can deploy their own indexer with a single click for about $10 a month.
  • Project will be open-sourced in the future.
  • The idea is to create a decentralized network where anyone can deploy their own indexer.
  • When an indexer starts, it automatically owns home.
  • The proxy pings the indexer every minute to verify data integrity.
  • Read more in his blog post: Indexing the Ethereum Name Service.

4. Review Upcoming Events

  • /

5. ENSIP Updates

  • ENSIP-27 – Clarifies the format to always be ensname@label
  • ENSIP-26: Minimum set of text records for agents (ENS AI group discussion).
  • Introduces two keys: agent context and agent endpoint.
  • Agent Context can evolve over time, potentially using markdown or embedded JSON.
  • Learn more about ENSIP-27.

6. Space for Service Providers

6.1. JustaName

  • Jaw.id iz is an identity-centric smart account infrastructure
  • The demo showcases advanced workflows enabled by the permission layer.
  • It highlights using ENS as a gamer tag across different games.
  • Session key functionality highlighted:
    • Starting a new session creates a private key (access key or session key) in the background, which changes on each session.
    • The session key is never funded or directly touched by the user.
    • In the example, permissions are delegated to this access key to spend 2 USDC for 1 hour.
  • Demo included onchain execution
    • Every click in the game costs 0.1 USDC.
    • After clicking multiple times, all calls are grouped into a signal tx and executed onchain.
    • If the original allowance is exceeded (2 USDC), the transaction should have failed.
  • Launched CLI SDK:
    • Goal: Maintain security properties of the Jaw stack while allowing CLI usage, especially with AI agents.
    • A local daemon runs on the user’s device and communicates encrypted messages via a relay.
    • The relay is open source and can be self-hosted
    • CLI can be used to call wallet connect and sign transactions
    • The CLI SDK provides rails to develop stronger use cases, especially with machine payment protocols (MPP) recently announced by Tempo.

7. Open Space for Additional Topics

  • /
1 Like