...
Enable FIO Chain upgrades without requiring node upgrades: https://fioprotocol.atlassian.net/browse/WP-430
Simplify API chain code for Signed transactions: https://fioprotocol.atlassian.net/browse/BD-2256
Simplify blockchain code for getter API endpoints: https://fioprotocol.atlassian.net/browse/BD-2254
It also impacts performance and scalability: https://fioprotocol.atlassian.net/browse/BD-3044
Performance analysis of the chain is currently on the roadmap: https://fioprotocol.atlassian.net/browse/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/BD-3120
EOSIO initiatives and issues
https://github.com/dfuse-io/dfuse-eosio
https://eos.io/for-developers/build/demux/
https://github.com/eosnetworkfoundation/mandel/issues/22
Summary of present initiatives and issues
ship data consistency proofs – this would be very beneficial for the FIO off chain state database. We will keep an eye on this and try to meet with Todd Flemming to see if we can get an understanding of the level of interest within EOSIO regarding solving this.
Demux – this effort is perceived as lacking support and momentum.