We watch what security-critical projects change—then translate the code into clear, independent intelligence anyone can understand.
AI analysis is published as generated. Community notes appear after human validation.
This commit is a routine feature update. It upgrades a dependency called bindex from version 0.1.1 to 0.1.2 and changes the code to pass a configurable REST server URL into the indexing component. There is no indication in the commit that …
1255a377by Roman Zeyde+6−53 filesThis commit changes the hash function used inside Bitcoin Core's in-memory coin cache (the UTXO cache) from SipHash-2-4 to a faster SipHash-1-3 variant. The change is framed as a performance optimization. The commit message and code commen…
2beab948by Lőrinc+48−95 filesThis is a small internal cleanup in Bitcoin Core's coin-cache code. It makes a temporary set of transaction IDs use the same hash function as the main coins cache, instead of a separate one. The change is described by the authors as a perf…
3bfdcbd7by Lőrinc+12−84 filesThis is a code cleanup (refactor) that moves the internal SipHash mixing steps into shared helper methods. It does not change how Bitcoin hashes data, how many rounds are run, or any user-visible behavior. There is no security bug being fi…
25bfca06by Lőrinc+74−1222 filesThis commit adds a new, weaker variant of the SipHash algorithm inside Bitcoin Core's cryptography module. It is explicitly designed for low-security uses such as internal hash tables, not for protecting funds or network messages. The code…
c2d7931bby Pieter Wuille+103−02 filesThis commit adds two new shortcut methods for computing a specific SipHash variant on fixed-size inputs. It is a pure performance/ergonomics addition: the new methods copy the hasher's internal state before operating, so they do not alter …
a0ccd4adby Pieter Wuille+21−01 fileThis commit only adds new test cases and fuzzing coverage for an existing SipHash variant called SipHash-1-3-UJ. It does not change any production code, so it cannot introduce a security vulnerability or fix one. The change makes the softw…
3aea8541by Pieter Wuille+131−643 filesThis commit only adds new performance benchmark tests for a hash function called SipHash. It does not change any production code that handles Bitcoin transactions, networking, or wallet data. There is no security issue here.
7ff55cc6by Lőrinc+49−31 fileThis commit fixes a race condition in btcd's peer networking code. If a peer was told to disconnect before a network socket had been attached, the socket could later be attached but never closed, leaking the connection. The fix adds a lock…
617ebe2bby Boris Nagaev+111−72 filesThis commit refactors how btcd handles incoming Bitcoin v2 transport handshakes. It adds a new admission-control hook so a responder can decide whether to spend CPU on a v2 handshake only after it has seen enough bytes to confirm the peer …
6cad3935by Boris Nagaev+494−1022 filesThis commit adds a new optional feature to btcd's connection manager that lets operators set a maximum number of simultaneous inbound connections. It is a defensive hardening change, not a fix for an active vulnerability. The default behav…
ad8d94e6by Boris Nagaev+291−74 filesThis commit adds a new inbound connection rate-limiting and admission-control system to btcd. It is designed to reduce the risk of denial-of-service attacks where an attacker opens many incomplete handshake connections or forces the server…
6c056ec4by Boris Nagaev+1001−1812 filesA 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.