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

PSBTv2 per input required lock time calculation

Public commit record

What the developer wrote

Authored by scgbckbone

45/100 · Thin
PSBTv2 per input required lock time calculation
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds support in the COLDCARD firmware for a newer Bitcoin transaction format feature (PSBTv2) that lets each input specify its own required lock time. Before this change, the device did not correctly compute the final transaction lock time from these per-input requirements, which could cause it to sign transactions with the wrong lock time or reject valid ones. The patch implements the BIP-370 rule: if any input requires a lock time, the transaction's final lock time must be the most restrictive (maximum) of those requirements, overriding any fallback. This is a correctness/feature fix rather than a remote exploit, but incorrect lock-time handling could in theory let a malicious co-signer or wallet software trick a user into signing a transaction that becomes spendable earlier or later than expected.

Recommended action

Review the locktime computation logic for off-by-one and boundary conditions, ensure user-facing warnings accurately reflect the computed lock time, and confirm that the assertion-based rejection surfaces a clear error message rather than a crash. Continue monitoring for related PSBTv2 fields that may need similar handling.

Security signals we found

01

PSBTv2 per-input locktime parsing and validation added

02

BIP-370 required locktime computation implemented

03

Incompatible height/time locktime requirements rejected with assertion

04

Required locktimes override global fallback locktime

05

New test coverage for locktime edge cases

Risk score

Why this scored 34/100

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