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

🌱 ENS Ecosystem
44
tags: Ecosystem

Ecosystem Meeting, May 30, 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. ENSv2 discussion with @nick.eth forum post
  2. Project Highlights
  3. Gitcoin Payout Update @Limes
  4. Weekly ENSIP Placeholder @Premm.eth
  5. Review any upcoming events with ENS involvement
  6. Open space for service providers
    a. Resolver Works @slobo.eth
  7. Weekly Review of Canny
  8. Open space for additional topics

36 Participants in Call

1. ENSv2 discussion with @nick.eth forum post

  • Take advantage of opportunity to redesign ENS from the ground up
  • Everything learned from last 7 years went into redesign
  • ENS root registry will continue to be on Ethereum L1
  • No most-favored nation status. A chain will host ENS on L2 but users will be able to move name on any chain
  • ENS Chain is a placeholder for whichever chain go with
  • Won’t be building L2 from scratch, building a good L2 massive challenge, good L2s already exist
  • Chain picked must have clear path to maximum decentralization
  • Reverse resolution is something can push forward to clients even as building ENSv2
  • Timeline: Too early to commit to timeline, need to get feedback and commit to an L2, this is main focus, want to build quickly
  • Yes, offchain names will continue to function normally after the migration
  • High-level thoughts about migration: Transfer name to migration contract and receive L2 name, could also keep on L1
  • New registrations would have to happen on L2, but could chose to move to L1
  • Biggest lessons learned from name wrapper and how applied? Biggest lesson is that resolution process is upgradeable permisionlessly. But same hasn’t been true about ownership. Name wrapper was an attempt to open up ownership model but had to be built on top since registration not upgradeable. New system allows for upgradeability on top of registration as well
  • Domain names hosted on an L2, but resolution will still be on L1
  • Why not put resolution on L2 as well? Want users to still be able to choose gold standard security and censorship resistance of L1. Don’t want to force clients to use lower trust L2 node
  • How final is design? If somebody comes up with a different design needs to be a real barn burner to be considered. Revisions to this design are still very much open for real, meaningful technical feedback
  • Is architecture using EVM gateway? Yes, EVM gateway key to reading results on ENS chain
  • Latency for name resolution increasing a bit
  • Technical feedback thread: Technical feedback thread for ENSv2
  • How see other L2s play into new architecture? Other L2s will benefit from EVM infrastructure and cross-compatability between L2s of ENS Chain
  • What are you most excited about? Write all new solidity code. Find architecture really interesting and fun to see come together. Unique architecture haven’t seen before

Ongoing from ENS Labs

  1. Breaking change to EVM gateway to OP Mainnet sometime in next few weeks. Join dev chat to stay in touch with updates: Telegram: Join Group Chat
  2. Subgraph for querying ENS data migrating to decentralized version, not a breaking change. But if use a lot of queries should sign up for own account

2. Project Highlights

None this week

3. Gitcoin Payout Update @Limes

  • Analysis of distribution completed
  • Contract funded, waiting to receive matching funds and additional grant funds
  • Aiming to complete payout soon

4. Weekly ENSIP Placeholder (@Premm.eth)

5. Review any upcoming events with ENS involvement

  • ETH Belgrade: https://ethbelgrade.rs/

    • June 3-5 in Belgrade
    • DM @cap.eth if attending

  • Big Presence at EthCC: https://ethcc.io/

    • July 8-11 in Brussels, Belgium
    • More details coming soon, will have dev day with ENS Labs in addition to a social event

  • ETH Global: https://ethglobal.com/

    • July 12 - 14 in Brussels, Belgium

6. Open space for service providers

Resolver Works @slobo.eth

  • Launched https://teamnick.xyz at beginning of year
  • Upgraded gateway to EVM style gateway, now trust-minimized capable
  • Data behind gateway is open-sourced and available on repo: GitHub - resolverworks/ens-gateway
  • Forum post on difficulties from a UX perspective since state doesn’t get changed on L1 right away, please read and provide thoughts/feedback: EVM Gateway & User Experience
  • @clowes.eth: What’s intention of TeamNick going forward? How make accessible to normal non-technical people? Average user wants to see name in wallet right-away, might have to give on trust-minimized to accomplish that goal to serve the needs of users

7. Weekly Review of Canny

Engagement and upvoting on Canny are helpful, offering direct feedback to ENS Labs & Working Groups that benefit the ENS protocol. ENS.canny.io includes feature requests, integrations, bug reports, and community upvoting.

8. Open Space for Additional Topics

@maintainer.eth: What’s easiest way to see if something on Canny has been built? @slobo.eth: Can filter by completed within Canny

@netto.eth: Where can I find matching amount for Gitcoin Round?
@slobo.eth: Currently being calculated as matching amount was increased

Discussion around moving funds to L2/ around L2s to participate in Gitcoin and how make easier/ less friction to allow more people to participate. Discussion around tutorials/videos to help users

Notes by @don.nie

1 Like