Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Table of Contents

...

  1. Verify voters2 table contents match what was in voters before the migration

  2. Register a producer

  3. Register fio_address for producer

  4. Vote for the producer

  5. Verify owner and fio_address are populated as a voter in the accounts voters2 record

  6. Verify voting still works and no regression

Plan:

  • TODO: Add the post table migration tests above to vote.js. Confirm running them at all phases of contract rollout.

Performance Testing plan

  • Voteproducer stress testing should be done on voters table before the migration, then voter2 table after the migration. Results will be compared.

  • Tests carried out on devnet, testnet before deployment to mainnet

...

  • Chain_plugin update must be released first so more block producers are able to support the new voters table before the contract update has been rolled out

  • For Testnet and Mainnet release, confirm that bloks.io is accessing either the new Table, or getting voter information from the account record.

  • Work with BPs to update any tools that point to the voters table.

Rollout/Release verification plan

...