Where Does a Cashu Mint Store Data?
Cashu mints keep keys in env with a SQLite or Postgres database. Backup set and key rotation notes.
Last updated
A Cashu mint guards two things: the private key that defines its identity and the database tracking issued ecash. Keys and Lightning credentials live in the env file from the example template. The database defaults to a SQLite directory in the checkout, swappable for Postgres.
Losing either half ends the mint. Without the key and derivation path, outstanding ecash becomes unredeemable; without the database, spent tracking vanishes. Docker deployments configure purely through env names. Wallet data is separate under the Cashu home dir and never substitutes for mint files.
Where Cashu stores this, by platform
<nutshell-checkout>/data/mint/mint.sqlite3
SQLite mint database by default with Postgres URL alternative. Env at .env holds MINT_PRIVATE_KEY, derivation path and backend creds. Wallet CLI state under ~/.cashu stays separate. Back up env plus database together.
Frequently asked questions
What must a Cashu mint backup include?
The env file with the mint private key and derivation path plus the mint database directory or dump. Keys without history cannot verify spends; history without keys cannot sign. Keep both offline and encrypted.
How do Cashu keysets rotate?
By deriving a new path while keeping old keys for redeeming outstanding ecash. Never delete retired keys until their tokens expire. Announce rotations so wallets fetch fresh keysets.
Where is the Cashu wallet database?
Under the Cashu home directory, separate from any mint database on the same box. Wallets and mints share tooling but never state. Back them up as independent units.
Notice an outdated path? Let us know.