Update testnet to the "CAS-ready" version

[troggy]

Bounty

Prerequisites

• all the development tasks in "CAS project" project are delivered and new leap-node release is created

Scope

• update leap-node version on testnet nodes to run "CAS" release (leap-node@5.4.1)
• upgrade bridge contracts to "CAS" release (leap-contracts@1.3.1):
  • Bridge
  • FastExitHandler
  • PoaOperator
• contracts code should be verified on Etherscan
• update testnet release: code version, contract implementation addresses, attach deployment log
• smoke test, check all the infrastructure is working:
  • bridge UI
  • faucet
  • sniper rifle
  • tx store

Deliverables

• testnet running updated nodes
• announcement in #testnet channel about the network upgrade

Publicly visible delivery

• tweet about testnet update

Gain for the project

• prepare the ground for mainnet update

Roles

bounty gardener: @troggy / 50 DAI bounty worker: @troggy / 100% bounty reviewer: no review needed

[troggy]

• [x] on a network leap-node@5.3.3 + leap-contracts@1.2.0 verify node upgrade to 5.4.1 and contracts to 1.3.1
• [x] deploy new contracts
• [x] verify new contracts on Etherscan
• [x] upgrade nodes
• [x] execute contract upgrade via Rinkeby MinGov
• [x] verify
• [x] update testnet release: version, contract addresses, config
• [x] announce

[troggy]

Found a period submission handling error. Described and fixed here: https://github.com/leapdao/leap-node/pull/363

[troggy]

Follow ups:

• https://github.com/leapdao/meta/issues/180
• https://github.com/leapdao/leap-node/issues/359
• https://github.com/leapdao/leap-node/issues/365
• https://github.com/leapdao/bridge-ui/issues/250
• https://github.com/leapdao/meta/issues/150

[troggy]

delivered