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

🌱 ENS Ecosystem Meetings
63

1. ENS Labs Updates

  • L2 primary names: Integrations moving along
  • Greg rewrote the docs around primary names and reverse registrars
  • Feedback button added to the Docs pages
  • Integration highlight: Gemini launched a smart wallet + ENS subnames
  • Simon’s going on Gemini Livestream
  • Greg is speaking at the World of Apps event later hosted by Nouns and the EF
  • ETHGlobal New York workshop this week

2. Project Highlights

Simple Page

  • Joel wrote an ENSIP - DService and presented last week
  • Used that IP to build a Simple Page
  • The project started as a way to publish a blog on the ENS name
  • Editable in browser, supports file uploads, pictures, etc.
  • Version control is available to see previous versions
  • Each new blog post is essentially a fork and a new deployment
  • To solve the problem of indexing websites published on IPFS, an indexer was created to look at published websites
  • The goal was to make the tool decentralized and censorship-resistant
  • URL of the indexer can be stored on a text record in an ENS domain
  • Works with a subscription-based model like ENS (1$ per month)

ENScribe

  • Accelerating smart contract naming using ENS
  • Integrated L2 primary names for contracts
  • Developers can now name their contracts on L2 networks

Proposal Review - Squid SDK

  • Reviewed the proposal about decentralizing the indexing stack for the ENSNode that currently uses Ponder
  • Barry’s team put together a demo of how to run the stack and rewrote the ENS subgraph to use their indexing stack using the Squid SDK
  • There are 3,000 workers who distribute this data in parallel
  • They aim to decentralize the entire indexing stack

3. Review Upcoming Events

  • ETH Global New York
  • The next one is Devconnect in Argentina

4. ENSIP Updates @raffy

  • New proposal for ERC-7996
  • ERC 7996 is for things that don’t have interfaces
  • It allows contracts to indicate their ability to digest specific call data types, like multicalls
  • ENSIP-22 (based on EIP-7996) defines a way for resolvers to declare and implement extra “features” via ERC-165
  • ENSIP-23 – Standardizes the universal resolver
  • The universal resolver now has a standard interface with three functions: find resolver resolve (forward resolution), and reverse (primary name resolution)
  • The Universal Resolver is not actually a resolver

5. Space for Service Providers

  • /

6. Open Space for Additional Topics

  • /
2 Likes