This commit updates a GitHub Actions workflow that runs an optional code-review bot called 'gateway'. It only changes two pinned version numbers (SHA hashes) for the bot's action and its runtime, moving from v0.5.0 to v0.6.0. There is no c…
This commit only updates a generated API snapshot file (all-features.txt). It records that some serde helper functions now require only Encode for serialization and only Decode for deserialization, rather than requiring both traits. The ac…
This commit relaxes the rules for which Rust types can be converted to and from serde serialization formats. Previously, a type had to support both encoding and decoding to be used in either direction. Now, types only need to support the d…
This commit only adds a new fuzz test for an existing data type (TapLeafHash). It does not change any production code, fix a bug, or alter behavior. There is no security issue here.
This commit adds standard data-encoding support for a Bitcoin Taproot hash type (TapLeafHash) so it can be properly serialized and deserialized in PSBT data. There is no indication of a security bug being fixed; it appears to be a missing-…
No security-relevant signal in commit message or diffChange is a feature addition (encoding trait implementations)No bounds-checking, memory-safety, or cryptographic flaws evident in diff
This commit simply adds a new internal software building block (a Rust crate dependency called bitcoin-consensus-encoding) to another internal crate (taproot-primitives). It updates package lists and feature flags so the new dependency can…
This commit adds a single line re-exporting a new Rust crate called taproot_primitives from the main bitcoin crate. It is a routine dependency wiring change with no visible security implications in the diff itself.
This commit only adds a new automated test to the project. It does not change any production code. The test demonstrates that two equivalent Bitcoin blocks—one with a cached witness root and one without—compare as equal. It is a regression…
Test-only change, no runtime code modifiedReferences a prior bug fix in commit messageDemonstrates equality semantics ignore cached witness root
This commit only updates generated API snapshot text files that record which Rust traits are implemented for the library's types. The actual code change (adding or removing trait bounds on equality comparisons for a Block type) is not pres…
This commit fixes a bug in how Bitcoin 'Block' objects are compared for equality. The old code automatically compared every internal field, including a cached 'witness_root' value that can be missing or different depending on how the block…
Incorrect equality semantics on a core consensus-adjacent data structure (Block)Derived equality included a cache field (witness_root) that is not part of the canonical block identityPotential for logic bugs, test failures, or incorrect caching/lookup behavior downstream
This commit only adds two new empty database tables (our_outputs and our_txs) to Core Lightning's wallet. It is a preparatory schema change for a future feature; no code reads from or writes to these tables yet, and no existing behavior is…
Schema-only migration with no runtime codeNew tables are not yet populated or queried by any code pathDesign note: sentinel 0 replaces NULL for blockheight/txindex/reserved_til, which could reduce NULL-handling bugs in future code
This commit adds new wallet bookkeeping code for Core Lightning. It records Bitcoin deposits found by a new chain-watcher ('bwatch') into database tables and handles blockchain reorganizations by demoting transactions back to unconfirmed r…
New database write paths for wallet UTXOs and transactionsReorg revert logic demotes rather than deletes rows to preserve metadataOwner-string constructors added to avoid silent unwatch failures from format mismatches
A quiet fix may be responsible caution—or it may leave users unaware that their assets were ever at risk. CommitWatch preserves the evidence, adds context, and tracks whether vendors disclose, acknowledge, and learn.