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

Switch testnets from Ropsten to Goerli #1054

Open
5 tasks
tomholford opened this issue Oct 12, 2022 · 2 comments
Open
5 tasks

Switch testnets from Ropsten to Goerli #1054

tomholford opened this issue Oct 12, 2022 · 2 comments

Comments

@tomholford
Copy link
Collaborator

tomholford commented Oct 12, 2022

Ropsten is being sunset in Q4 2022. As such, we will need to migrate testnet usage for future development work.

Tasks off the top of my head (probably more will be needed):

  • update Infura API endpoint and key
  • deploy Azimuth and Ecliptic to new testnet
  • spawn test address space on new testnet
  • update scripts in package.json
  • point dev environment to new testnet
@vvisigoth
Copy link
Contributor

@tomholford was this ever done?

@tomholford
Copy link
Collaborator Author

@tomholford was this ever done?

Most of the required work was handled in this commit:

b660379

Specifically, Bridge's references to Ropsten were updated to point to Goerli. And, @liam-fitzgerald deployed the azimuth contracts to the new testnet as part of the Groups 2 migration prep. But at the time (~6 months ago), the other contracts (delegatedSending, linearSR, and conditionalSR) were not deployed. So, Bridge will crash when attempting to reference those entities.

So, once those additional contracts are deployed to Goerli, and the addresses are updated in contracts.js, then it "should just work"... hopefully

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

No branches or pull requests

2 participants