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

Add support for ENS name resolution wherever addresses are expected #540

Closed
Arachnid opened this issue Jan 10, 2017 · 4 comments
Closed
Assignees
Labels
2.x 2.0 related issues Feature Request Stale Has not received enough activity
Projects

Comments

@Arachnid
Copy link
Contributor

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

@frozeman frozeman added this to the 1.0 milestone Jan 11, 2017
@frozeman
Copy link
Contributor

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.

Will have to think about that how to solve that.

@Arachnid
Copy link
Contributor Author

Can it simply have a default address for the registry, and optionally accept an address to override the default?

@nivida nivida self-assigned this Aug 9, 2018
@nivida
Copy link
Contributor

nivida commented Nov 29, 2018

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.

@nivida nivida added this to To do in 1.0 Nov 29, 2018
@nivida nivida added the 2.x 2.0 related issues label Jun 20, 2019
@cgewecke cgewecke mentioned this issue Nov 20, 2019
11 tasks
@GregTheGreek GregTheGreek removed this from the 1.0 milestone Jul 3, 2020
@github-actions
Copy link

github-actions bot commented Aug 3, 2020

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.

@github-actions github-actions bot added the Stale Has not received enough activity label Aug 3, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2.x 2.0 related issues Feature Request Stale Has not received enough activity
Projects
No open projects
1.0
  
Backlog
Development

No branches or pull requests

4 participants