FIO.Relic is the history ecosystem solution for the FIO Blockchain comprised of a FIO Nodeos node providing state history via the state-history plugin, FIO.Chronicle for ingest and processing of that historical data and a relational database for utilization by consumers such as the FIO Dashbboard, a block explorer or any entity desiring relevant FIO historical data. It is based on the opensource product EOS-Chronicle, a middleware app that consumes history data available via the state history plugin of an Antelope (EOSIO) blockchain and provides downstream consumers json formatted data via plugins. In summary, FIO.Relic is the integrated system of applications incorporating the ingest of state history data, as well as the parsing and storage of that data into a relational database for asynchronous consumption by 3rd party applications.
The Foundation for Interwallet Operability (FIO) or, in short, the FIO Protocol, is an open-source project based on EOSIO 1.8+.
- For information on FIO Protocol, visit FIO.
- For information on the FIO Chain, API, and SDKs, including detailed clone, build and deploy instructions, visit FIO Protocol Developer Hub.
- To get updates on the development roadmap, visit FIO Improvement Proposals. Anyone is welcome and encouraged to contribute.
- To contribute, please review Contributing to FIO
- To join the community, visit Discord
Refer to the FIO Protocol Developer Hub documentation to install or attach to an enterprise fio.nodeos blockchain. See the FIO Readme for instructions on how to build and install the FIO Protocol fio.nodeos block chain locally.
See the FIO.Relic Tech Stack document for the requisite hardware and software needed to install and run the FIO.Relic ecosystem
See the FIO.Relic Deployment Guide document for the deployment outline of a FIO History Node, and FIO.Chronicle which includes the RDMS, PostgreSQL.