Amber nodes are monitored by CommitWatch. Gray nodes are sampled from authenticated GitHub public commit search and may not represent complete contribution history.
This commit fixes a bug where Bitcoin Core could hang during shutdown if the user started a 'reindex' and then asked the program to quit before it finished loading the very first block. The fix adds a notification so the shutdown request i…
Denial-of-service/availability issue: graceful shutdown can hangFix is in initialization/shutdown synchronization logicNo attacker-controlled input path identified
This is a tiny test-only change that adds a missing assertion in a unit test. It does not change any production code, network rules, or wallet behavior. There is no security issue here.
This is a small code cleanup that removes an unused parameter from an internal function. The function previously received a 'BlockManager' object but did not actually use it. The change only adjusts the function signature and the two place…
This commit only removes a misleading comment in the source code. It does not change any actual code behavior. The old comment incorrectly stated that failing certain script checks could cause a peer to be banned from the network. The comm…
This commit only adds documentation (release notes) describing a prior change. It does not modify any executable code, network behavior, or security logic. There is no security issue in this commit itself.
This commit only adds new test cases to Bitcoin Core's unit tests. It checks that a function called ValidateInputsStandardness correctly returns specific error messages when transactions have unusual or non-standard inputs. There is no cha…
This is a code cleanup change that separates how fee rates are displayed (BTC/kvB versus sat/vB) from how fees are estimated. It introduces a new FeeRateFormat enum and removes display-only values from the FeeEstimateMode enum. There is no…
This commit is a simple code reorganization: it moves an existing list of fee-estimation options (the FeeEstimateMode enum) from one header file to another, without changing any values, logic, or behavior. There is no security issue here.
This commit only adds documentation: a release note explaining that the Bitcoin Core fee estimator now tracks lower fee rates (down to 0.1 sat/vB instead of 1 sat/vB). There is no code change, no bug fix, and no security issue in the diff …
This commit only changes a Bitcoin Core functional test file. It adds a new test to verify that the fee estimator can return estimates below 1 satoshi per virtual byte, and refactors how the test tracks confirmed and unspent transaction ou…
This commit removes an unused placeholder value from the fee estimator's saved data file format. It is a cleanup change with no apparent security relevance.
This commit simply updates a version number used when Bitcoin Core saves its fee-estimation data to disk. It is a routine compatibility marker, not a security fix. There is no vulnerability here.
This commit lowers the lowest fee-rate bucket used by Bitcoin Core's built-in transaction fee estimator from 1000 to 100. It is a follow-up to an earlier policy change that reduced the default minimum relay fee. The change keeps the estima…
No memory safety, cryptographic, or consensus changesNo input validation or authorization changesConstant-only change in fee-estimator configuration
This commit only changes a code comment in a header file. It deletes an outdated, incorrect description of the removeUnchecked function and replaces it with a short, accurate note. No program logic, behavior, or security boundary is change…
This is a documentation-only change. A developer renamed a function called PackageMempoolChecks to PackageRBFChecks and removed an outdated comment. No actual transaction-validation logic was changed, so this cannot affect security or beha…
This is a small internal code cleanup in Bitcoin Core's transaction acceptance logic. It moves a check so that a package-replacement-specific validation routine is only called when actually processing a package RBF (replace-by-fee), rather…
This commit is a simple cleanup: it updates comments and documentation strings that still pointed to an old file path (`policy/fees.h`) after that file was apparently moved or split. The actual code behavior does not change at all. There i…
This commit adds a new 'interruptWait' feature to Bitcoin Core's mining interface so that a long-running wait for the next block template can be safely cancelled. It is a normal feature addition with no obvious security bug. The change inc…
No security-relevant signals in the diff: no memory corruption, no authentication/authorization changes, no cryptographic changes, no consensus changes.New IPC method is stateful but only affects the local waiter's own block-template wait; it does not alter chain state or mempool policy.Condition-variable wake pattern is standard and does not introduce new deadlock or use-after-free paths visible in the diff.
This commit fixes a math bug in the Bitcoin Core block-building code. The original code subtracted a safety margin from the maximum block weight and then compared the current block weight to that lower number. Because the variables are uns…
Unsigned integer underflow in block-weight comparisonMiner block-assembly logic correctness fixPotential consensus-adjacent behavior in transaction selection