FIO Chain is a fully decentralized public Delegated Proof of Stake (DPoS) blockchain that is designed specifically to support the the unique usability requirements of the FIO Protocol. It is ran and controller by a diverse group of Block Producers all over the world.
|On-chain fees||Describes on-chain fees and bundled transactions.|
|FIO Token||Describes the native FIO Token.|
|Accounts and permissions||Describes the FIO Chain accounts and how to use permissions.|
|FIO Account Name Hash Function||Describes how FIO Public Key is hashed to FIO Account Name.|
|FIO Public/Private Keys||Describes the FIO Private/Public keys.|
|Encryption in FIO Request and FIO Data||Describes how certain sensitive data is encrypted and decrypted in /new_funds_request and /record_obt_data|
When interacting with the FIO Chain you can access one of the many public FIO Chain nodes ran by the community. However, if you want to be running your own FIO Chain Node, checkout our FIO Chain Node Guide.
Why run your own node?
- Reliability. You can configure your node according to your bandwidth needs and make it available only to your application.
- Security. By keeping the node in your own secure environment you can further enhance the security of reading the chain information.
State Tables hold current state of the blockchain and can be read using the FIO Chain Getters API.
As an example, you can use /get_fio_balance endpoint to look-up the current FIO Token balance for an account.
Historical data, can be read using FIO Chain History API. The data returned includes transactions which were executed in the past.
As an example, you can use /get_actions endpoint to look-up the past FIO Token transactions for an account.
Write Transactions modify data on the FIO Chain and the integrator must have access to user's Private key to properly serialize and sign each transaction. Please see Write Transactions Guide for more details.
Updated 3 months ago