...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
...
FIP-39 indicates a RAM increase of 2560 on fio.address (updcryptkey); Is there anything to do here?
FIP-39 createfee for update_encrypt_key has type 1 (in clio command); is this correct? Not sure when type 0 or type 1, etc.
FIP-40: No clearperm addaction, correct? why does fio.devtools have an addaction for this then?
FIP-40: validate setter on new fio.perms contract doesnt need abi/wasm.
FIP-42 indicates new fee for register_fio_domain_address, however, none is specified, what is default?
Overview
This document covers the upgrade to the FIO Protocol release of Fio 3.5 (core) and Fio.Contracts 2.9.
Guidance
For this release, the BPs will execute the MSIGs in 3 parts, as noted by in the section headings: Batch #1, Batch #2, and Batch #3.
Batch #2 msigs can only be created after Batch #1 msigs are executed since they need the fio.perms account to exist in order to set the privilege and RAM limits.
Rollout Guides
...
Overview
This document covers the upgrade to the FIO Protocol release of Fio 3.5 (core) and Fio.Contracts 2.9.
Guidance
For this release, the mSigs will be executed in 3 parts, as noted by in the section headings: Batch #1, and Batch #2, and Batch #3.
Batch #2 msigs may only be executed after Batch #1 msigs are executed since they need the fio.perms account to exist in order to set the privilege and RAM limits.
FIPS & Rollout Guides
https://github.com/fioprotocol/fips
FIP-36 Deployment and rollout guide : Fio (Core) Update (account public key)
...
[FIP-47] Deployment and rollout guide : Fio Contracts Update (use regproducer to update info)
Add new actions (Batch #1)
./clio -u http://localhost:8889 push action eosio addaction '{"action":"newfioacc","contract":"eosio","actor":"eosio"}' --permission eosio
./clio -u http://localhost:8889 push action eosio addaction '{"action":"updcryptkeyregdomadd","contract":"fio.address","actor":"eosio"}' --permission eosio
./clio -u http://localhost:8889 push action eosio addaction '{"action":"addpermupdcryptkey","contract":"fio.permsaddress","actor":"eosio"}' --permission eosio
./clio -u http://localhost:8889 push action eosio addaction '{"action":"rempermaddperm","contract":"fio.perms","actor":"eosio"}' --permission eosio
./clio -u http://localhost:8889 push action eosio addaction '{"action":"clearpermremperm","contract":"fio.perms","actor":"eosio"}' --permission eosio
./clio -u http://localhost:8889 push action eosio addaction '{"action":"regdomaddclearperm","contract":"fio.addressperms","actor":"eosio"}' --permission eosio
...
Validation (Postman): Verify new actions exist using g
Create
...
new fees (Batch #1)
./clio -u http://localhost:8889 push action -f fio.fee createfee '{"end_point":"new_fio_chain_account","type":"0","suf_amount":"2000000000"}' --permission fio.fee@active
...
./clio -u http://localhost:8889 push action -f fio.fee createfee '{"end_point":"remove_fio_permission","type":"0","suf_amount":"1000000000"}' --permission fio.fee@active
./clio -u http://localhost:8889 push action -f fio.fee createfee '{"end_point":"register_fio_domain_address","type":"0","suf_amount":"10000000001183130919351"}' --permission fio.fee@active
Validation:
Postman
https://fiotestnet.greymass.com/v1/chain/get_fee, {“end_point”:”new_fio_chain_account”}
https://fiotestnet.greymass.com/v1/chain/get_fee, {“end_point”:”update_encrypt_key”}
BlockPane Dev Tools
Point to TestNet and set contract=fio.fee and table=fio.feefiofees
Create account and set permissions (Batch #1)
(This must be done before Batch #2 msigs are created)
First, create a file called “payload.json” with the following permissions:
| Code Block |
|---|
{
"creator": "eosio",
"name": "fio.perms",
"owner": {
"threshold": 1,
"keys": [],
"accounts": [{
"permission": {"actor": "eosio", "permission": "active"},
"weight": 1
}],
"waits": []
},
"active": {
"threshold": 1,
"keys": [],
"accounts": [{
"permission": {"actor": "eosio", "permission": "active"},
"weight": 1
},
{
"permission": {"actor": "fio.perms", "permission": "eosio.code"},
"weight": 1
}],
"waits": []
}
}
|
...
|
Next create a new account with those permissions.
./clio -u http://localhost:8889 push action -j -s -d eosio newaccount payload.json -p eosio@active
Validation:
View account Insert Account Creation mSig here and compare to FIO System account (specifically permissions)
System account may be retrieved via Postman at https://fiotestnet.greymass.com/v1/chain/get_account
Add additional new action [See BD-4580] (Batch #2)
./clio -u http://localhost:8889 push action eosio addaction '{"action":"burndomain","contract":"fio.address","actor":"eosio"}' --permission eosio
Create account to be privileged and set RAM limits. (Batch #2)
Set the account to be privileged.
./clio -u http://localhost:8889 push action eosio setpriv '["fio.perms",1]' -p eosio@active
Validation:
Postman
https://fiotestnet.greymass.com/v1/chain/get_account
account = fio.perms
Expected Result: "privileged": true
Remove RAM limits on the new account, this may be called by eosio, and fio.system only!
./clio -u http://localhost:8889 push action eosio setnolimits '{"account":"fio.perms"}' --permission eosio@active
Validation:
Postman
https://fiotestnet.greymass.com/v1/chain/get_account
account = fio.perms
Expected Result: "ram_quota": -1
Deploy EOSIO system contract (Batch #3)
./clio -u http://localhost:8889 set contract -j eosio /opt/FIO/bin/Contracts/last/fio.system fio.system.wasm fio.system.abi -p eosio@active
Deploy any new system contracts and set each contract on the new account (Batch #3)
./clio -u http://localhost:8889 push action -j -s -d eosio newaccount payload.json -p eosio@active
Validation:
View account Insert Account Creation mSig here and compare to FIO System account (specifically permissions)
System account may be retrieved via Postman at https://fiotestnet.greymass.com/v1/chain/get_account
Create account to be privileged and set RAM limits. (Batch #2)
...
set contract -j fio.perms /opt/FIO/bin/Contracts/last/fio.perms -p fio.perms@active
Validation: See Validation Notes above for contract validation
Set all other contracts (Batch #3)
./clio -u http://localhost:8889 set contract -j eosio.msig /opt/FIO/bin/Contracts/last/eosio.msig eosio.msig.wasm eosio.msig.abi -p eosio.msig@active
./clio -u http://localhost:8889 push action eosio setpriv '["fio.perms",1]' -p eosio@active
Validation:
Postman
https://fiotestnet.greymass.com/v1/chain/get_account
account = fio.perms
Expected Result: "privileged": true
...
set contract -j fio.address /opt/FIO/bin/Contracts/last/fio.address fio.address.wasm fio.address.abi -p fio.address@active
./clio -u http://localhost:8889 push action eosio setnolimits '{"account":"fio.perms"}' --permission eosio@active
Validation:
Postman
https://fiotestnet.greymass.com/v1/chain/get_account
account = fio.perms
Expected Result: "ram_quota": -1
...
set contract -j fio.escrow /opt/FIO/bin/Contracts/last/fio.escrow fio.escrow.wasm fio.escrow.abi -p fio.escrow@active
./clio -u http://localhost:8889 set contract -j fio.oracle /opt/FIO/bin/Contracts/last/fio.oracle fio.oracle.wasm fio.oracle.abi -p fio.oracle@active
./clio -u http://localhost:8889 set contract -j eosio fio.reqobt /opt/FIO/bin/Contracts/last/fio.request.system obt fio.request.systemobt.wasm fio.request.systemobt.abi -p eosio@active
...
fio.reqobt@active
./clio -u http://localhost:8889 set contract -j fio.perms staking /opt/FIO/bin/Contracts/last/fio.perms /last/fio.staking fio.staking.wasm fio.staking.abi -p fio.perms@active
Validation: See Validation Notes above for contract validation
Set all other contracts (Batch #3)
staking@active
./clio -u http://localhost:8889 set contract -j fio.address token /opt/FIO/bin/Contracts/last/fio.address token fio.addresstoken.wasm fio.addresstoken.abi -p fio.address@activetoken@active
./clio -u http://localhost:8889 set contract -j fio.reqobt tpid /opt/FIO/bin/Contracts/last/fio.reqobt tpid fio.reqobttpid.wasm fio.reqobttpid.abi -p fio.reqobt@activetpid@active
./clio -u http://localhost:8889 set contract -j fio.token treasury /opt/FIO/bin/Contracts/last/fio.token treasury fio.tokentreasury.wasm fio.tokentreasury.abi -p fio.token@activetreasury@active
Validation: See Validation Notes above for contract validation
...
TESTNET: ./clio.sh push action fio.escrow setmrkplcfg '{"actor":"p325sqluvj4u", "listing_fee": "5000000000", "commission_fee": 3, "max_fee": "1000000000", "e_break": 0}' -p eosio@active
MAINNET: ./clio.sh push action fio.escrow setmrkplcfg '{"actor":"q3k31xlj413z", "listing_fee": "5000000000", "commission_fee": 3, "max_fee": "1000000000", "e_break": 0}' -p eosio@active
Validation: check fio.escrow mrkplconfigs table to confirm account was added
Testnet example:https://fio-test.bloks.io/msig/bsbdk2lectan/setmrkplcfg
TODO: Remove once script is finalized.
Examples
Fee: Testnet example: https://fio-test.bloks.io/msig/gws1hlwlqhq1/fiocreatefee
New Account: Testnet example: https://fio-test.bloks.io/msig/bsbdk2lectan/crtfioescrow2
Privileges: Testnet example: https://fio-test.bloks.io/msig/un3emex141fp/setpriv.a
Contract Update: Testnet example: https://fio-test.bloks.io/msig/bsbdk2lectan/updfiosys
Set contract on Account: Testnet example: https://fio-test.bloks.io/msig/bsbdk2lectan/crtfioesc
Marketplace Account: Testnet example: https://fio-test.bloks.io/msig/bsbdk2lectan/setmrkplcfg
...