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

[Rewrite 4.x] ENS #4321

Closed
4 tasks
Tracked by #4317
jdevcs opened this issue Sep 13, 2021 · 2 comments
Closed
4 tasks
Tracked by #4317

[Rewrite 4.x] ENS #4321

jdevcs opened this issue Sep 13, 2021 · 2 comments
Assignees
Labels
4.x 4.0 related Epic

Comments

@jdevcs
Copy link
Contributor

jdevcs commented Sep 13, 2021

( This is Epic for 4.x Management )

ENS

Have features to interact with ENS and using ENS in other modules of web3 instead of addresses.
Migrate existing ENS functions from 1.x web3-eth-ens to 4.x

Related Issues / Feature Requests / Discussion

Create web3-eth-ens package structure for 4.x - #4550
Create ENS class - #4752
Migrate ens resolver and registry abi from 1.x #4551
Migrate contract registry functions from 1.x - #4552
Migrate Resolver functions and config from 1.x - #4553
ENS support in all web3 packages - #4574

Can be released after 4.x alpha release:
ENS reverse registrar functions - #4586
ENS permanent Registrar functions - #4588
ENS add new ABI contract functions for feature parity with ENS in 4.x #4600

Features

  • Registry, Resolver, Owners, TTL and Record Management
  • Allow to use ENS in other parts of web3 instead of addresses

https://docs.ens.domains/
https://github.com/ChainSafe/web3.js/tree/1.x/packages/web3-eth-ens

Dependencies / Related Modules

Providers
Eth
Contract
Transaction
Utils

Documentation

  • README ( overview, example, .. )
  • Documentation

Related EIPs

External Libs

Follow Lib Selection checklist.

@github-actions
Copy link

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 May 21, 2022
@mconnelly8 mconnelly8 removed the Stale Has not received enough activity label May 24, 2022
@github-actions
Copy link

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 Jul 24, 2022
@github-actions github-actions bot closed this as completed Aug 9, 2022
@luu-alex luu-alex reopened this Aug 9, 2022
@luu-alex luu-alex reopened this Aug 24, 2022
@luu-alex luu-alex removed the Stale Has not received enough activity label Aug 24, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
4.x 4.0 related Epic
Projects
None yet
Development

No branches or pull requests

4 participants