FIO Snapshots
These archives are used by a set of Docker images that can greatly expedite getting a fully-synced and working node
Mainnet Files
List of all snapshots / archives
| Type | Size | File |
|---|---|---|
| Latest history archive | ~16GB | mainnet-latest-history.txz |
| Latest blocks.log and snapshot | ~14GB | mainnet-latest-blocks.txz |
| Latest snapshot only | ~145MB | mainnet-latest-snap.txz |
Testnet Files
List of all snapshots / archives
| Type | Size | File |
|---|---|---|
| Latest history archive | ~13GB | testnet-latest-history.txz |
| Latest blocks.log and snapshot | ~13GB | testnet-latest-blocks.txz |
| Latest snapshot only | ~9MB | testnet-latest-snap.txz |
Notes
- These are snapshots of the FIO Protocol chain.
- The script used to create these is available on github.
- There are three types of archives here: a full archive of a light-history node, an archive of the blocks.log with a snapshot, and a snapshot only.
- The files are updated daily
- These were taken from a pinned version of “nodeos”. The state file may not be compatible if nodeos was compiled with different settings (only applies to full archive,) but using the snapshot should allow working around this issue.
Use the following settings for a history node:
chain-state-db-size-mb = 8192
reversible-blocks-db-size-mb = 1024
plugin = eosio::history_plugin
plugin = eosio::history_api_plugin
filter-on = *
filter-out = eosio:onblock:
history-per-account = 9223372036854775807
history-index-state-db-size-mb = 1000000
history-state-db-size-mb = 4000000
- It’s important to untar the files using the sparse flag (-S), or the state file will be exploded to the full 8GB. These were xz compressed using ‘pixz’. Example of extracting the archive:
tar -xvS -I'pixz' -C /var/lib/fio -f testnet-latest-history.txz
