...
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.
a fee was added for the new endpoint update_encrypt_key
Contracts for deployment
insert information about all contract changes for this projectfio repo new getter and endoint added, branch name is indicated in dev spec
Actions added
none
Fees added
none
Contracts for deployment
none
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
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!!!!)none