You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
ENS deployment on Mainnet is coming soon, and it'd be awesome if web3 supported transparently resolving names any place an address is expected - for instance, myContract.at('foo.eth').
The only problem is that web3.js has to be aware of the network its on. And therefore needs to make async calls on init to determine the network, which is not ideal.
I'll add full support of ENS as soon as possible. Currently we have only the ENS module and I will add ENS support for all from or to properties/arguments too.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. If you believe this was a mistake, please comment.
ENS deployment on Mainnet is coming soon, and it'd be awesome if web3 supported transparently resolving names any place an address is expected - for instance,
myContract.at('foo.eth')
.An ENS library is already available here: https://www.npmjs.com/package/ethereum-ens
The text was updated successfully, but these errors were encountered: