BT
← All projectsbtcsuite

btcd

Alternative full-node Bitcoin implementation written in Go.

BitcoinNode implementationsNormal
Repository coverage

261 commits in the local evidence base

Every captured commit receives deterministic security triage and a separate communication-quality score. Security candidates and broader second-pass signals receive full-patch Ollama analysis.

60security candidates38second-pass queue233AI analyses
0commits · 30 days
48commits · 60 days
134commits · 180 days
248commits · 365 days
Backfill bands
Aug 5 → Feb 621 seen1 candidatesComplete
Feb 6 → Jun 6112 seen7 candidatesComplete
Jun 6 → Jul 634 seen13 candidatesComplete
Jul 6 → Aug 530 seen7 candidatesComplete
Commit communication

Does the history explain itself?

Message quality measures whether a commit identifies its scope, purpose, rationale, testing, and supporting references. It does not change the security-severity score.

70/100 average clarity
84Strong · 80–100
109Adequate · 60–79
63Thin · 40–59
5Opaque · 0–39
Read the scoring rubric →
Developer activity

Who is changing the project?

Public Git author strings; identities are not independently verified.

DeveloperCommitsCandidatesAnalyzedHigh riskMessage avg.
Boris Nagaev702056265
Olaoluwa Osuntokun882078174
Lrifton92434186
Erick Cestari818177
Or Aharonee404184
Oliver Gugger13413047
MPins333079
yyforyongyu322069
Drake Thomsen222091
Eric Grill313086
Julio Cesar111045
Jacob Schuler111088
Analysis record

Published AI watches

Last scanned 35 minutes ago

Informational 0 AI analysisMessage 80 · Strong
BT btcsuitebtcd BitcoinNode implementations

build: pin v0.27.0 nested module releases

This commit only updates build dependency version numbers in go.mod and go.sum. It does not change any application code, so by itself it cannot introduce or fix a security vulnerability. The commit message says it pulls in fixes that were …

01a9e591by Olaoluwa Osuntokun+15−182 files
No security note in commit
Moderate 61 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2611 from yyforyongyu/task-btcutil-audit

This commit tightens two safety checks in btcd's helper libraries. First, it makes child key derivation reject rare 'cancellation' cases where a derived private key would become zero or a public key would become the point at infinity—both …

Rejection of zero private scalar and point-at-infinity in BIP32 derivationReconciliation of conflicting witness/non-witness UTXO descriptions in PSBT fee computationAddition of unit tests exercising the new rejection paths
e799ee42by Olaoluwa Osuntokun+254−217 files
No security note in commit
Moderate 57 AI analysisMessage 78 · Adequate
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2655 from yyforyongyu/task/txscript-signature-validation

This commit tightens how Bitcoin script signatures are validated in btcd. It moves several security checks earlier in the process, limits a special 'OP_SUCCESS' shortcut to ordinary tapscript leaves, and fixes the signature-removal logic s…

Moved ScriptVerifyConstScriptCode check before signature parsing in legacy scriptsRestricted OP_SUCCESS shortcut to base tapscript leaf versionFixed removeOpcodeByData to match only data pushes and handle empty dataToRemove
a72ace10by Olaoluwa Osuntokun+90−764 files
No security note in commit
Moderate 69 AI analysisMessage 50 · Thin
BT btcsuitebtcd BitcoinNode implementations

txscript: align signature opcode validation

This commit fixes several subtle inconsistencies in how btcd validates Bitcoin script signatures, especially for newer Taproot-style transactions. It changes when empty signatures and unknown public-key types are rejected, tightens the rul…

Consensus/policy divergence in signature opcode validationTapscript empty-signature and unknown-pubkey-type handling changedScriptVerifyConstScriptCode placement and scope changed
8a2b9165by yyforyongyu+90−764 files
No security note in commit
Low 44 AI analysisMessage 58 · Thin
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2654 from Roasbeef/build/go-1.27.3

This commit updates the Go programming language toolchain used to build btcd from version 1.27.2 to 1.27.3, and bumps the minimum required Go version from 1.26.9 to 1.26.10. The README explicitly says this is to include a mitigation for CV…

Toolchain point-release upgradeREADME references CVE-2026-111943 mitigationMinimum Go version bumped across all go.mod files
a1cc50bdby Olaoluwa Osuntokun+24−1915 files
Vendor flagged security relevance
Low 33 AI analysisMessage 88 · Strong
BT btcsuitebtcd BitcoinNode implementations

build: upgrade Go toolchain to 1.27.3

This commit updates the Go programming language version used to build btcd from 1.27.2 to 1.27.3, and bumps the minimum required Go version from 1.26.9 to 1.26.10. The commit message says this is done to pick up a security fix in Go's cryp…

