MSIG Rollout Process

Owned by Michael Leet
Last updated: Aug 24, 2023
2 min read

This document captures the working notes of rolling out actions to be performed by the BPs. See the Release script template, [Release n.n] Release Script, specifically the account creation, permissions, privilege and ram limit items (part 1 and part 2).

 

Draft process from Eric:

(Assumes items in checklist have been completed up to the msig creation step)

The general process is:

  • Post to the Testnet or Mainnet telegram channel and tag @robDewilder and @BohdanCryptoLions to request new msigs

  • List out the Clio for the actions you need or point them to the release script and let them know which set of msigs they should create

    • Ask the BPs to hold off on executing once the msig is approved.

  • If you do not hear from them in a day or so, ping them to make sure they got the request. Continue until the create the msigs.

  • Once the msigs are created, either:

    • Pin the post from the BP if it contains the right information, or

    • create a new, more detailed, post with all of the information including the msig links and what the msigs are for and pin this post (add links to release hashes, etc. for the other BPs to follow)

  • Once a day post how many have signed the msig and the top21 BPs that have not yet signed. Something like:

BPs, we are at 8/15 for our Testnet msigs: https://fio-test.bloks.io/msig/bsbdk2lectan/updescrow https://fio-test.bloks.io/msig/bsbdk2lectan/updtpid Need 7 more from: 4t1zcuqj34rd  currencyhub@fiotestnet @currencyhub 54givmsg2zii  teamgreymass@fiotestnet @jestagram 5du5xkgkki5x  cryptolions@fiotestnet @BohdanCryptoLions bbislgrjhtpq  eosdac@fiotestnet @michaelyeates ggiqzbabkl3s  everstake@fiotestnet @olya_atticlab ii4x3hj5vvje  alohaeos@fiotestnet @n8dee, @aloha_patrick o5gvcigybyro  blockside@fiotestnet @blockside q34cne24j4co  bp@moonstake 0 sweidrpkehv2  bp@fiosweden @orcus @xebb82 uwqff2yk3sdi  eosamsterdam@fiotestnet @cc32d9 vs3ntpje2dyp  blocksmithio@fiotestnet @tvle83 xbuiswnv5izy  acheron-bp3@fiotestnet 0 yxeiw3p53dns  blockpane@fiotestnet @blockpane

  • This spreadsheet, BP Lookup, has an excel spreadsheet that maps account names to FIO Crypto handles to generate this (FIO Google Sheets Home). Also, it would be fairly straightforward to script the generation of this list from the data found on the “bp.json” files that every BP is supposed to maintain on the website.

  • Once the msig is approved:

  • Send a note to the BPs letting them know when you are going to execute the msigs

  • Either work with a BP to execute, or execute yourself. It may be easier to just do the execution ourselves going forward?

    • I generally DM, on Discord, Todd (@blockpane) and have him execute them so he can also monitor the chain.

    • Additional rigor around this execution process is probably needed.

  • Do any manual validation or testing needed to validate the execution of the script.

    • I made notes in the “release script” file as to which validation I have been doing.

    • If it is a Testnet release, you should also run fio.test > testnet-smoketest.js test with the appropriate parameters after all the msigs have been executed.

  • Once executed and tested, let the BPs know.