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 51 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.

Security candidatebuild: pin v0.27.0 nested module releasesby Olaoluwa Osuntokun · 01a9e591 · Oct 21, 2026 · 2 filesMessage 80 · StrongInformational 0Details
Commit message · Olaoluwa Osuntokun

build: pin v0.27.0 nested module releases

In this commit, we pin the newly published wire, btcec, address, txscript, and btcutil patch releases in the root module. This makes a normal btcd build include the fixes already merged into the repository, without relying on the in-tree module workspace. We also tidy the checksums and drop the obsolete Android anet dependency.

80/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
Why it was queued
access control
AI analysis · Informational 0/100

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 already merged elsewhere, but the actual code changes shown are purely bookkeeping.

AI review queuedMerge pull request #2611 from yyforyongyu/task-btcutil-auditby Olaoluwa Osuntokun · e799ee42 · Oct 21, 2026 · 7 filesMessage 73 · AdequateModerate 61Details
Commit message · Olaoluwa Osuntokun

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

multi: reject inconsistent UTXOs and invalid keys

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Moderate 61/100

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 of which are unusable and could previously be returned silently. Second, it makes PSBT fee calculation reject inconsistent UTXO descriptions, so a malicious or buggy PSBT cannot report one input value via its non-witness UTXO and a different value via its witness UTXO. These are defensive hardening fixes rather than active remote-exploitable bugs.

Security candidateMerge pull request #2655 from yyforyongyu/task/txscript-signature-validationby Olaoluwa Osuntokun · a72ace10 · Oct 21, 2026 · 4 filesMessage 78 · AdequateModerate 57Details
Commit message · Olaoluwa Osuntokun

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

txscript: align signature opcode validation

78/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference✓ Names security-relevant behavior explicitly
Why it was queued
signing boundarymerge-commit duplicate discount
AI analysis · Moderate 57/100

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 so it only matches actual data pushes. These changes reduce the chance that an attacker could craft a transaction that passes validation when it should fail, or that future script versions accidentally inherit today's rules.

Security candidatetxscript: align signature opcode validationby yyforyongyu · 8a2b9165 · Oct 21, 2026 · 4 filesMessage 50 · ThinModerate 69Details
Commit message · yyforyongyu

txscript: align signature opcode validation

50/100 · ThinMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Names security-relevant behavior explicitly! No meaningful explanatory body
Why it was queued
signing boundary
AI analysis · Moderate 69/100

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 rule that prevents signatures from being removed from the script they are signing, and restricts a special 'OP_SUCCESS' shortcut to the standard Tapscript leaf type. These are consensus- and policy-sensitive changes: getting them wrong could let an attacker craft a transaction that btcd accepts but other Bitcoin nodes reject, or vice versa, potentially causing chain splits or funds loss.

AI review queuedMerge pull request #2654 from Roasbeef/build/go-1.27.3by Olaoluwa Osuntokun · a1cc50bd · Oct 21, 2026 · 15 filesMessage 58 · ThinLow 44Details
Commit message · Olaoluwa Osuntokun

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

build: upgrade Go toolchain to 1.27.3

58/100 · ThinMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Links an issue, advisory, or supporting reference! No meaningful explanatory body
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: security-sensitive path
AI analysis · Low 44/100

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 CVE-2026-111943, which affects Go 1.27.0 through 1.27.2. The commit itself only changes version numbers and documentation; it does not contain the actual Go security fix. It is a routine dependency/security maintenance patch.

Security candidatebuild: upgrade Go toolchain to 1.27.3by Olaoluwa Osuntokun · 887de811 · Oct 21, 2026 · 15 filesMessage 88 · StrongLow 33Details
Commit message · Olaoluwa Osuntokun

build: upgrade Go toolchain to 1.27.3

In this commit, we upgrade CI, Docker builds and release binaries to Go 1.27.3. This release adds the crypto/x509 mitigation for CVE-2026-111943, which distrusts affected intermediate CA keys. We also move every module language version to Go 1.26.10, the latest release on the previous supported branch.

