☎️ ENS Ecosystem – Weekly Meeting: 12pm ET, Thursday – Term 5

tags: Ecosystem

Ecosystem Meeting, October 10, 2024

Details

Time/Day – 12pm ET (5pm UTC) every Thursday
Google Meet Link – http://meet.google.com/ecv-oizn-psi

Stewards: @slobo.eth | ENS Profile, @limes | ENS Profile, @184.eth | ENS Profile

:information_source: Please reach out to @slobo.eth Warpcast l X if you would like to present on a future call

Agenda

  1. ENS Labs Updates
  2. Project Highlights
  3. Gitcoin Round
  4. Review upcoming events
  5. Open space for service providers
    a. Namespace
  6. Weekly ENSIP Update
    a. Editor recommendations
  7. Open space for additional topics

28 Participants in Call


1. ENS Labs Updates


2. Project Highlights

Daniel Zarzecki presenting https://Rescue.Name


3. Gitcoin

  • Participating in Gitcoin grants GG22: https://grants.gitcoin.co/
  • Applications open before next week, look out for announcements
  • ENS putting up $50k USDC, Gitcoin matching $25k, in ENS Community Round
  • Starting on October 23
  • Stewards ineligible to participate but all other projects working on ENS can participate including service providers

4. Review upcoming events


5. Open space for service providers

Nenad and @cap from https://Namespace.tech


6. Weekly ENSIP Update


7. Open Space for Additional Topics

Discussion around proposal for multichain ENS based on this post : GitHub - stevieraykatz/multiaddress-resolver: Proposal for a Multiaddress ENS Resolver
* This ENSIP specifies a new mechanism for associating multiple addresses with a single name. This should allow a user to collate their onchain identity within a single namespace
* 1 central identity for all onchain data is the summary of use case

  • @premm.eth thinks this ENSIP could help address the proposal ENSIP-ideas/ENSIPS/ensip-TBD-6.md at main Β· nxt3d/ENSIP-ideas Β· GitHub
    • This ENSIP introduces hooks, a new ENS record type to support secure onchain data resolution, including cross-chain data access and ZK-based credentials. Hooks expand ENS functionality beyond simple text resolution, establishing a framework for resolving verified onchain data on ENS names and profiles.

Discussion around EOAs/Reverse Resolution

  • ENSIP-19: EVM-chain Reverse Resolution | ENS Docs
    • Allow users to set a default address
    • Would require campaign to get users to update
    • This ENSIP specifies a way for reverse resolution to be used on other EVM chains. This allows setting primary names on L2s, as well as resolving any other records set on this specific reverse record, such as the avatar
  • EIP7702 where wallet addresses could get upgraded to contracts
    • Written by Vitalik, adds complexity
  • ENSIPs
    • This ENSIP specifies a way to set an EOA/Fallback address for a name. This allows for users to set one address to be used for all chains, or as a fallback for when a chain-specific address record is not set.

Discussions to continue in ENS Developers Chat


Notes by @don.nie

2 Likes