|
8 | 8 |
|
9 | 9 | - [Multi-wallet environment](#multi-wallet-environment)
|
10 | 10 |
|
| 11 | + - [Berkeley DB database based wallets](#berkeley-db-database-based-wallets) |
| 12 | + |
| 13 | + - [SQLite database based wallets](#sqlite-database-based-wallets) |
| 14 | + |
11 | 15 | - [GUI settings](#gui-settings)
|
12 | 16 |
|
13 | 17 | - [Legacy subdirectories and files](#legacy-subdirectories-and-files)
|
@@ -66,26 +70,36 @@ Subdirectory | File(s) | Description
|
66 | 70 |
|
67 | 71 | ## Multi-wallet environment
|
68 | 72 |
|
69 |
| -Wallets are Berkeley DB (BDB) databases: |
| 73 | +Wallets are Berkeley DB (BDB) or SQLite databases. |
70 | 74 |
|
71 |
| -Subdirectory | File(s) | Description |
72 |
| --------------|-------------------|------------ |
73 |
| -`database/` | BDB logging files | Part of BDB environment; created at start and deleted on shutdown; a user *must keep it as safe* as personal wallet `wallet.dat` |
74 |
| -`./` | `db.log` | BDB error file |
75 |
| -`./` | `wallet.dat` | Personal wallet with keys and transactions. May be either a Berkeley DB or SQLite database file. |
76 |
| -`./` | `.walletlock` | Wallet lock file |
77 |
| -`./` | `wallet.dat-journal` | SQLite Rollback Journal file for `wallet.dat`. Usually created at start and deleted on shutdown. A user *must keep it as safe* as the `wallet.dat` file. |
78 |
| - |
79 |
| -1. Each user-defined wallet named "wallet_name" resides in `wallets/wallet_name/` subdirectory. |
| 75 | +1. Each user-defined wallet named "wallet_name" resides in the `wallets/wallet_name/` subdirectory. |
80 | 76 |
|
81 | 77 | 2. The default (unnamed) wallet resides in `wallets/` subdirectory; if the latter does not exist, the wallet resides in the data directory.
|
82 | 78 |
|
83 |
| -3. A wallet database path can be specified by `-wallet` option. |
| 79 | +3. A wallet database path can be specified with the `-wallet` option. |
84 | 80 |
|
85 | 81 | 4. `wallet.dat` files must not be shared across different node instances, as that can result in key-reuse and double-spends due the lack of synchronization between instances.
|
86 | 82 |
|
87 | 83 | 5. Any copy or backup of the wallet should be done through a `backupwallet` call in order to update and lock the wallet, preventing any file corruption caused by updates during the copy.
|
88 | 84 |
|
| 85 | + |
| 86 | +### Berkeley DB database based wallets |
| 87 | + |
| 88 | +Subdirectory | File(s) | Description |
| 89 | +-------------|-------------------|------------- |
| 90 | +`database/` | BDB logging files | Part of BDB environment; created at start and deleted on shutdown; a user *must keep it as safe* as personal wallet `wallet.dat` |
| 91 | +`./` | `db.log` | BDB error file |
| 92 | +`./` | `wallet.dat` | Personal wallet (a BDB database) with keys and transactions |
| 93 | +`./` | `.walletlock` | BDB wallet lock file |
| 94 | + |
| 95 | +### SQLite database based wallets |
| 96 | + |
| 97 | +Subdirectory | File | Description |
| 98 | +-------------|----------------------|------------- |
| 99 | +`./` | `wallet.dat` | Personal wallet (a SQLite database) with keys and transactions |
| 100 | +`./` | `wallet.dat-journal` | SQLite Rollback Journal file for `wallet.dat`. Usually created at start and deleted on shutdown. A user *must keep it as safe* as the `wallet.dat` file. |
| 101 | + |
| 102 | + |
89 | 103 | ## GUI settings
|
90 | 104 |
|
91 | 105 | `bitcoin-qt` uses [`QSettings`](https://doc.qt.io/qt-5/qsettings.html) class; this implies platform-specific [locations where application settings are stored](https://doc.qt.io/qt-5/qsettings.html#locations-where-application-settings-are-stored).
|
|
0 commit comments