88/100 · StrongMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
Why it was queued
explicit security languagesigning or wallet path
AI analysis · Low 33/100

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 crypto/x509 package for CVE-2026-111943, which blocks trust in some compromised certificate authority keys. The actual code changes are only version number updates in build files; there are no direct changes to btcd's own security logic.

Security candidateMerge pull request #2628 from fametrano/musig2-bip327-vectorsby Olaoluwa Osuntokun · ec47ee12 · Oct 21, 2026 · 7 filesMessage 83 · StrongInformational 15Details
Commit message · Olaoluwa Osuntokun

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

btcec/schnorr/musig2: refresh BIP 327 test vectors

83/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification✓ Links an issue, advisory, or supporting reference
Why it was queued
secret or key materialfuzzing or regression evidencesigning or wallet pathmerge-commit duplicate discount
AI analysis · Informational 15/100

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 how the tests read them. There is no indication of a security vulnerability being fixed.

AI review queuedMerge pull request #2627 from starius/bump-depsby Olaoluwa Osuntokun · c615bd70 · Oct 12, 2026 · 52 filesMessage 68 · AdequateLow 46Details
Commit message · Olaoluwa Osuntokun

Merge pull request #2627 from starius/bump-deps

multi: update dependencies and fix RPC, Tor, and cross-build failures

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathmerge-commit duplicate discountsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Low 46/100

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 security fixes by themselves, but a few areas have clear defensive value: websocket authentication now has size limits and a timeout, websocket writes have a timeout, SOCKS/Tor proxy handling was rewritten, and peer inventory is now compared by value rather than by pointer. The commit does not describe itself as a security patch and no CVE is mentioned.

Security candidaterpcserver: detect unexpected replies before websocket shutdownby Olaoluwa Osuntokun · b67710c7 · Oct 12, 2026 · 1 fileMessage 88 · StrongLow 31Details
Commit message · Olaoluwa Osuntokun

rpcserver: detect unexpected replies before websocket shutdown

In this commit, we read from the client before waiting for the server to
finish handling the connection. Waiting first let the authentication
timeout close an unread pipe and hide a reply queued for an
unauthenticated malformed request.

With both pre-authentication guards removed, the old test still passed.
The updated helper catches the unexpected replies for both single and
batch requests.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
access control
AI analysis · Low 31/100

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 was queued for an unauthenticated, malformed request. The change makes the test correctly detect unexpected replies, but it is a test-only fix; the underlying server behavior is not changed.

Security candidatebtcec/schnorr/musig2: refresh BIP 327 test vectorsby Ferdinando Ametrano · f237e882 · Oct 9, 2026 · 7 filesMessage 88 · StrongInformational 15Details
Commit message · Ferdinando Ametrano

btcec/schnorr/musig2: refresh BIP 327 test vectors

Update the vectors under data/ to the current ones in bitcoin/bips
(bip-0327/vectors at 927b6de9, last changed in 1c6ac0c4):

- nonce_gen: rand_ is now 0F..0F, and the expected secnonce and
pubnonce are given separately.
- sign_verify: new valid cases with an empty and a 38-byte message,
a longer invalid pubnonce, and new signatures in the verify cases
after the "Fix the four test vectors" change.
- key_sort: one more key.
- sig_agg: the error case now names its contributor.

Test changes:

- The nonce generation test reads rand_ from the vector and checks
the pubnonce as well as the secnonce.
- The verify-fail test ignored signer_index and always checked the
signature against the first signer, so the "Wrong signer" case did
not fail with the corrected signature. It now uses the nonce and
key at signer_index.
- The unused memsetRandReader is removed.
- The two valid cases with a message that is not 32 bytes are skipped,
as Sign takes a 32-byte message.

88/100 · StrongMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification✓ Names security-relevant behavior explicitly
Why it was queued
signing boundaryfuzzing or regression evidencesigning or wallet path
AI analysis · Informational 15/100

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 was always checked against the first signer instead of the intended signer, and removes an unused test helper. No production code is changed, so this does not affect real users or introduce a security vulnerability.

Security candidateMerge pull request #2625 from starius/port-35984by Olaoluwa Osuntokun · bbeb9d41 · Oct 9, 2026 · 4 filesMessage 68 · AdequateModerate 64Details
Commit message · Olaoluwa Osuntokun