Toolchain update to a Go point release advertised as fixing CVE-2026-111943 in crypto/x509No application code changes; risk depends entirely on the accuracy of the upstream Go release notesCVE identifier appears fabricated or future-dated (2026) and does not match known public CVE numbering at the time of review
887de811by Olaoluwa Osuntokun+19−1915 files
Vendor flagged security relevance
Informational 15 AI analysisMessage 83 · Strong
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2628 from fametrano/musig2-bip327-vectors

This commit updates the test data and test code for the MuSig2 multi-signature implementation in btcd to match the latest official BIP 327 test vectors. It does not change the cryptographic implementation itself, only the test fixtures and…

No production code changesTest-only data refreshNo vulnerability description in commit or references
ec47ee12by Olaoluwa Osuntokun+67−437 files
No security note in commit
Low 46 AI analysisMessage 68 · Adequate
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2627 from starius/bump-deps

This is a large maintenance update for btcd that upgrades Go and many dependencies, replaces some old external libraries with newer or in-house ones, and fixes several bugs in RPC, Tor proxy, and build processes. Most changes are not secur…

Unauthenticated websocket read limit added (64 KiB) to prevent large-message abuse before authWebsocket authentication timeout added to drop unauthenticated clientsWebsocket write timeout added to prevent slow/stalled clients from hanging server goroutines
c615bd70by Olaoluwa Osuntokun+1848−30952 files
No security note in commit
Low 31 AI analysisMessage 88 · Strong
BT btcsuitebtcd BitcoinNode implementations

rpcserver: detect unexpected replies before websocket shutdown

This commit fixes a test helper in btcd's RPC websocket server. The helper now reads any leftover server response before waiting for the connection to close. Previously, waiting first could let an authentication timeout hide a reply that w…

Test-only hardening against hidden/unexpected RPC repliesUnauthenticated malformed request handling in websocket RPC pathAuthentication timeout may mask server replies
b67710c7by Olaoluwa Osuntokun+4−21 file
No security note in commit
Informational 15 AI analysisMessage 88 · Strong
BT btcsuitebtcd BitcoinNode implementations

btcec/schnorr/musig2: refresh BIP 327 test vectors

This commit only updates test data and test code for the MuSig2 cryptographic signing feature. It refreshes the official Bitcoin BIP 327 test vectors, adjusts the tests to match the new vector format, fixes a test bug where verification wa…

No production code changesTest-only vector refreshTest bug fix in verify-fail signer indexing
f237e882by Ferdinando Ametrano+67−437 files
No security note in commit
Moderate 64 AI analysisMessage 68 · Adequate
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2625 from starius/port-35984

This commit fixes a Bitcoin signing bug in btcd. When creating a transaction signature of type SIGHASH_SINGLE for an input whose index has no matching output, the signature would not actually commit to any output. That means the signature …

SIGHASH_SINGLE without matching output creates signature committing to no outputSignature remains valid if outputs are later mutated, as long as matching output remains absentCould allow funds redirection by anyone holding the signature
bbeb9d41by Olaoluwa Osuntokun+344−04 files
Vendor flagged security relevance
Moderate 61 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

Merge pull request #2565 from Roasbeef/wire-script-arena

This commit is a large refactoring of how btcd decodes Bitcoin network messages. It replaces a fixed 4 MiB temporary buffer (a 'slab') with a tiered arena allocator and adds checks to avoid reserving huge amounts of memory when a message c…

Replaced fixed 4 MiB decode slab with tiered arena to reduce memory amplification and unbounded free-list retentionAdded truncated-payload guards (validateElementCount, canPreallocateElements, readBytes) to prevent huge preallocation on malformed length/count prefixesCleared TxIn/TxOut on failed MsgTx decode to avoid leaking arena-backed slices to callers
6c52a019by Olaoluwa Osuntokun+2654−20130 files
Vendor flagged security relevance
Low 34 AI analysisMessage 83 · Strong
BT btcsuitebtcd BitcoinNode implementations

rpcclient: preserve transactions during mempool accept validation

This commit fixes a bug in btcd's RPC client where a function that checks whether transactions would be accepted by the mempool was accidentally modifying the caller's transaction data during its internal validation. The fix makes the func…

Mutation of caller-owned input objects in a public APIPotential transaction data corruption or unexpected state change in downstream consumersRegression test added covering both success and failure validation paths
81d3555dby Olaoluwa Osuntokun+68−12 files
No security note in commit
Moderate 61 AI analysisMessage 78 · Adequate
BT btcsuitebtcd BitcoinNode implementations

wire: clear transaction scripts on decode errors

This commit fixes a memory-safety bug in btcd's Bitcoin transaction decoder. When decoding a transaction failed partway through, the partially built transaction could still hold pointers to a shared memory area (an 'arena') used for script…

Use-after-free-like pattern: staged slices referencing a reusable arena after decode failureShared memory pool (script arena) reused across decodesPotential information disclosure or memory corruption if stale arena-backed scripts are accessed
6651b8f3by Olaoluwa Osuntokun+76−184 files
No security note in commit
Informational 15 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

