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

chore: update ENS Registry migration #243

Merged
merged 2 commits into from
Feb 18, 2020

Conversation

aranhaagency
Copy link
Contributor

@aranhaagency aranhaagency commented Feb 17, 2020

fixes #237

@aranhaagency aranhaagency changed the title chore: update ENS Registry migration #237 chore: update ENS Registry migration Feb 17, 2020
@skywinder
Copy link
Collaborator

Thanks. Can you kindly check tesnetwrek contracts as well? should we update them?

@aranhaagency
Copy link
Contributor Author

@skywinder is the same address for all networks, I will update the pull request now.

[The ENS registry is deployed at 0x00000000000C2E074eC69A0dFb2997BA6C7d2e1e. This same address is used across Mainnet, Ropsten, Rinkeby and Goerli.] (https://docs.ens.domains/ens-deployments)
Copy link
Collaborator

@skywinder skywinder left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you!

@skywinder skywinder merged commit fe61f68 into web3swift-team:master Feb 18, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

ENS Registry migration
2 participants