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

psbt: assume final sequence when PSBT_IN_SEQUENCE is omitted

Public commit record

What the developer wrote

Authored by Sjors Provoost

75/100 · Adequate
psbt: assume final sequence when PSBT_IN_SEQUENCE is omitted

get_unsigned_tx() asserted that every input has a sequence number,
crashing on the minimal BIP 370 test vector.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit fixes a crash in the PSBT (Partially Signed Bitcoin Transaction) handling code. When a transaction input did not specify a sequence number, the software would crash with an assertion failure instead of assuming the standard default value (0xffffffff). The fix makes the code follow the BIP 370 specification correctly, allowing it to handle minimal PSBTv2 files without crashing.

Recommended action

Apply the patch. It is a low-risk correctness fix that improves robustness when processing externally supplied PSBTv2 files. No immediate security incident response is indicated, but users parsing untrusted PSBTs should update.

Security signals we found

01

Denial-of-service vector: assertion failure on malformed/minimal PSBT input

02

Non-compliance with BIP 370 default sequence semantics

03

Crash triggered by external PSBT data (parser robustness issue)

Risk score

Why this scored 35/100

Our methodology →
Potential impact 8/30
Exploitability 5/25
Stealth signal 4/15
Affected reach 6/15
Confidence 8/10
Evidence quality 4/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.