This PR:
- provides detailed info about the Bitcoin Core files;
- does not mention temporary files, e.g.,
mempool.dat.newandpeers.????
This PR:
mempool.dat.new and peers.????Overall LGTM. Could mention in PR/commit description that references to 0.8.0 are dropped.
Could mention in PR/commit description that references to 0.8.0 are dropped.
The PR description has been updated.
PR/commit description that references to 0.8.0 are dropped.
I think it makes sense to keep a list the "legacy files" somewhere, so that people encountering them (in old installs) have something to search for, and know they are no longer necessary and can be removed. Even if you drop mention of exact versions and meanings.
I think it makes sense to keep a list the "legacy files" somewhere, so that people encountering them (in old installs) have something to search for, and know they are no longer necessary and can be removed. Even if you drop mention of exact versions and meanings.
Agree. Currently a user can choose any branch from 0.14 to 0.18 in GitHub web interface. Could it be "somewhere" that keeps a list of legacy files?
Please keep it in this document.
Please keep it in this document.
Done.
Concept ACK.
I like the direction of this @hebasto. Some suggestions:
holds->containscustom->custom format, could even link or add information about the formatblock chain->blockchainbitcoin.conf could have a reference to the example (share/examples/bitcoin.conf)database/ contains data, not BDB logsDescriptiondatadir/ and wallet_name as literals is confusing* NOTE: could be a blockquote or footnote; regexp->regex** NOTE: could be a blockquote or footnote, or maybe inlinedblocks/index/: How do I set a custom path via CLI?No option could spell out the -mainnet flagAlso, here's another interpretation of the table of contents / section titles, if useful:
1. Datadir location
2. Datadir layout
3. Wallet files
- Default, single wallet layout
- Multi-wallet layout
4. Other files
- QSettings
5. Legacy files and directories
database/contains data, notBDB logs
Considering: https://github.com/bitcoin/bitcoin/blob/30c2b0b1cb110c27e329e453210561ea5dcdbeb5/src/wallet/db.cpp#L190
and https://docs.oracle.com/cd/E17076_01/html/api_reference/C/envset_lg_dir.html, I believe the contents of the database/ are BDB logging files.
BDB log files are part of the data though—comparable with the journal in file systems, not as in the debug log (which means, most importantly, that it is not safe to just erase them).
@ch4ot1c The most part of your suggestions has been implemented. Didn't catch the last two of them:
blocks/index/: How do I set a custom path via CLI?Chain option
No optioncould spell out the-mainnetflag
Would you mind re-wording your ideas?
Sure -
blocks/index/ - Block index; `-blocksdir` option does not affect this path - how do I affect this path?no option (mainnet)->No option (or `-mainnet`)* `blocks/index/` - `` Block index; `-blocksdir` option does not affect this path `` - how _do_ I affect this path?
Considering: https://github.com/bitcoin/bitcoin/blob/94d6a18f23ec1add600f04fc7bd0808b7384d829/src/txdb.cpp#L148-L149
there is no way to affect blocks/index/ path.
* `no option (mainnet)`->`` No option (or `-mainnet`) ``
Do we have -mainnet as command-line option?
-chain=main, but no. Good notes - thanks for mentioning!
ACK 86b9f92
Concept ACK
129 | +`blk000?.dat` | Block data (custom format, 2 GiB per file); replaced by `blocks/blkNNNNN.dat`<sup>[\[2\]](#note2)</sup> in 0.8.0 | [PR #1677](https://github.com/bitcoin/bitcoin/pull/1677) 130 | +`addr.dat` | Peer IP address BDB database; replaced by `peers.dat` in [0.7.0](https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.7.0.md) | [PR #1198](https://github.com/bitcoin/bitcoin/pull/1198), [`928d3a01`](https://github.com/bitcoin/bitcoin/commit/928d3a011cc66c7f907c4d053f674ea77dc611cc) 131 | + 132 | +## Notes 133 | + 134 | +<a name="note1">1</a>. The `/` (slash, U+002F) is used as the platform-independent path component separator in this paper.
lol @ "in this paper"
ACK 86b9f92da25f2768eb29eefd6526320135f39a2f this is much of an improvement
ACK 86b9f92da25f2768eb29eefd6526320135f39a2f
<details><summary>Show signature and timestamp</summary>
Signature:
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
ACK 86b9f92da25f2768eb29eefd6526320135f39a2f
-----BEGIN PGP SIGNATURE-----
iQGzBAEBCgAdFiEE+rVPoUahrI9sLGYTzit1aX5ppUgFAlwqrYAACgkQzit1aX5p
pUjztQv/cnmPIi2I/WrLg8Tbaj6N4ylQOGWWCt/nMyczT7sjGw1f3x8TP8d9yvi+
s7SJT+IlpBcAZXWsm7RhaCOM9R1K/1dtazMM/ZChKGfVJ+8Ey8KTfSEwayfORkDD
fTBen4typXXyHhAzoyLyTAr35vEH/DoFS8MtBD/Rm48Mo4HgY2DVBfAL8DhpXqVE
AOyJV1GGMKwsAvmoLpJpieSkBzdugxN7x9zwfH9rCKa9F6yUGmLG0Y8W/gMQ4Zfn
5xEHE1BqW9FOzWHWjk32mZN3DsTsbZvfwdaDQ3N/2sYFbcxU/1RT5rCbKdeJIV1l
X2sLXs0yJC7CTa+9OHwlrPpzJtr6Rcua/VpnR4qRJaU+4G0mX0k1mmmaPx1HW4Lt
hOvwuPgOM5QtGnodZI32alYzkLx8qOkbpolPMmYULMS1zGU1IuhIdKO5sUpBJLAo
MdUEGA4xnofNlflcGEY+gkpMAtKaj4cXjLOUnx0mlWXICQL7etdWCYBlaOdNezbx
w8YoInm9
=LO4O
-----END PGP SIGNATURE-----
Timestamp of file with hash 9f2ff8ea4a42ee5db2f108e51e215fb6faf8857556cb207b0fe9722786a9906b -
</details>