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

Support -network=arbitrum-one #2242

Closed
leszko opened this issue Feb 7, 2022 · 3 comments · Fixed by #2254
Closed

Support -network=arbitrum-one #2242

leszko opened this issue Feb 7, 2022 · 3 comments · Fixed by #2254

Comments

@leszko
Copy link
Contributor

leszko commented Feb 7, 2022

Add support for -network=arbitrum-one.

Similar to what we did in #2202

Activities:

  • Add chain support build variables
  • Add controller address in livepeer.go
@leszko leszko self-assigned this Feb 7, 2022
@leszko
Copy link
Contributor Author

leszko commented Feb 7, 2022

blocked until contracts are deployed in Arbitrum Mainnet

@yondonfu
Copy link
Member

yondonfu commented Feb 8, 2022

Suggested change: I think we should use arbitrum-one-mainnet as the name of the network to follow the arbitrum-one-* naming convention that we already use for arbitrum-one-rinkeby since "Arbitrum One" is the term used to distinguish Arbitrum's flagship rollup chain from other deployments of Arbitrum rollup chains.

@yondonfu
Copy link
Member

Making a note that we'll want to remember to set redeemGas in the network config for arbitrum-one-mainnet similar to what we do for arbitrum-one-rinkeby in #2252

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants