Configuration File Location
You can specify your configuration file in two ways:- Set the
FIREDANCER_CONFIG_TOMLenvironment variable - Pass it to commands with the
--configoption
The same configuration file must be supplied to all commands, especially when configuring and later running the validator. Using a different file for different commands may cause them to fail.
Basic Configuration Example
An example TOML file overriding select options needed for a new validator on testnet:Core Configuration Fields
Name of this Firedancer instance. This name serves as a unique token so that multiple Firedancer instances can run side by side without conflicting when they need to share a system or kernel namespace.
The operating system user to permission data and run Firedancer as. Firedancer will automatically determine a user to run as if none is provided. The user should be minimally permissioned and never a superuser or root.
Absolute directory path to place scratch files used during setup and operation. The ledger and accounts databases will also be placed in here by default. Supports
{user} and {name} substitutions.Port range used for various incoming network listeners, in the form
<MIN_PORT>-<MAX_PORT> inclusive. This port range should NOT overlap with any of the static ports used by Firedancer.Migrating from Agave
Firedancer translates many configuration options to Agave command line arguments internally, allowing you to configure everything in one place.Logging Configuration
By default Firedancer maintains two logs:- Permanent log: Written to a file for long-term archival
- Ephemeral log: Written to stderr for fast visual inspection
Next Steps
Consensus Configuration
Configure validator identity, voting, and consensus parameters
Network Configuration
Set up network interfaces, XDP, and bandwidth settings
RPC Configuration
Enable and configure JSON RPC and WebSocket APIs
Ledger Configuration
Configure ledger storage, snapshots, and accounts