Merge pull request #2625 from starius/port-35984

txscript: reject SIGHASH_SINGLE signing without a matching output

68/100 · AdequateMessage clarity
✓ Descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing boundarysigning or wallet pathmerge-commit duplicate discount
AI analysis · Moderate 64/100

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 remains valid even if someone later changes where the money goes, as long as no output exists at that input's index. The patch now refuses to produce such signatures, preventing wallets or automated tools from accidentally creating signatures that could be reused to redirect funds.

AI review queuedMerge pull request #2565 from Roasbeef/wire-script-arenaby Olaoluwa Osuntokun · 6c52a019 · Oct 9, 2026 · 30 filesMessage 73 · AdequateModerate 61Details
Commit message · Olaoluwa Osuntokun

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

wire: replace 4 MiB script slab with tiered arena allocator

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
Why it was queued
signing or wallet pathparser or protocol pathmerge-commit duplicate discountsecond-pass: unusually broad changesecond-pass: security-sensitive path
AI analysis · Moderate 61/100

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 claims to contain many elements but the data is truncated. The change is primarily defensive: it reduces memory waste and makes malformed messages harder to turn into memory-exhaustion attacks. A small fix in the RPC client also stops a local validation helper from mutating caller-owned transactions.

AI review queuedrpcclient: preserve transactions during mempool accept validationby Olaoluwa Osuntokun · 81d3555d · Oct 8, 2026 · 2 filesMessage 83 · StrongLow 34Details
Commit message · Olaoluwa Osuntokun

rpcclient: preserve transactions during mempool accept validation

In this commit, we validate serialized transactions with a temporary MsgTx instead of decoding back into the caller's object. TestMempoolAcceptAsync now preserves the supplied transactions on both successful validation and local decode errors.

The regression checks transaction contents and input/output identity, rejection without an outbound request, and the transaction bytes and fee limit queued for a valid request.

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
defensive validationsigning or wallet pathsecond-pass: near security thresholdsecond-pass: security-sensitive path
AI analysis · Low 34/100

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 function decode into a temporary copy instead of the caller's original object, so users' transactions remain unchanged. The included tests verify the original transaction is preserved on both success and failure paths.

AI review queuedwire: clear transaction scripts on decode errorsby Olaoluwa Osuntokun · 6651b8f3 · Oct 8, 2026 · 4 filesMessage 78 · AdequateModerate 61Details
Commit message · Olaoluwa Osuntokun

wire: clear transaction scripts on decode errors

In this commit, we clear TxIn and TxOut before a failed public transaction decode releases its script arena. This prevents the partially decoded receiver from retaining slices into memory that later decodes can reuse, while keeping the block decoder's internal path unchanged.

The regression covers every truncated prefix in base and witness encodings with buffered and streaming readers, then checks a successful retry into the same receiver. We also inspect the internal decoder in the allocation-budget test so error cleanup cannot hide excessive reservations.

78/100 · AdequateMessage clarity
✓ 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: security-sensitive path
AI analysis · Moderate 61/100

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 scripts. That arena would then be reused for later decodes, meaning stale or attacker-controlled data could leak between unrelated transactions. The fix clears the transaction's inputs and outputs on any public decode error before returning the arena to the pool. The commit also adds tests covering every truncated prefix and both buffered and streaming readers.

Security candidatemulti: switch to github.com/decred/dcrd/container/lruby Boris Nagaev · eb8c6c94 · Oct 8, 2026 · 6 filesMessage 73 · AdequateInformational 15Details
Commit message · Boris Nagaev

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

github.com/decred/dcrd/lru is deprecated in favor of
github.com/decred/dcrd/container/lru, which provides typed generic
caches. Use a Set for the known inventory, sent nonces, known addresses
and v1 downgrade addresses, and a Map for the per-source v2 handshake
limiters, which removes a type assertion.

Lookups keep their semantics: Set.Contains and Map.Get mark the item as
most recently used, like Cache.Contains and KVCache.Lookup did.

73/100 · AdequateMessage clarity
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
Why it was queued
update trust
AI analysis · Informational 15/100

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 change.

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.

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.

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.

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.

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.