...

• transfer-tokens.js

Plan: create new record-obt-data.js test:

• Test single recordobt with bundles

  • Send FIO with Memo

  • Confirm get_obt_data returns correct record for payee and payer

  • Confirm content can be decrypted by payee

    • Include correct content for each content field and confirm it can be read by payee

  • Confirm status field for payee and payer

  • Confirm 2 bundles are deducted

• Test single recordobt with no bundles

  • Same test as above, but with no bundles remaining

• Error testing

  • Send with large content field that is too large

  • record obt with:

    • badly formatted payer_fio_address and payee_fio_address

    • Send character string to fio_request_id

    • payee_fio_public_key that does not own the the payee_fio_address

• Paging testing

...

This is not a forking change since users on current chain code and new chain code will maintain the same state. What changes in the new chain code is how the FIO Request getters work. In the current code, they call into the current tables. In the new chain code, they will call into the new tables. So, wallets that point to an API that has not upgraded will eventually get null data once we fully transfer over to the new tables and delete the old ones. We will maintain both tables for a time, but at some point we will do a contact msig that deletes the old table. So, we do not need a date in the chain code, the break will come when we do the msig.

Rollout/Release Plan

Contracts Release 1 - fio.contracts (Bravo

...

)

After this update and the initial call to migrtrx, new Request and OBT data coming in will be entered into both the old and new tables.

Step 1 introduces the new table structure and adds a new “temporary” action call called migrtrx. This action enables the top 21 block producers to start migrating existing data over to the new formatted index tables.

This will migrate the three current tables (fioreqctxts, recordobts, fioreqstss) into two new tables (fiotrxts, reqledgers). It also creates and uses a temporary table (migrledgers) that is used during the migration process.

...

[FIP-1.b] Step 1: Add continuous migration of request and obt data (FIO #182)

The complete migration of data has to happen before fio chain is released. An off chain validation should be done to confirm this.

Note that the partial implementation of transfer address (https://fioprotocol.atlassian.net/browse/BD-2232 ) will work after Step 1.

...

Contracts Release 1.b

Do the migration process:

• Call migrtrx repeatedly

• After the first call, new requests and OBTs should be added to both tables. (Test)

• migrtrx is also used to check status updates.

Created test for initial migration: fio.test bravo-migr-test.js

Chain Release 1 - fio chain (

...

Bahamas)

Step 2 updates the getters (e.g., get_xyz_fio_requests)

Users pointing to non-upgraded nodes will be retrieving data from the old tables and users pointing to upgraded nodes will be retrieving data from the new tables.

Contracts Release

...

Part 2 - fio.contracts (

...

migr/part2)

All fio chain nodes should be upgraded prior to rolling out Contract Step 2.

Step 2 does two things:

• Modifies the Request code to stop updating the old tables. After this release, only the new tables will get updated.

• Modifies the  migrtrx call. It will now remove data from the old tables.

...

• New OBT and Requests will be put into the new tables

• Get requests and OBT getters will point to the old tables so they will get “no request found” or the OBT data will not be found results.

Contracts Release

...

Part 3 - fio.contracts (

...

migr/part3-

...

final)

Step 3 includes:

• The removal of migrtrx temp action

• Removes old table references (fioreqctxts, recordobts, fioreqstss)

...

Release Verification Plan

Casey Gardiner Need this. Add info on your scripts that will verify data, etc.