-
Notifications
You must be signed in to change notification settings - Fork 7
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
upgrade operator contract on testnet #202
Comments
started testing the upgrade locally, got this:
suspicion: |
ok, with this PR the upgrade works on local network. here is what i did:
if period submission would fail, then machine-gun would stop. |
One thing to keep in mind: leap-node version for such tests should be the same as on testnet (if contract upgrade will be done before node upgrade) |
as the first machine gun run was able to pass a period submission i guess there is no danger to upgrade nodes before upgrading contracts? 🤔 |
contract deployed an verified at: https://rinkeby.etherscan.io/address/0xd5588c166bc53e9360320ee0fe2daf7b510718ce |
I'm on it. leap-node is good enough for testnet
There was one more change since this deployment. Will create a new leap-contracts release and deploy the latest version |
|
contracts upgraded |
reviewed contract deployment by:
|
Bounty
with the current contract
CASheartbeats and better slot management is not supported.Scope
Deliverables
Gain for the project
Roles
bounty gardener: @johannbarbie / 10%
bounty worker: name / share
bounty reviewer: name / share
The text was updated successfully, but these errors were encountered: