​​ReBOOTY Launch Checklist

​​Launch Criteria

​​Repeatable success for core flows - deposits, withdrawals, recollateralization, and tipping - on the staging camsite against Rinkeby.
​​
​​Target: Friday/Saturday

​​Ordered List of Operations

  1. ​​Review https://github.com/SpankChain/camsite/pull/1280 (Lex/Layne/Rahul)
  • ​​This is a moderately complex change, so I’d like some more careful eyes on it to make sure it doesn’t accidentally explode things.
  • ​​Currently running on staging (… once cloud build finishes)
  1. ​​Move currently “in progress” tickets to “done” if they are done (Lex)
  1. ​​Knock out tickets from the REB board “Backlog” - this is where we’ll keep an ordered list of “stuff that needs doing”
  • ​​If you’re sitting asking yourself “what should I be doing right now?” the answer is “taking a ticket from the backlog!
  1. ​​Noon PST: start “Preparation” checklist

​​Preparation

  • ​​Create a tag of what currently exists on custodial-revert​.
  • ​​ dec21-18-cusodial-revert-pre-booty-drop​
  • ​​Make sure everyone has a couple wallets in different browser profiles available to test the migration on the camsite
  • ​​Lex
  • ​​David
  • ​​Slipper
  • ​​Layne
  • ​​Rahul
  • ​​Arjun
  • ​​Ameen
  • ​​Ensure that all automated release triggers for master​ and develop​ branches are disabled.
  • ​​Merge all work into master​  (and develop​) as necessary across both the camsite​ and contracts​ repositories.
  • ​​booty-development​ merged into develop​
  • ​​develop​ merged into master​
  • ​​Create a release tag from master​ across both the camsite​ and contracts​ repositories.
  • ​​camsite​ release version: v4.0.0​
  • ​​contracts​ release version: v1.0.0​
  • ​​Deploy all contracts to mainnet, and point them to the appropriate owners and tokens. Addresses are below:
​​
​​Contract
​​Address
​​Booty
​​0x6b01c3170ae1efebee1a3159172cb3f7a5ecf9e5
​​Channel Manager
​​0xbf2aeab03b82c182599930217272ef0fc5cf662b
​​Hub Hot Wallet
​​0x526d0cd57a8b977D3628f12cDeceAb12dd49297C (todo rename REB-30)
  • ​​Fund the channel manager contract with BOOTY.
  • ​​Add the contract addresses above to the hub-staging-config.yaml​ and vynos-staging-config.yaml​ files as well as update the Vynos deployment variables to match.

​​Deployment

​​Zoom link: https://zoom.us/j/520134809 (dev zoom)
​​
  • ​​Communicate with any relevant externals that the site is going down for maintenance.
  • ​​Put site in maintenance mode.
  • ​​Deploying
  • ​​Take database backup:
  • ​​Camsite
  • ​​Custodial hub
  • ​​Run the closeAllChannels​ script:
  1. ​​node dist/src/main/spankchain.js closeAllChannels​
  • ​​Run the closeSettlingChannels​. Note: Will likely emit a large number of errors, because since we last run this more people have started using the Unidirectional.sol smart contract than just Spankchain.