Page Comparison

...

1. We desire ease of readability for FIO state and supplemental information.

2. We desire ease of deployability and increased manageability.

   1. For BPs.

      1. ease of playback.

      2. ease of data capture.

      3. ease of management of operational data.

   2. For integrators, we want to free them of the burden of having to upgrade nodes every time new feature function is added to the FIO protocol.

3. We desire to increase FIO protocol performance.

   1. decrease size and complexity of all on chain state data.

      1. increase query performance.

      2. increase transaction performance when making blocks

      3. increase max users capability

      4. increase max volume capability.

      5. there are other perf advantages we can list that come from decreasing/optimizing state size.

4. We desire to add supplemental information to whatever data model we provide for off chain state.

   1. We want to provide a state model that allows on chain state size to be reduced significantly.

5. We want to provide a scalable and robust solution for populating off chain state.

   1. programs populating offline data should not become overwhelmed as volume of transactions increases.

   2. add programs populating offline data easily as volume increases

6. We want to consider as many existing tactics, approaches, and solutions to integrating EOSIO chains with offline data analysis as possible.

7. We desire to maintain, or increase FIO/EOSIO maintainability.

   1. make sure we use EOSIO tactics preferentially.

   2. always try to maintain merge-ability of FIO Core to and from EOSIO.

8. We want to support all manner of offline analytics (grafana, and others).

9. Verifiability – we must be able to verify that the offline data matches what is in state on the chain at any time.

10. Authorization – we may need to consider additional authorization models to permit the update of data associated with state data stored off chain.

Existing FIO initiatives

This impacts some of our projects aimed at updating state, chain code, and aligning FIO with eosio code base to simplify future upgrades and integrations:

...