aboutsummaryrefslogtreecommitdiff
path: root/src/validation.cpp
diff options
context:
space:
mode:
author0xb10c <0xb10c@gmail.com>2021-12-06 11:06:36 +0100
committerArnab Sen <arnabsen1729@gmail.com>2022-02-18 20:48:52 +0530
commit799968e8b38833dc7fd7b6d488a66a14580ef674 (patch)
tree8dee10dad4d43ac15c768630a267deb0e54d1cda /src/validation.cpp
parent36a65847033540cf2203252c7baf42bc5ec97579 (diff)
tracing: misc follow-ups to 22902
- mention 'Lost X events' workaround - clarify flush tracepoint docs - fix typo in tracepoint context - clarify flush for prune The documentation and examples for the `fFlushForPrune` argument of the utxocache flush tracepoint weren't clear without looking at the code. See these comments: https://github.com/bitcoin/bitcoin/pull/22902#issuecomment-987094612 - doc: note that there can be temporary UTXO caches Bitcoin Core uses temporary clones of it's _main_ UTXO cache in some places. The utxocache:add and :spent tracepoints are triggered when temporary caches are changed too. This is documented.
Diffstat (limited to 'src/validation.cpp')
0 files changed, 0 insertions, 0 deletions