From my research on ENS, it seems that it has the potential to work on any L2. However, it’s worth considering if there are any teams currently working on implementing this feature. As for the ENS team itself, I haven’t noticed much progress on this front. It’s possible that they are deliberately focusing their efforts on other areas, such as the recently launched StarkNetID. Regardless, exploring the compatibility of ENS with various L2 solutions could offer many benefits for the Ethereum ecosystem, so it would be interesting to see more work on this.
Great contribution, although I suppose the intention is to strongly support the teams that are taking on the task of building in the Cairo environment (not an easy one). Personally, I would aim to continue supporting native builders.
With the forums since they post topics often and do 3 weekly google meets sometimes things can get lost in the shuffle. I stay tapped in to what Matoken.eth is doing ever since I found out he was the one leading the charge on L2’s integration because arbitrum and optimism are big users of ENS, but I’m more of aware of optimism being the main L2 users fully behind it. I believe we will see L2 resolvers / ENS records being able to be updated on there to avoid ETH gas fees sooner than later, which will trickle down to the other L2’s & blockchains since ENS is crosschain.
We were also working with starknet.id to integrate it. We will implement a minimal ENS resolver without and then work on integrating starknet.id. There are some awkward edge cases about the mutability of the ENS name and how that interacts between L1 and L2. Starknet.id has a fundamentally different model to ENS - having other data included with your address resolution is a bit odd for ENS users.
@discobot imo you should have ENS. this is a web we are decentralizing and it’s not a web if they are isolated. Leverage and complement it as much as you can. it’s better for your users if you do. has anyone asked starknet ecosystem lead re i’d they are working on this?
it does seem like lens is working w starknet so that may be why ens seems not active. a guess only.
It quite interesting in this matter, as it does show recognition from ENS to layer 2. However, I think it should be separated between ENS and Starknet.id. Each has their own place. Integration is great but benefits or recognition should be used or established differently. I am not saying we should leave ENS, but need to find a way for this to work effectively.