multi: switch to github.com/decred/dcrd/container/lru

This is a routine dependency update. The project switched from an older, deprecated Decred LRU cache package to a newer typed/generic version. The code behavior is intended to stay the same; no security vulnerability is visible in the chan…

eb8c6c94by Boris Nagaev+28−266 files
No security note in commit
Low 46 AI analysisMessage 78 · Adequate
BT btcsuitebtcd BitcoinNode implementations

multi: replace btcsuite/go-socks with an x/net/proxy wrapper

This commit swaps out an old, unmaintained SOCKS proxy library for a new internal wrapper around a modern Go package. The change is mostly a refactor, but it deliberately fixes several subtle SOCKS/Tor-related behaviors that could affect s…

Replacement of outdated/unmaintained SOCKS dependencyFix for peer whitelisting bypass via proxy RemoteAddr semanticsPer-connection random Tor stream-isolation credentials
4041477cby Boris Nagaev+545−1110 files
No security note in commit
Low 49 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

config: apply --torisolation to --proxy without credentials

This commit fixes a configuration bug in btcd, a Bitcoin node implementation. When a user enabled Tor stream isolation with --torisolation and used a proxy without a username/password, the isolation was silently not applied. The fix makes …

Privacy configuration silently ignoredTor stream isolation bypassUser expectation mismatch between flags and behavior
f9b34babby Boris Nagaev+41−32 files
Vendor flagged security relevance
Informational 18 AI analysisMessage 83 · Strong
BT btcsuitebtcd BitcoinNode implementations

multi: switch from btcsuite/websocket to gorilla/websocket

This commit swaps btcd's websocket library from an old, unmaintained in-house copy to the actively maintained gorilla/websocket. The only behavior change is that the new library reports a normal peer disconnect differently, so the code now…

Dependency switched from unmaintained fork to maintained upstream websocket libraryBehavior change only in error classification for clean disconnectsNo memory corruption, authentication bypass, or cryptographic weakness visible in diff
63febe36by Boris Nagaev+367−88 files
No security note in commit
Informational 19 AI analysisMessage 73 · Adequate
BT btcsuitebtcd BitcoinNode implementations

multi: replace btcsuite/winsvc with golang.org/x/sys/windows/svc

This commit swaps out an old, unmaintained Windows service helper library for the modern, officially maintained Go equivalent. The main practical effects are that btcd can now be compiled for Windows on ARM64 computers, and the Windows ser…

Dependency on stale/unmaintained Windows service library removedNew dependency is the officially maintained golang.org/x/sys module already present in the buildWindows service creation now sets ErrorControl to ErrorNormal, improving failure visibility
b7d6cd52by Boris Nagaev+10−113 files
No security note in commit
Informational 18 AI analysisMessage 70 · Adequate
BT btcsuitebtcd BitcoinNode implementations

build: bump GitHub Actions

This commit updates the versions of several GitHub Actions used in the project's automated build and release workflows. It moves actions/checkout and actions/setup-go to v7, and updates Docker-related actions to newer pinned releases. The …

Dependency/version bump of CI/CD actionsMove from Node 20 runtime to Node 24 runtime for GitHub ActionsDocker action pins updated from 2021-22 releases to 2024-25 releases
6fe579baby Boris Nagaev+16−163 files
No security note in commit
Repository ledger

Explore captured commits

Expand any commit for its author, full message, clarity score, changed files, triage signals, analysis, and source link.

Lower-prioritypeer: match known inventory by valueby Boris Nagaev · f35560c5 · Oct 8, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Boris Nagaev

peer: match known inventory by value

When knownInventory moved from btcd's own inventory map to the generic
dcrd/lru cache in 875b51c9 (2020), the *wire.InvVect pointers were
passed as the keys. The old map was keyed by the dereferenced value, but
the generic cache compares the pointers, so inventory from one message
never matched the same inventory from another. Every check of whether a
peer already knows some inventory came out false, and btcd announced
inventory back to the peers that had just announced it.

Store and look up the values again, through a knowsInventory helper.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Security candidatemulti: replace btcsuite/go-socks with an x/net/proxy wrapperby Boris Nagaev · 4041477c · Oct 8, 2026 · 10 filesMessage 78 · AdequateLow 46Details
Commit message · Boris Nagaev

multi: replace btcsuite/go-socks with an x/net/proxy wrapper

btcsuite/go-socks, a fork of samuel/go-socks is outdated. Replace it
with a maintained package golang.org/x/net/proxy. Add internal/socks,
which keeps the API btcd used on top of x/net/proxy, and the behavior it
relied on:

