Page Comparison

Problem: Update architecture for FIP-1 to include the ability to page and cache data on wallets

...

This new contract update will be proposed via msig to the protocol. This will finalize all necessary changes to complete the transfer of FIO domains and addresses while maintaining request integrity. 

Release Plan

...

Release 1

...

- fio.contracts (Bravo-

...

c1)

After this update, 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.

...

[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.

Release 2 - fio chain

...

(Bravo-chain)

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.

...

Release 3 - fio.contracts (Bravo-c2)

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.

...

Release 4 - fio.contracts (Bravo-c3)

Step 3 includes:

• The removal of migrtrx temp action

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

...