npub18e…hsuvj on Nostr: Bitcoin Core PR #34806 refactors logging API Bitcoin Core PR #34806, opened by ...
Bitcoin Core PR #34806 refactors logging API
Bitcoin Core PR #34806, opened by ajtowns on Apr 27, 2026, refactors the logging API: ShrinkDebugFile now takes the logging mutex, NO_RATE_LIMIT can bypass throttling for critical logs, GetLogCategory moves out of the global namespace, ShouldLog is split into ShouldDebugLog / ShouldTraceLog, LogAcceptCategory is removed, and more files include util/log.h instead of logging.h.
Mechanically this is about safer and more explicit node logging: mutex protection targets races during logging initialization, rate-limit tags give controlled escape hatches for critical output, and the split logging predicates tighten signature-based filtering with less runtime ambiguity. The summary says this does not change consensus or transaction behavior.
Caveat from the review surface: adding mutexes may add contention in low-latency paths, NO_RATE_LIMIT depends on disciplined use, and the ShouldLog split only improves filtering if callers do not bypass the intended path.
Source:
https://github.com/bitcoin/bitcoin/pull/34806https://github.com/bitcoin/bitcoin/pull/34806#Bitcoin #BitcoinCore #FullNodes #NodeOps
Published at
2026-07-03 13:45:18 UTCEvent JSON
{
"id": "8cb9a78ccf6773880e5f96f596c37b104c38995024b3443509d1e12ffcaefdd4",
"pubkey": "3e6a037c63e7c726f4ed51a1898aa2bb442913ef4ba729f0d27392ab3a57b3c1",
"created_at": 1783086318,
"kind": 1,
"tags": [
[
"t",
"bitcoin"
],
[
"t",
"bitcoincore"
],
[
"t",
"fullnodes"
],
[
"t",
"nodeops"
]
],
"content": "Bitcoin Core PR #34806 refactors logging API\n\nBitcoin Core PR #34806, opened by ajtowns on Apr 27, 2026, refactors the logging API: ShrinkDebugFile now takes the logging mutex, NO_RATE_LIMIT can bypass throttling for critical logs, GetLogCategory moves out of the global namespace, ShouldLog is split into ShouldDebugLog / ShouldTraceLog, LogAcceptCategory is removed, and more files include util/log.h instead of logging.h.\n\nMechanically this is about safer and more explicit node logging: mutex protection targets races during logging initialization, rate-limit tags give controlled escape hatches for critical output, and the split logging predicates tighten signature-based filtering with less runtime ambiguity. The summary says this does not change consensus or transaction behavior.\n\nCaveat from the review surface: adding mutexes may add contention in low-latency paths, NO_RATE_LIMIT depends on disciplined use, and the ShouldLog split only improves filtering if callers do not bypass the intended path.\n\nSource: https://github.com/bitcoin/bitcoin/pull/34806\n\nhttps://github.com/bitcoin/bitcoin/pull/34806\n\n#Bitcoin #BitcoinCore #FullNodes #NodeOps",
"sig": "1c1057a8cd97695fd6612c151b818292c91e9950c7bab7dc8c23adf98012344015a56c4c3350bb7e2c6c16203af34170362eec7a5f233a021d64b26190a74bdc"
}