- The connection reports the requested destination as its remote
address. outboundPeerConnected whitelists peers by it, so with a
plain x/net/proxy connection, which reports the proxy's address, a
whitelisted local Tor proxy would have whitelisted every peer reached
through it.
- Its local address is the address the proxy bound, now parsed
correctly.
- Tor stream isolation uses new random credentials for every
connection.
- Hostnames, including onion addresses, are passed to the proxy
unresolved.
- The timeout covers the SOCKS handshake too.

rpcclient now dials its websocket through the proxy with the dialer's
context, so the handshake timeout also covers the proxy.

Verified end to end with two simnet nodes connected through a
forwarding SOCKS5 proxy: the handshake completes, getpeerinfo reports
the peer and the proxy's bound address, the peer connection uses random
isolation credentials, and btcctl and an rpcclient websocket client
reach the RPC server through the proxy.

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Names security-relevant behavior explicitly
Why it was queued
credential or privilege state
AI analysis · Low 46/100

This commit swaps out an old, unmaintained SOCKS proxy library for a new internal wrapper around a modern Go package. The change is mostly a refactor, but it deliberately fixes several subtle SOCKS/Tor-related behaviors that could affect security: peer whitelisting, stream isolation, hostname handling, and handshake timeouts. The commit message and tests describe these as behavior-preserving fixes rather than as a response to a reported vulnerability.

Security candidateconfig: apply --torisolation to --proxy without credentialsby Boris Nagaev · f9b34bab · Oct 8, 2026 · 2 filesMessage 73 · AdequateLow 49Details
Commit message · Boris Nagaev

config: apply --torisolation to --proxy without credentials

With --proxy and --torisolation, Tor stream isolation was only enabled
when --proxyuser or --proxypass was also set, so a plain
--proxy=127.0.0.1:9050 --torisolation silently ran without it. The
credentials were only meant to decide whether to warn that they get
overridden, as they did when isolation was added in 2015; the two
conditions were merged in a 2016 refactor.

Enable isolation whenever --torisolation is set, except in bridge mode,
where --onion is also set and gets the isolation instead.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
credential or privilege state
AI analysis · Low 49/100

This commit fixes a configuration bug in btcd, a Bitcoin node implementation. When a user enabled Tor stream isolation with --torisolation and used a proxy without a username/password, the isolation was silently not applied. The fix makes --torisolation work as expected regardless of whether proxy credentials are set, except in 'bridge mode' where a separate onion proxy is configured. The practical effect is that affected users' connections through Tor were not being isolated as they believed, potentially reducing their privacy.

Lower-priorityrpcserver: time out websocket writesby Boris Nagaev · ad55533f · Oct 8, 2026 · 2 filesMessage 60 · AdequateTriage 0Details
Commit message · Boris Nagaev

rpcserver: time out websocket writes

Set a write deadline for every message. It is a generous five minutes,
so a slow link can still receive a large reply.

60/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body
Lower-priorityrpcserver: bound websocket clients before they authenticateby Boris Nagaev · 16f6d4d3 · Oct 8, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Boris Nagaev

rpcserver: bound websocket clients before they authenticate

The /ws endpoint upgrades the connection before the client has
authenticated, and only expects the authenticate command afterwards.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-priorityrpcclient: time out the websocket handshakeby Boris Nagaev · ca98ef58 · Oct 8, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Boris Nagaev

rpcclient: time out the websocket handshake

The websocket dialer had no handshake timeout, so a server that accepted
the TCP connection but never completed the opening handshake hung the
dial forever. gorilla/websocket also reads up to 1 KiB of the response
body when the handshake fails, so a server that sends an error status
but stalls the body hangs it too, where btcsuite/websocket returned
right after the headers.

Bound the dial and the handshake by the same one-minute timeout used
for HTTP POST requests.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
AI review queuedmulti: switch from btcsuite/websocket to gorilla/websocketby Boris Nagaev · 63febe36 · Oct 8, 2026 · 8 filesMessage 83 · StrongInformational 18Details
Commit message · Boris Nagaev

multi: switch from btcsuite/websocket to gorilla/websocket

btcsuite/websocket is a copy of gorilla/websocket. gorilla/websocket is
maintained and already a test dependency.

The one difference btcd depends on: when the peer sends a normal close
frame, the old code returned io.EOF from ReadMessage, while gorilla
returns a *CloseError. Treat that like io.EOF in the read loops of the
RPC server and rpcclient, so clean disconnects aren't logged as errors.

Add a websocket test server for the RPC server that runs without a
chain, and use it to test that a normal close isn't logged.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 18/100

This commit swaps btcd's websocket library from an old, unmaintained in-house copy to the actively maintained gorilla/websocket. The only behavior change is that the new library reports a normal peer disconnect differently, so the code now treats a normal close frame like a clean disconnect instead of logging it as an error. There is no direct security vulnerability being fixed; it is primarily a maintenance and noise-reduction change.

