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

psbt: enforce required locktime bounds

Public commit record

What the developer wrote

Authored by Sjors Provoost

45/100 · Thin
psbt: enforce required locktime bounds
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This change makes the hardware-wallet interface library stricter when reading PSBT (Partially Signed Bitcoin Transaction) files. It now rejects locktime values that don't follow Bitcoin's rules: a time-based locktime must be at least 500,000,000, and a block-height-based locktime must be greater than 0 and less than 500,000,000. Without these checks, a malformed or malicious PSBT could confuse a hardware wallet about when a transaction is allowed to be mined, potentially leading to signing something the user didn't expect.

Recommended action

Review whether any other PSBT implementations or downstream hardware-wallet clients need the same locktime-bound validation, and ensure the new test vectors are exercised in CI. Consider adding explicit documentation or release-note mention of the stricter parsing.

Security signals we found

01

Input validation added to PSBT deserialization

02

Enforcement of Bitcoin locktime semantics boundary (500000000)

03

New negative test cases for invalid locktime combinations

04

Potential for PSBT parsing confusion / unexpected signing behavior before patch

Risk score

Why this scored 47/100

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