Page Comparison

This document contains notes on the TestNet release process, specifically mSig request, creation, and execution. As much of this process is performed by a BP, this document captures those things a FIO core chain member might do to monitor “addaction”, “createfee”, “set contract” and account creation on TestNet

...

Refer to FIO 3.4/FIO Contracts 2.8 Release Script as it contains much of the information that will be included here.

Outline

• Based on the release Release Script, a request is sent on the Telegram TestNet channel to create the mSigs. Currently Rob (@robDewilder) and Bohdan (@bohdanCryptoLions) are the POCs for this activity. See FIO 3.4/Contracts 2.8 mSig creation request .

• mSigs are created and posted to the FIO POCs (currently Eric Butz, Michael Leet) on the TestNet channel.

• mSigs are reviewedRequests are sent ; matches request, expiry date.

• Formalized request is sent to BPs on the TestNet channel to sign the mSigs (Generally currently there are 30 default approvers, 15 signatures are needed (2/3 of 21 + 1)). See FIO 3.4/Contracts 2.8 mSig notification to BPs

• Once mSigs are approved, a BP will execute them. Rob at BlockPane usually performs this activity.

  • While he usually does this himself it is possible to co-monitor this activity via Zoom or Discord

Example TestNet mSig Proposals:

• FIP-41 Add Actions mSig

• FIP-17 Add Actions mSig

• FIP-17 Account Creation mSig

• FIP-17 Create Fee mSig

• FIP-17 Account Ram Limit Removal

• FIP-17 Set Account Privilege

Execution Notes:

• BP may execute msigs via links above*

Validation Notes:

• For addaction and , createfee, set contract actions, view transaction (after execution)

  • View transaction details, click ‘Block Number’, then confirm that next block is produced by clicking ‘Next’

    Image Removed

    Image Added

  • View the Block Information details (Raw tab) and expand all nodes to locate any errors. For example, note the ‘transactions’ node below:

  • Image Added

• For contract deployment (set contract) validation, run fio.devtools “Contract Hashes” query to confirm ABI and contract hashes match.

• Use Aloha EOS TestNet Producer Reliability Tracker to verify that no blocks are missed. Note, missed rounds will result in a post to the Telegram TestNet channel.

• Use FioTop and FioWatch tool to check transactiontools to watch/view transactions

  • fio-tools/fio-top at master · blockpane/fio-tools (github.com)

  • blockpane/fiowatch: GUI network monitor for FIO (github.com)

• Validate new actions using Postname with api Postman

  • https://fiotestnet.greymass.com/v1/chain/get_actions

• Validate new fees using:

  • Postman

    • https://fiotestnet.greymass.com/v1/chain/get_fee

      • Example endpoint: {“end_point”:”wrap_fio_domain”}

    • https://fiotestnet.greymass.com/v1/chain/get_table_rows

    BlockPane Dev

    • • This may return many rows and it may be difficult to locate the data in a timely fashion.

  • BlockPane UI Tools

    • FIO Tools (blockpane.com)

      • Point to TestNet and set contract=fio.fee and table=fio.fee

• Validate new account creation:

  • View account new account mSig transaction and compare to FIO System account (specifically permissions)

  • System account may be retrieved via Postman at https://fiotestnet.greymass.com/v1/chain/get_account

    • account = fio.system

• Validate account privilege information using Postman with API https://fiotestnet.greymass.com/v1/chain/get_account

  • account = fio.<account>

  • Expected Result: "privileged": true

• Validate account ram information using Postman with API https://fiotestnet.greymass.com/v1/chain/get_account

  • account = fio.<account>

  • Expected Result: "ram_quota": -1