AI review queuedmulti: replace btcsuite/winsvc with golang.org/x/sys/windows/svcby Boris Nagaev · b7d6cd52 · Oct 7, 2026 · 3 filesMessage 73 · AdequateInformational 19Details
Commit message · Boris Nagaev

multi: replace btcsuite/winsvc with golang.org/x/sys/windows/svc

btcsuite/winsvc is a 2013 copy of code.google.com/p/winsvc, last synced
in December 2014, with no btcd-specific changes. Its service control
callback is written in 386 and amd64 assembly, so btcd didn't build for
windows/arm64 at all. golang.org/x/sys/windows/svc provides the same
API (Start is now variadic) and is maintained, and x/sys is already a
dependency.

btcd now builds for windows/amd64, windows/386 and windows/arm64.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 19/100

This commit swaps out an old, unmaintained Windows service helper library for the modern, officially maintained Go equivalent. The main practical effects are that btcd can now be compiled for Windows on ARM64 computers, and the Windows service installer is slightly more robust about reporting startup failures. There is no direct fix for an active security vulnerability in the diff itself.

Security candidatebuild: bump GitHub Actionsby Boris Nagaev · 6fe579ba · Oct 7, 2026 · 3 filesMessage 70 · AdequateInformational 18Details
Commit message · Boris Nagaev

build: bump GitHub Actions

actions/checkout v4 and actions/setup-go v5 run on Node 20, which is
end of life; move them to v7, which run on Node 24.

The image publishing workflow pinned the Docker actions to commits of
2021-22 releases: setup-buildx-action v1.6.0, login-action v1.10.0,
metadata-action v3.3.0 and build-push-action v2.10.0. It only runs on
tags, so breakage from deprecated runtimes would only show at release
time. Pin the latest releases instead, keeping commit pins with the
version in a comment. The inputs and outputs the workflow uses are
unchanged in those versions.

70/100 · AdequateMessage clarity
✓ Descriptive subject✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
access controldocumentation-only discount
AI analysis · Informational 18/100

This commit updates the versions of several GitHub Actions used in the project's automated build and release workflows. It moves actions/checkout and actions/setup-go to v7, and updates Docker-related actions to newer pinned releases. The stated reason is to avoid relying on older GitHub Actions runtimes that run on Node 20, which is approaching end-of-life. There is no direct code change to the btcd software itself, and no specific security vulnerability is described or fixed.

Lower-prioritydocker: move runtime images to Alpine 3.24by Boris Nagaev · ea0ce657 · Oct 7, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Boris Nagaev

docker: move runtime images to Alpine 3.24

The published images ran on Alpine 3.15, end of life since November
2023, and the root Dockerfile on Alpine 3.21, which reaches end of life
on 2026-11-01. Alpine 3.24 is supported until mid-2028 and matches the
golang:1.27.2-alpine3.24 build image.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritydocker: build into a flat directory so cross-built images startby Boris Nagaev · fb9ac138 · Oct 7, 2026 · 2 filesMessage 73 · AdequateTriage 0Details
Commit message · Boris Nagaev

docker: build into a flat directory so cross-built images start

Both Dockerfiles cross-compiled with go install, which puts the
binaries in /go/bin/<os>_<arch>/ rather than /go/bin/ when GOOS or
GOARCH differ from the build container's. The published images copy
/go/bin to /bin, so on every platform except amd64 there is no btcd on
PATH: the arm64 image of v0.26.2 has /bin/linux_arm64/btcd and fails to
start. Build with go build -o /out/ and copy that directory instead.

The root Dockerfile also builds its first stage on the host platform
now, like the workflow one, and its arm64 example passes --platform:
with BuildKit, --build-arg ARCH=arm64v8 alone failed to resolve the
arm64-only base image.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritybuild: bump pgregory.net/rapid to v1.3.0by Boris Nagaev · 6208749a · Oct 7, 2026 · 2 filesMessage 82 · StrongTriage 0Details
Commit message · Boris Nagaev

build: bump pgregory.net/rapid to v1.3.0

rapid is only used by the property-based tests in peer, blockchain and
internal/inbound.

82/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides an explanatory body✓ Mentions testing or verification
AI review queuedmulti: bump secp256k1 to v4.4.1by Boris Nagaev · 5f66b914 · Oct 7, 2026 · 14 filesMessage 78 · AdequateLow 43Details
Commit message · Boris Nagaev

multi: bump secp256k1 to v4.4.1

v4.4.1 reduces inputs to the crypto/elliptic compatibility shim modulo
the field prime, so callers that pass unreduced coordinates get the same
points as with reduced ones, and deprecates the elliptic.Curve methods
since the standard library interface itself is deprecated. btcd only
uses those methods in btcec tests.

78/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Low 43/100

