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

SFT-8674: warned about timelocks when reviewing a transaction

Public commit record

What the developer wrote

Authored by Jack

85/100 · Strong
SFT-8674: warned about timelocks when reviewing a transaction

A transaction can be signed with a lock that stops it confirming until
a date, or until its inputs have aged, and the review never showed
either. The amounts can't change, but the payment can be held up
without the signer knowing.

Only those two cases are flagged. Most wallets set nLockTime to the
current block height on every transaction to deter fee sniping, and
Passport doesn't know the current height, so a height lock can't be
told apart from one far in the future. Flagging every height would put
a warning on almost every transaction.

The date is computed directly because utime counts from 2000 on this
port, so utils.timestamp_to_str would be 30 years off for a Unix time.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Explains rationale or failure mode
The short version

What changed, and why it matters

This commit adds on-screen warnings to the Passport hardware wallet when a Bitcoin transaction being reviewed includes a timelock that could delay confirmation. Before this change, a user could unknowingly sign a transaction that is blocked from confirming until a future date or until its inputs have aged. The amounts cannot change, but the payment can be held up. The fix flags only date-based and relative timelocks, not the common anti-fee-sniping block-height locks that most wallets set.

Recommended action

Users should update to firmware containing this commit and carefully read any new 'Timelock' or 'Relative Timelock' warnings during transaction review. Wallet coordinators and reviewers should verify that legitimate timelocked transactions now display the expected delay information.

Security signals we found

01

UI now warns users about transaction timelocks that delay confirmation

02

Previously undisclosed to the signer: absolute date locks and BIP68 relative locks

03

Height-based nLockTime intentionally not flagged to avoid warning fatigue

04

Custom UTC formatting avoids 30-year epoch offset bug on device

05

New test coverage for both flagged and non-flagged timelock cases

Risk score

Why this scored 52/100

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