Configuration Files
To configure the Old Faithful RPC server, you create a YAML configuration file per epoch of data you want the server to support.
You can provide as few or as many epochs as you want, just make sure each has it's own configuration file.
Storage
Store the configuration files on disk in a folder that can be accessed by the Old Faithful binary.
A common folder structure is like this
configs/
epoch-0.yml
epoch-2.yml
epoch-3.yml
...
Old Faithful YAML Config File Format
version
: current version is 1epoch
: the epoch that this config file is for, an Old Faithful server can only host one config per epochgenesis
: (only used for epoch 0), provide a URI to a genesis file if you want to serve epoch 0.data
: retrieval configuration for the block/transaction datacar
: used for Filecoin v1, http, and local file system retrievalsfilecoin
: used for Filecoin v2 retrievals
indexes
: retrieval configuration for the index data (each index header is auri
argument)slot_to_cid
: provide a local file system path or HTTP URI to the slot-to-cid indexcid_to_offset_and_size
: provide a local file system path or HTTP URI to the cid-to-offset-and-size indexsig_to_cid
: provide a local file system path or HTTP URI to the sig-to-cid indexsig_exists
: provide a local file system path or HTTP URI to the sig exists indexgsfa
: provide a local file system path to an unpackedgsfa
index folder.If you want to use a remote URI, you need to start the faithful RPC with
--gsfa-only-signatures.
Last updated