This commit updates btcd's cryptographic library dependency from secp256k1 v4.4.0 to v4.4.1 across multiple Go modules. The new version makes the compatibility layer with Go's standard elliptic curve functions more forgiving by automatically reducing unreduced coordinate inputs modulo the field prime, and it deprecates the old elliptic.Curve methods. The commit itself only changes version numbers in go.mod and go.sum files; it does not contain the actual cryptographic fix code. The commit message describes the upstream change as a behavioral normalization rather than a security vulnerability, and no independent security advisory or CVE is supplied.

AI review queuedmulti: bump golang.org/x/crypto, x/sys and x/timeby Boris Nagaev · 38362a9f · Oct 7, 2026 · 16 filesMessage 68 · AdequateInformational 24Details
Commit message · Boris Nagaev

multi: bump golang.org/x/crypto, x/sys and x/time

Bump x/crypto to v0.57.0 (from v0.40.0, and v0.25.0 in v2transport),
x/sys to v0.48.0 (from v0.35.0 and v0.22.0) and x/time to v0.16.0,
which all require Go 1.26.

btcd doesn't use the affected packages, but scanners flagged 21 to 23
advisories against the old versions, mostly in x/crypto/ssh. The only
one left is GO-2026-5932 for x/crypto/openpgp, which has no fix and
isn't used.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 24/100

This commit updates several Go programming-language helper libraries (golang.org/x/crypto, x/sys, and x/time) to newer versions across btcd's modules. The project says it does not actually use the vulnerable parts of those libraries, but security scanners were flagging the old versions. This is a routine dependency cleanup rather than a fix for an active security problem in btcd itself.

Lower-prioritymempool: move MockTxMempool into a mempooltest packageby Boris Nagaev · 4d8f5d5d · Oct 7, 2026 · 2 filesMessage 83 · StrongTriage 0Details
Commit message · Boris Nagaev

mempool: move MockTxMempool into a mempooltest package

mocks.go is a non-test file of the mempool package, so its testify/mock
import linked testify and its dependencies (including the archived
gopkg.in/yaml.v3, until the testify bump) into the btcd binary. Move
the mock into a new mempool/mempooltest package, which only tests
import.

This is a breaking change for any external code that used
mempool.MockTxMempool: it is now mempooltest.MockTxMempool.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
AI review queuedmulti: bump testify to v1.12.1by Boris Nagaev · d49b8d0b · Oct 7, 2026 · 14 filesMessage 68 · AdequateInformational 19Details
Commit message · Boris Nagaev

multi: bump testify to v1.12.1

testify v1.12 replaces gopkg.in/yaml.v3, whose repository has been
archived since April 2025, with the maintained go.yaml.in/yaml/v3, and
no longer depends on pmezard/go-difflib. Both drop out of every module.
btcec moves from v1.8.0, the others from v1.10.0.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
signing or wallet pathsecond-pass: security-sensitive path
AI analysis · Informational 19/100

This commit updates the project's testing helper library (testify) to a newer version and swaps an old, archived YAML parsing dependency for a maintained one. It only touches build/dependency files (go.mod and go.sum) across several modules. There are no code changes to the Bitcoin node logic itself, and the commit message frames this as routine maintenance, not a security fix.

Lower-prioritydatabase: bump goleveldb to its latest upstream commitby Boris Nagaev · 3eb8d3fb · Oct 7, 2026 · 2 filesMessage 81 · StrongTriage 0Details
Commit message · Boris Nagaev

database: bump goleveldb to its latest upstream commit

