Index of PATHs

This is an index of all of the filesystem PATHs Cuprate actively uses.

The cuprate_helper::fs module defines the general locations used throughout Cuprate.

dirs is used internally, which follows the PATH standards/conventions on each OS Cuprate supports, i.e.:

Cache

Cuprate's cache directory.

OSPATH
WindowsC:\Users\Alice\AppData\Local\Cuprate\
macOS/Users/Alice/Library/Caches/Cuprate/
Linux/home/alice/.cache/cuprate/

Config

Cuprate's config directory.

OSPATH
WindowsC:\Users\Alice\AppData\Roaming\Cuprate\
macOS/Users/Alice/Library/Application Support/Cuprate/
Linux/home/alice/.config/cuprate/

Data

Cuprate's data directory.

OSPATH
WindowsC:\Users\Alice\AppData\Roaming\Cuprate\
macOS/Users/Alice/Library/Application Support/Cuprate/
Linux/home/alice/.local/share/cuprate/

Blockchain

Cuprate's blockchain directory.

OSPATH
WindowsC:\Users\Alice\AppData\Roaming\Cuprate\blockchain\
macOS/Users/Alice/Library/Application Support/Cuprate/blockchain/
Linux/home/alice/.local/share/cuprate/blockchain/

Transaction pool

Cuprate's transaction pool directory.

OSPATH
WindowsC:\Users\Alice\AppData\Roaming\Cuprate\txpool\
macOS/Users/Alice/Library/Application Support/Cuprate/txpool/
Linux/home/alice/.local/share/cuprate/txpool/

Database

Cuprate's database location/filenames depend on:

  • Which database it is
  • Which backend is being used

cuprate_blockchain files are in the above mentioned blockchain folder.

cuprate_txpool files are in the above mentioned txpool folder.


If the heed backend is being used, these files will be created:

FilenamePurpose
data.mdbMain data file
lock.mdbDatabase lock file

For example: /home/alice/.local/share/cuprate/blockchain/lock.mdb.

If the redb backend is being used, these files will be created:

FilenamePurpose
data.redbMain data file

For example: /home/alice/.local/share/cuprate/txpool/data.redb.

Last change: 2024-10-02, commit: a003e05