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

🌱 ENS Ecosystem Meetings
61

1. ENS Labs Updates

  • L2 primary names are live at the protocol level
  • A demo walkthrough is available to show how it works
    • Greg’s address is the only test case: 0x179A862703a4adfb29896552DF9e307980D19285
    • Test directly here.
  • Integrations for VIEM and WAGMI are coming next week.
  • If you wanna use it before those integrations are live, see this.
  • Base will be migrating existing records to the new official reverse registrar on Base in a few weeks.
  • ENS Node has support for all of this that is going to ship.
  • Idea to expose an API where an app can request the primary name for an address, providing an ordered list of chains to check
  • It will take time for the basics to proliferate through libraries and apps.

2. Project Highlights

  • /

3. Review Upcoming Events

4. ENSIP Updates @jthor

  • DService Text Records: specification for putting a list of URLs in an ENS name
  • Made a PR to the ENSIP repo.
  • Every DApp needs an indexer, leading to reliance on centralized infrastructure or building their own.
    • This creates a UX issue where a decentralized app hosted on ENS relies on a single endpoint controlled by the developer.
    • If the developer shuts down services, the app becomes unusable.
  • DService text records allow dynamic updates without redeploying applications

5. Space for Service Providers

5.1 JustaName

  • Big release went live with infrastructure optimization
  • Three main items: 1) admin dashboard revamp, 2) allowed domains for API keys, and 3) new functionality called Records for offchain subnames
  • Admin Dashboard:
    • Shows analytics to communities about ENS usage at the workspace level
    • Displays ENS names, resolution counts, and claimed subnames
    • Analytics on the ENS level include community, cointype distribution, and text record distribution
  • Allowed domains:
    • Addresses the issue of API key security during client integration
    • Developers can add allowed domains that are permitted to use the API key
    • API requests are checked to ensure they originate from allowed domains
    • Enables direct frontend integration without serverless functions or a backend
  • Records functionality:
    • Addresses the issue of resolving offchain subnames
    • The first request returns a response that gives the keys of those records
    • Allows clients to use those keys and get all of the data that is attached to the name

6. Open Space for Additional Topics

2 Likes