The pinned goleveldb commit is from August 2021 and 18 commits behind
the last upstream commit (July 2022). The newer commits rotate the
MANIFEST file once it reaches 64 MiB instead of letting it grow until
the database is reopened, fix table files leaking when the manifest is
rotated (#409), and speed up the block cache and merged iterators.

A database written by the old version opens fine with the new one.

81/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Lower-prioritymulti: gofmt with Go 1.27by Boris Nagaev · ec6a8309 · Oct 7, 2026 · 2 filesMessage 68 · AdequateTriage 0Details
Commit message · Boris Nagaev

multi: gofmt with Go 1.27

Go 1.27's gofmt indents the composite literals of a multi-value return
statement differently, and v2transport/handshake_test.go was formatted
the old way. integration/p2a_test.go had a trailing blank line that
gofmt removes with any version. These are the only changes make fmt
makes with the Go 1.27.2 toolchain.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Lower-prioritybuild: bump golangci-lint and goimports for Go 1.27by Boris Nagaev · c1e26cef · Oct 7, 2026 · 1 fileMessage 85 · StrongTriage 0Details
Commit message · Boris Nagaev

build: bump golangci-lint and goimports for Go 1.27

The Makefile installs both tools with the local Go, which is now Go
1.27.2, and neither pinned version works with it:

- golangci-lint v2.1.6 builds, but fails to load any package ("export
data version 5 is greater than maximum supported version 2").
- goimports at the October 2024 x/tools commit doesn't build: it sets
the gotypesalias GODEBUG, which Go 1.27 removed.

Bump golangci-lint to v2.14.0 and goimports to x/tools v0.51.0, the
latest releases, which both build and run with Go 1.27.2.

85/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
AI review queuedwire: refresh stale decode docs, comments, and fuzz seedsby Olaoluwa Osuntokun · e449f2f4 · Oct 5, 2026 · 4 filesMessage 83 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

wire: refresh stale decode docs, comments, and fuzz seeds

In this commit, we fix the doc comments that still describe a scratch
buffer parameter named b. The Buf variants of the readers and writers
require the caller to pass a non-nil buffer, so the old 'If b is
non-nil' paragraphs described behavior these functions never had; each
now states simply that buf must be at least an 8-byte slice.

The truncated decode benchmarks gain comments explaining what each
payload prefix represents in the message encoding, such as the 4-byte
transaction version before the input count or the 80-byte block header
plus 4-byte transaction count before the merkle hash count. The
transaction input benchmark's prewarm comment also stops referring to
'this patch' and instead describes what the prewarm isolates: it warms
the chunk pool so the benchmark measures only the allocation made while
decoding rather than the one-time chunk creation.

The fuzz seeds are now cloned before being added to the corpus. f.Add
keeps a reference to the slice it is given, so reusing one buffer across
seeds overwrote the coinbase seed with the multi-input transaction
before the corpus entry ever ran, and the coinbase case was silently
never asserted.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
fuzzing or regression evidenceparser or protocol pathsecond-pass: security-sensitive path
AI analysis · Informational 15/100

This commit is a documentation and test-maintenance cleanup. It corrects outdated code comments that described an old scratch-buffer behavior, adds explanatory comments to benchmark tests, and fixes a fuzz-test bug where reused buffers caused one test seed to silently overwrite another. There are no changes to production logic or security-sensitive behavior.

AI review queuedwire: make decode budget tests assert what they describeby Olaoluwa Osuntokun · 12e3f98a · Oct 5, 2026 · 1 fileMessage 83 · StrongInformational 12Details
Commit message · Olaoluwa Osuntokun

wire: make decode budget tests assert what they describe

In this commit, we strengthen the decode budget tests so each one
actually verifies the property its comment claims.

The truncated vector test now asserts a decode reserves zero element
storage rather than comparing against an always-zero maxCap column, and
it covers MsgBlock.DeserializeTxLoc in addition to BtcDecode, closing
the one count-driven vector the table missed.

The streaming decode tests no longer silently take the preallocation
path: a bare bytes.Reader exposes its remaining length, which let the
decoders preallocate from the claimed counts. Both now wrap the reader
in readSizeRecorder, which hides the remaining length, and assert the
element vectors grew to only about twice the delivered count.

The truncated frame test now measures total bytes allocated across one
hundred truncated header reads and bounds them far below the claimed
payload, covering reservation as well as the already-checked read sizes.
The variable length prefix test gains a loop that claims the maximum
payload while delivering progressively more bytes, asserting the staged
reservation tracks what was delivered rather than the claim.

The readSizeRecorder helper moves next to the other test readers and
gains a doc comment explaining its two jobs: hiding the reader's
remaining length to force streaming, and recording the largest read
request to catch oversized speculative reads.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
parser or protocol pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Informational 12/100

This commit only changes test code. It strengthens existing tests that verify Bitcoin wire-protocol decoders do not reserve huge amounts of memory based on attacker-controlled length fields. No production code is modified, so it does not introduce or fix a runtime vulnerability by itself. It appears to be a follow-up that makes earlier decode-budget protections actually testable.

AI review queuedwire: derive arena chunk class without cursor stateby Olaoluwa Osuntokun · 1577c186 · Oct 5, 2026 · 7 filesMessage 73 · AdequateLow 35Details
Commit message · Olaoluwa Osuntokun

wire: derive arena chunk class without cursor state

In this commit, we remove the per-arena class field and its starting
class constants entirely. grow now derives the chunk size class from
the request itself on every call, choosing the smallest class that holds
both the allocation and one more byte than the current chunk, so
consecutive growths keep walking up the ladder without any cursor state
to maintain or reset across borrows, rewinds, and releases. The worst
case is four iterations of the class lookup.

This also removes the borrowScriptArena starting class parameter, since
without a cursor there is nothing to seed: every arena starts at the
smallest class and grows on demand. The rewind path no longer needs to
reposition a class cursor after retaining the largest chunk, and release
no longer needs to reset one.

alloc additionally rejects negative sizes with errScriptArenaFull. The
decode path never passes one, but the remaining budget check alone would
let a negative size through and panic on the slice bounds below it, so
the guard keeps alloc total on any input.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: broader security terminologysecond-pass: security-sensitive path
AI analysis · Low 35/100

This commit refactors a memory arena used when decoding Bitcoin transactions and blocks. It removes a chunk-size cursor and instead calculates the right chunk size on every allocation. It also adds a guard so negative allocation sizes are rejected instead of causing a panic. The change is primarily a robustness and maintainability improvement; it does not appear to fix an actively exploitable vulnerability, but it removes a class of potential panic/corruption bugs related to stale cursor state and negative sizes.

Security candidatetxscript: reject SIGHASH_SINGLE signing without a matching outputby Boris Nagaev · 99944777 · Oct 5, 2026 · 4 filesMessage 91 · StrongHigh 74Details
Commit message · Boris Nagaev

txscript: reject SIGHASH_SINGLE signing without a matching output

When SIGHASH_SINGLE has no output corresponding to the input being
signed, legacy signing uses the constant hash one and segwit v0 signing
commits to no outputs. These signatures can allow funds to be
redirected.

Reject this case in RawTxInSignature and RawTxInWitnessSignature with
ErrInvalidSigHashSingleIndex, including when ANYONECANPAY is set.
Their callers inherit the protection; multisig signing omits refused
signatures through its existing error handling, as SignTxOutput now
documents.

The check masks the hash type with sigHashMask (0x1f) like the sighash
code, where Core masks with 3; the two agree for the standard hash
types. When the matching output is absent, Core also refuses
non-standard types such as 0x07, 0x0b and 0x13. btcd's sighash treats
those like SIGHASH_ALL, committing to every output, so they are still
signed. This divergence is intentional.

Leave sighash calculation unchanged to preserve consensus verification.
Taproot signing already rejects this case.

Add regression coverage for P2PKH, bare multisig, P2SH-P2PKH,
P2SH-multisig, P2WPKH and P2TR across the six standard explicit sighash
types, checking both missing-output rejection and successful signing of
supported combinations. Also cover the raw ECDSA signers with
non-standard hash types: without a matching output, 0x23, 0x43 and 0xc3
are refused, while 0x07, 0x0b and 0x13 are still signed.

Port of Bitcoin Core PR bitcoin/bitcoin#35984:
https://github.com/bitcoin/bitcoin/pull/35984

91/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarydefensive validationconsensus or confidential-proof validationsigning or wallet path
AI analysis · High 74/100

This commit fixes a bug in btcd's transaction signing code. When a Bitcoin transaction is signed with the SIGHASH_SINGLE type, the signature normally commits to one specific output. If the input being signed has no matching output (for example, input index 1 when there is only one output), the signature would commit to nothing. That would let anyone holding the signature later change where the money goes while keeping the signature valid. The patch now refuses to create such signatures, preventing funds from being redirected.

AI review queuedwire: bound complete streaming payload growthby Olaoluwa Osuntokun · 34ad1221 · Sep 22, 2026 · 3 filesMessage 68 · AdequateLow 49Details
Commit message · Olaoluwa Osuntokun

wire: bound complete streaming payload growth

In this commit, we replace the bytes.Buffer streaming fallback with geometrically sized chunks capped by the remaining payload. bytes.Buffer.ReadFrom reserves additional space before its final EOF check, which lets a complete read retain capacity beyond the advertised length.

The chunked path allocates only as bytes arrive, returns a single chunk without copying for small messages, and joins larger messages into exact-sized storage once complete. Complete framed-message benchmarks cover ping and block payloads.

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
parser or protocol pathsecond-pass: security-sensitive path
AI analysis · Low 49/100

This commit changes how btcd reads message payloads from the Bitcoin peer-to-peer network. Previously, the code used a standard Go bytes.Buffer, which could reserve more memory than the actual message size after a complete read. The new code reads in bounded, geometrically growing chunks and returns an exactly sized byte slice. The commit message and tests frame this as a memory-budgeting improvement: preventing a complete, well-formed message from retaining hidden extra capacity. It is not a fix for a remote crash or code-execution vulnerability, but it removes a way that a peer could cause a node to hold more memory than the protocol advertises.

AI review queuedwire: assert block arena reuse across transactionsby Olaoluwa Osuntokun · 133e4897 · Sep 22, 2026 · 1 fileMessage 83 · StrongInformational 12Details
Commit message · Olaoluwa Osuntokun

wire: assert block arena reuse across transactions

In this commit, we add a block-level footprint assertion for both Deserialize and DeserializeTxLoc. The test decodes 1,000 small transactions through isolated chunk pools and requires a single 16 KiB staging chunk, so removing the per-transaction rewind now fails even when round-trip correctness remains intact.

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
Why it was queued
second-pass: broader security terminology
AI analysis · Informational 12/100

This commit only adds a new test to btcd. It does not change any production code. The test checks that when decoding a Bitcoin block containing many small transactions, the internal memory arena reuses a single chunk rather than allocating many chunks. It is a regression test for memory efficiency, not a fix for a security vulnerability.