Note: if using the full-archive for a history node the following settings should match in the config.ini files:
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
WARNING: these mainnet snapshots were created with a pre-release version of nodeos (v3.0.0-rc5,) and should not be used in production yet!
Here's an example of how to use the light-history full-archive, this is part of a script used for a docker container on first boot. It's a lot of data, and can take as long as 20 minutes to download on a fast connection, but still beats 1-2 days to sync from genesis:
if [ ! -f /var/lib/fio/data/blocks/blocks.log ]; then
pushd /var/tmp >/dev/null
tar -xvS -I'pixz' -C /var/lib/fio -f testnet-latest-history.txz || exit
rm -f testnet-latest-history.txz
Don't pull in an archive when _building_ a container!
Docker/OCI/Podman etc. all use golang, and the stdlib tar package does not properly handle sparse files. It will explode the state file, adding >8gb to the container.
Also available are the block producer rankings used by ([email protected] and [email protected]) the automated proxy-voting system for mainnet and testnet
Lookup FIO domains or addresses, query tables, and more with fio-utils
Provided by: Block Pane, LLC