AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 26 Bitcoin

coinselection: Track whether BnB completed

Public commit record

What the developer wrote

Authored by Murch

68/100 · Adequate
coinselection: Track whether BnB completed

BnB may not be able to exhaustively search all potentially interesting
combinations for large UTXO pools, so we keep track of whether the
search was terminated by the iteration limit.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit changes how Bitcoin Core's coin-selection algorithm tracks whether it finished its search. Previously, the code created the result object after the loop, so it could not record whether the Branch-and-Bound (BnB) search hit its iteration limit or completed the full search. The patch moves the result object earlier and marks it 'completed' or 'not completed' inside the loop. This is a correctness/observability improvement for fee estimation and coin-selection diagnostics, not a direct fix for a remote exploit. It could matter for security indirectly: if BnB aborts early, the wallet may fall back to a less optimal selection, possibly paying higher fees or creating larger change, but there is no evidence in the commit of a vulnerability being disclosed or exploited.

Recommended action

Treat as a routine correctness improvement. Review whether downstream callers of SelectionResult::GetAlgoCompleted (or equivalent) handle the 'not completed' case appropriately, especially for fee-bump and privacy-sensitive transactions. No urgent security patch is indicated by this commit alone.

Security signals we found

01

No explicit security relevance stated in commit title or message

02

No CVE, advisory, or researcher attribution in commit

03

Change is observability/correctness: tracking algorithm completion state

04

Potential indirect security relevance: incomplete BnB search can lead to suboptimal UTXO selection, higher fees, or privacy-affecting change outputs

05

No memory safety, cryptographic, or network-layer changes

Risk score

Why this scored 26/100

Our methodology →
Potential impact 5/30
Exploitability 3/25
Stealth signal 4/15
Affected reach 5/15
Confidence 6/10
Evidence quality 3/5
Human-validated context

Community notes

Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.

No validated notes yet.

The AI analysis stands alone for now. Submit a note if you can add evidence or important context.