Description
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:
)
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
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.