We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Currently, the ENS name is resolvable only when Metamask is connected to Ethereum Mainnet.
However, ENS has support for multicoin types (eg: Bitcoin) since 2019 and we recently extended to support any EVM chains.
The proposed flow is.
coinType
resolver.getAddr(namehash, 60)
For example, the coinType of Polgyon (ChainID 137) is 2147483785 hence resolver.getAddr(namehash, 2147483785)
resolver.getAddr(namehash, 2147483785)
The draft implementation is at MetaMask/metamask-extension#18035 and I would like to get feedback before turning this into production-ready PR.
The text was updated successfully, but these errors were encountered:
This is fixed in the extension by MetaMask/metamask-extension#26242
Sorry, something went wrong.
Gudahtt/metamask-extension@5e08c06
Successfully merging a pull request may close this issue.
Currently, the ENS name is resolvable only when Metamask is connected to Ethereum Mainnet.
However, ENS has support for multicoin types (eg: Bitcoin) since 2019 and we recently extended to support any EVM chains.
The proposed flow is.
coinType60 (ETH) (eg:resolver.getAddr(namehash, 60)coinType.For example, the
coinTypeof Polgyon (ChainID 137) is 2147483785 henceresolver.getAddr(namehash, 2147483785)The draft implementation is at MetaMask/metamask-extension#18035 and I would like to get feedback before turning this into production-ready PR.
The text was updated successfully, but these errors were encountered: