Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only resolving ENS on Mainnet? No Unstoppable Domain transactions? Age of Interoperability is here! #12990

Open
luncht1me opened this issue Dec 6, 2021 · 10 comments

Comments

@luncht1me
Copy link

luncht1me commented Dec 6, 2021

I'm addressing a poor design decision over this issue: #7944 (Okay, maybe at the time it made sense...)

Now that we've entered the age of cross-chain interoperability, and ENS and Unstoppable Domains can resolve to a plethora of different networks (see:
image of network fields
)

It only seems reasonable that MetaMask should resolve ENS / Unstoppable on pretty much every major L1 and L2. Every day more and more users bridge over from ETH to FTM, Matic, One, Bsc, etc...

My friend just setup an ENS and configured his Fantom FTM address with it. But, while going to test it out, we're just hit with this
silly error

As you can see in the screenshot prior, ENS is supporting FTM on the Opera chain.

"Network does not support ENS". Well, sorry to say, but the network does. MetaMask has just simply chosen to not resolve unless on ETH MAINNET...

Please, for the sake of the users, strongly reconsider this. It's terribly stifling. Why should I have to go manually resolve an ENS just because I'm on a different network? The network supports it, thus MetaMask should support it on those networks.

My proposal? Remove the choke on only resolving ENS thru MetaMask strictly if only connected to Mainnet, and support Unstoppable Domains.

@Pietro395
Copy link

I agree

@spinlud
Copy link

spinlud commented Dec 29, 2021

+1

@murillojorge
Copy link

We need this.

@ahh1539
Copy link

ahh1539 commented Apr 23, 2022

Also want this feature!

@danfinlay
Copy link
Contributor

Related to #8556, but adds Unstoppable domains. I'd like to see the ENS part, I'd like to see users able to opt into other name systems also.

@connorbode
Copy link

Related to #8556, but adds Unstoppable domains. I'd like to see the ENS part, I'd like to see users able to opt into other name systems also.

Is support for other naming systems via snaps an option?

@MakerGit22
Copy link

Hope this gets implemented! So many users + chains would appreciate it!

@V-Shadbolt V-Shadbolt mentioned this issue Sep 13, 2022
6 tasks
@rsodre
Copy link

rsodre commented Aug 10, 2023

up!

shocked and frustrated about this!
so I can't test my dapp content redirection on testnet!?
need to deploy my contract to mainnet and spend real money to test?

@AskBlockchain
Copy link

Is this ever going to get Resolved?

@mozrt2
Copy link

mozrt2 commented Dec 3, 2023

Any updates here? Metamask is one of the only major wallets not supporting L2 ENS resolution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests