...
This document discusses the benefits and advantages of providing the FIO protocol with an off-chain state database. This database is envisioned as containing both FIO protocol state information, as well as supplemental information that enriches the FIO user experience.
Staffing and Duration Considerations
This project is complex and may require dedicated core engineering team focus.
to adequately identify resources it will be best to establish the scope of the project and perform a staffing analysis after the scope is agreed. These positions listed are based upon assumptions of max scope.
tech oversight of the FIO lead architect. (50% of available bandwidth)
this project will require a database architect, this is a full time roll 180k base and 40k incentive per year.
this project may also require a distributed database administrator/egineer. 120k base and 40k incentive per year.
Background
Ledger technology implemented on the EOSIO platform has limited query-ability. The state model which is represented in the chains state table structure is not query-able using SQL like queries. A secondary concern is that the state model represented on chain cannot be supplemented with additional information targeted to enrich the user experience. The maintainability of the chain, and the performance of the chain both can become encumbered when state becomes too large, or too complex/varied in its structure. Transaction processing (and thus block production) become encumbered as the size and complexity of state grows.
...
Initiative tracking State and CPU Optimization: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key WP-119 Grab bag of past requests that somewhat fit under State and CPU Optimization: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-1121
Enable FIO Chain upgrades without requiring node upgrades: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key WP-430 Simplify API chain code for Signed transactions: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-2256 Simplify blockchain code for getter API endpoints: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-2254 It also impacts performance and scalability: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-3044 Performance analysis of the chain is currently on the roadmap: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key WP-777 Currently there are several different “history API” options for FIO (V1 History, Hyperion). We have a story to figure out what our strategy is to support exchanges who rely on history to track transactions: https://fioprotocol.atlassian.net/browse/
Jira Legacy server System JIRA serverId 5f0d8161-d4cf-3d17-96b1-53b2b2b5013d key BD-3120
EOSIO initiatives and issues
...