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

ENS: option to use custom registry addresses #3010

Closed
sohkai opened this issue Aug 7, 2019 · 0 comments · Fixed by #3301
Closed

ENS: option to use custom registry addresses #3010

sohkai opened this issue Aug 7, 2019 · 0 comments · Fixed by #3301
Labels
1.x 1.0 related issues 2.x 2.0 related issues Feature Request

Comments

@sohkai
Copy link

sohkai commented Aug 7, 2019

Description

The current web3.eth.ens module only supports the official ENS registries on various networks, but there are some custom ENS deployments (especially on testnets) that users may want to resolve from.

Expected behavior

Upon creating the ENS module, the user could pass an option to specify the registry address (e.g. see ethereum-ens's options).

Actual behavior

The ENS module self-selects a registry address based on the current network, without giving the user a chance to override it.

Versions

  • web3.js: v1.2.1 and v2

It would be ideal for this to be included in both v1 and v2, but if we'd like to avoid new features to v1, it would make sense to add it only to v2.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1.x 1.0 related issues 2.x 2.0 related issues Feature Request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants