arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-22 08:08:11 +00:00
Code Issues Releases Wiki Activity

Edited ch03_bitcoin-core.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-28 18:18:51 +00:00
parent 2473e0ce5c
commit e02ccdf22d
1 changed files with 9 additions and 9 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

18
ch03_bitcoin-core.adoc
View File

@ -478,47 +478,47 @@ Here are some of
the most important options that you can set in the configuration file,
or as command-line parameters to +bitcoind+:
++alertnotify++:: Run ((("alertnotify option (bitcoind command)")))a specified command or script to send emergency alerts
++alertnotify++:: Run ((("alertnotify option (bitcoind option)")))a specified command or script to send emergency alerts
to the owner of this node.
++conf++:: An ((("conf option (bitcoind command)")))alternative location for the configuration file. This only
++conf++:: An ((("conf option (bitcoind option)")))alternative location for the configuration file. This only
makes sense as a command-line parameter to +bitcoind+, as it can't be
inside the configuration file it refers to.
++datadir++:: Select((("datadir option (bitcoind command)"))) the directory and filesystem in which to put all the
++datadir++:: Select((("datadir option (bitcoind option)"))) the directory and filesystem in which to put all the
blockchain data. By default this is the _.bitcoin_ subdirectory of your
home directory. Depending on your configuration, this can use from about 10
GB to almost 1 TB as of this writing, with the maximum size
expected to increase by several hundred gigabytes per year.
++prune++:: Reduce the((("prune option (bitcoind command)"))) blockchain disk space requirements to this many megabytes by
++prune++:: Reduce the((("prune option (bitcoind option)"))) blockchain disk space requirements to this many megabytes by
deleting old blocks. Use this on a resource-constrained node that can't
fit the full blockchain. Other parts of the system will use other disk
space that can't currently be pruned, so you will still need at least
the minimum amount of space mentioned in the +datadir+ option.
++txindex++:: Maintain ((("txindex option (bitcoind command)")))an index of all transactions. This allows you to
++txindex++:: Maintain ((("txindex option (bitcoind option)")))an index of all transactions. This allows you to
programmatically retrieve any transaction by its ID provided that the
block containing that transaction hasn't been pruned.
[role="less_space pagebreak-before"]
++dbcache++:: The size((("dbcache option (bitcoind command)"))) of the UTXO cache. The default is 450 mebibytes (MiB). Increase
++dbcache++:: The size((("dbcache option (bitcoind option)"))) of the UTXO cache. The default is 450 mebibytes (MiB). Increase
this size on high-end hardware to read and write from your disk less
often, or reduce the size on low-end hardware to save memory at the
expense of using your disk more frequently.
++blocksonly++:: Minimize ((("blocksonly option (bitcoind command)")))your bandwidth usage by only accepting blocks of
++blocksonly++:: Minimize ((("blocksonly option (bitcoind option)")))your bandwidth usage by only accepting blocks of
confirmed transactions from your peers instead of relaying unconfirmed
transactions.
++maxmempool++:: Limit ((("maxmempool option (bitcoind command)")))the transaction memory pool to this many megabytes.
++maxmempool++:: Limit ((("maxmempool option (bitcoind option)")))the transaction memory pool to this many megabytes.
Use it to reduce memory use on memory-constrained nodes.
[[txindex]]
.Transaction Database Index and txindex Option
****
By default,
Bitcoin Core builds((("txindex option (bitcoind command)")))((("transactions", "building complete index"))) a database containing _only_ the transactions
Bitcoin Core builds((("txindex option (bitcoind option)")))((("transactions", "building complete index"))) a database containing _only_ the transactions
related to the user's wallet. If you want to be able to access _any_
transaction with commands like +getrawtransaction+ (see
<<exploring_and_decoding_transactions>>), you need to configure Bitcoin