This commit simply updates a single software library dependency from version 1.7.3 to 1.7.4. There is no information in the commit itself about what changed in that library or whether it fixes any security issue. Without knowing the conten…
This commit is a routine UI/UX refactor of the BTCPay Server reports page. It replaces a custom date-picker and JavaScript-driven report fetching with a shared date-range selector component and standard GET form submission. There is no ind…
This commit is a performance and user-experience improvement for Zcash batch transactions on the Keystone 3 hardware wallet. It speeds up processing of multiple Zcash PCZTs by caching decoded viewing keys and spend-authorization keys acros…
Refactors key derivation caching for Zcash batch signing (SpendAuthCache)Adds BatchCheckContext to cache decoded UFVK and WalletKeys across batch itemsFuses check and parse passes to reduce bundle walks and output trial-decryption
This commit adds a safety check for Zcash batch transactions on Keystone hardware wallets. Before fully parsing a batch of PCZT (Zcash transaction) data, the firmware now reads the declared number of items and rejects it if it exceeds 50. …
Pre-allocation input validation: bounds a length field before parser allocationPotential denial-of-service vector mitigated: oversized count could exhaust device memoryNew dependency `postcard` introduced for controlled length decoding
This commit refactors how Keystone's Zcash batch signing feature handles large batches. It replaces an older message envelope with a new format that uses the upstream Zcash PCZT batch signer, adds a 512 KiB total size cap, raises the maxim…
Adds explicit 512 KiB byte bound on batch request/response data in addition to a count boundSwitches batch response from full signed PCZT bytes to compact spend-authorization signatures, reducing data exposureRejects duplicate canonical PCZT payloads in a batch
This is a routine automated code-formatting commit. It only reorders imports, removes blank lines, and collapses multi-line formatting to single-line formatting as directed by the rustfmt tool. There are no functional code changes, no bug …
This Bitcoin Core commit refactors how transactions are selected and sorted before being announced to network peers. It replaces an older in-place heap sort with a new mempool function that picks the best transactions by mining fee score w…
Refactor of P2P transaction inventory relay ordering logicChange of container type from std::set to std::vector for pending inventoryIntroduction of new mempool dependency-aware selection API
This commit removes an unused helper function called CompareMiningScoreWithTopology from Bitcoin Core's transaction memory pool code. It also updates an internal consistency check to use a different, already-existing comparison method. The…
This commit introduces a brand-new, generic token-bucket utility class and a full set of unit tests for it. A token bucket is a common algorithm for rate limiting (controlling how often an action can happen). There is no change to existing…
This commit adds a global rate limiter to how many transaction announcements (INV messages) a Bitcoin node sends out. Before, each peer had its own queue, so a node could receive one transaction and announce it to over 100 peers, acting li…
Global rate limiting replaces per-peer queues to prevent transaction-announcement amplificationDual token buckets bound both INV count and relay bandwidthCommit message explicitly describes the change as limiting transaction-spam amplification and excessive memory/CPU usage
This commit adds a periodic debug log message that prints statistics about Bitcoin's inventory backlog. It is purely an observability/monitoring change and does not alter network behavior, consensus rules, or security boundaries.
This commit adds a new debug-only command-line option called -txsendrate that lets node operators change how many transaction announcements per second Bitcoin Core sends to inbound peers. The default behavior stays the same (14 transaction…
Adds a new DEBUG_ONLY configuration knob for transaction inventory broadcast rateClamps user-supplied value to 1-1000 tx/s to prevent extreme misconfigurationReplaces hardcoded constant with runtime option; default behavior unchanged
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.