FIPs 36-39 Deployment and rollout guide

This document will contain the working instructions for deploying FIPs 36-40 onto the main net version of the FIO core and FIO contracts. Any issues discovered will be included here.

Branches used in rollout testing

Actions added

newfioacc action added to the fio.system contract (eosio account).

updcryptkey action added to the fio.address contractt (fio.address account).

Fees added

a fee was added for the new endpoint new_fio_chain_account. the fee should be set to equal transfer tokens pub key.

a fee was added for the new endpoint update_encrypt_key, the fee should be set up to be same as register FIO Address at deployment

Contracts for deployment

insert information about all contract changes for this project

Hashes from local dev env

Instructions for contract rollout

insert detailed command line instructions using CLIO for rollout of the contracts for this project.

consider any dependencies required for the rollout.

Accounts

Actions

#FIP-38 begin
./clio -u http://$host push action eosio addaction '{"action":"newfioacc","contract":"eosio","actor":"eosio"}' --permission eosio
#FIP-38 end

Fees

#FIP-38 begin new_fio_chain_account
./clio -u http://localhost:8879 push action -f fio.fee createfee '{"end_point":"new_fio_chain_account","type":"0","suf_amount":"2000000000"}' --permission fio.fee@active
#FIP-38 end

#FIP-39 begin update_encrypt_key

./clio -u http://localhost:8879 push action -f fio.fee createfee '{"end_point":"update_encrypt_key","type":"0","suf_amount":"40000000000"}' --permission fio.fee@active

#FIP-39 end

Contracts to update

Contracts analysis

Summary of changes to each contract, and a statement of what changes MUST be achieved together.

Release manage TODO – (how do we roll back when a deployment goes bad!!!!)