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

🌱 ENS Ecosystem
26

Details

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

Agenda

  1. Project Highlights [@conor]
  2. Review Upcoming Events
  3. ENSIP Updates [@raffy ensip 21]
  4. Space for Service Providers
    • Blockful
    • NameHash Labs
  5. Open Space for Additional Topics

—

1. Project Highlights [@conor]

ENS app

  • Greg is at ETH Taipei
  • Sepolia ENS app is live
    • Simplying developers testing

ENScribe

  • Platform and service to deploy and/or name your contracts at deployment.
  • Added naming feature for existing contracts.
  • Primary name and forward resolution are supported.
    • If a contract extends Ownable, users can name it using ENScribe.
    • For contracts not compatible with Ownable, users can set forward resolution.
  • Plans to integrate with Foundry and Hardhat.
  • Plans to create a JavaScript library that can integrate into the ENSjs.
  • Trying to work with libraries like web3j, ethers.js, etc.

dWeb

  • Indexing and pinning service using ENS
  • This has been in discussion for about two years.
  • People struggle to work with IPFS nodes, and services have come and gone due to funding issues.
  • Next steps: fix bugs, IPNS pinning, eth.limo direct peering, snap sync, better ui, uptime monitor page.

2. Review Upcoming Events

  • ETHTaipei ongoing
  • The next event will be ethCC in Cannes, France

3. ENSIP Updates [@raffy ensip 21]

  • New ENSIP-21 written by Raffy called Batch Gateway Offchain Lookup Protocol
  • CCIP read involves a contract reverting, and the client-side library fetches data from a sub URL and feeds it back into the contract.
  • A primary user of this is the Universal Resolver, which aids in ENS resolution and is tied into the batch gateway because it needs to make multiple resolutions.
  • The current CCIP read standard requires sequential processing of URLs, which involves reverting and waiting for each URL.
  • ENS created the batch gateway for the Universal Resolver to resolve multiple URLs in parallel as a single CCIP read process.
  • ENSIP-21 standardizes the batch gateway functionality, which was initially codified in the Universal Resolver contract.
  • The standard specifies how to transform multiple offchain lookups into a request for the batch gateway, which then returns the results.
  • The standardized batch gateway provides privacy and faster ENS resolutions for users of the Universal Resolver with popular Web3 frameworks.
  • It also offers a solution for fault tolerance in CCIP read by transforming requests with multiple URLs into batch gateway requests, preventing failures due to server errors.
  • A local batch gateway will never fail unless there are Internet issues.

4. Space for Service Providers

1. Blockful

  • Presenting next week - working on the new voting UI for SPP2.

2. Namehash Labs

  • ENSNode is the new multi-chain indexer for ENSv2 and Namechain.
  • Provides a new resolution strategy in ENS.
  • ENSNode indexes state across multiple chains
  • In cases where all data is onchain, resolution can be completed in milliseconds.
  • If information is missing (e.g. a uni.eth subname using an offchain gateway), the ENSNode will dynamically retrieve it and return it asynchronously as server-sent events.
  • The subgraph has many limitations, and ENSNode breaks through these limitations by allowing custom APIs and not forcing a specific database structure.
  • Gateways are centralized, and ENSNode promotes decentralization by allowing any app to run its own instance
    • This eliminates dependencies on third parties.
  • ENSNode will also work to index offchain names, depending on the provider offering the right APIs.
  • The value proposition of offchain names is shrinking with the rise of Namechain and other L2s.

5. Open Space for Additional Topics

Feedback on ENS IPs (from Kenya)

  • Thomas in Kenya is teaching African builders about ENS and has received feedback that the ENS IPs are complicated.
    • Making it difficult to incentivize new engineers to work with ENS.
  • Potential solution: complexities can be abstracted away using APIs and frameworks.
  • A potential solution for simplifying this is from NamehashLabs - ENSAdmin – aiming to make it interactive to see how the protocol works and how practical cases are handled.
  • They are building a tool where users can choose a strategy and name, and a visualization will be dynamically built.
  • The goal is to learn through examples and help integrators build mature integrations with ENS.
2 Likes