There are a number of paths to set up a FIO Chain Node. This section walks through several paths for different types of users. We encourage you to ask questions about block production, running an API node, and any other node-related questions in the FIO Mainnet Telegram channel.
nodeosis the core service daemon that runs on every FIO Chain node. It can be configured to process smart contracts, validate transactions, produce blocks containing valid transactions, and confirm blocks to record them on the blockchain.
This section contains the following content:
|Installation Using Packages||This is the simplest method for installing a FIO API node. This install method does not require Docker and describes how to manually install and sync a FIO API node.|
|Docker installation||This is the fastest method for installing a FIO API node. It leverages Docker to install FIO .deb files.|
|Build from source||Describes how to compile and build a node from source. Building from source is only recommended for Producers and other advanced developers.|
|Enable fio-wallet||Important information if you use the fio-wallet (keosd) to manage your user's keys.|
|Enable V1 History||Configuration information if the light-history (v1 history) feature is needed.|
|Nodeos Replay||Instructions on speeding up node setup by replaying from a snapshot, blocks.log, or V1 History archive.|
|Validate Your Node||Information on validating your node once you have it up and running.|
|Summary Script||Script to perform a manual installation of the FIO blockchain with optional snapshot/history startup.|
|Uninstall and Cleanup||Instructions on how to remove a FIO installation and cleanup your node of FIO install artifacts.|
|FIO Chain Getter API||FIO Chain Getter API offers multiple endpoints design to return information about the FIO Chain or specific FIO Handles, FIO Requests, FIO Data, NFT Signatures, or FIO Chain accounts.|
|FIO Chain V1 History API||FIO Chain V1 History API offers returns historical information about FIO Chain transactions.|
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 about 1 month ago