Where Does Fedimint Store Guardian Data?
Fedimint guardians keep config files with a database in a data dir you choose. Files and backup notes.
Last updated
Fedimint stores guardian state in a data directory chosen at deploy time, not a fixed system path. Docker examples mount it at /data while native runs default nearby. Inside sit the federation config set, the invite code file and the database directory.
Filenames stay stable across deploys even as host paths vary, so guides quoting /data describe the common example rather than a rule. Back up the entire directory with private config and database together. Legacy password and salt files appear on older setups beside the current names.
Where Fedimint stores this, by platform
$FM_DATA_DIR (e.g. /data in Docker)
Holds consensus, local, private and client JSON configs with the invite-code file and database directory. Set with --data-dir or FM_DATA_DIR env. Native default is ./data. Back up the whole dir; private config plus database travel as one.
Frequently asked questions
What must a Fedimint backup include?
The entire data directory: federation configs, private material and the database folder. Partial copies orphan the federation state. Keep encrypted offline copies with the same care as mint keys.
Where is the Fedimint database?
In the database directory inside the data dir by database file constant. It rebuilds only through federation consensus, never from scratch locally. Copy it stopped for consistent snapshots.
Why do guides show different Fedimint paths?
The data dir is operator-chosen per deploy, so /data, ./data and custom mounts all appear. Filenames inside stay constant. Match backup scripts to your own data-dir flag rather than any single guide path.
Notice an outdated path? Let us know.