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

bugfix: allow setting block_h from tmp seed

Public commit record

What the developer wrote

Authored by scgbckbone

45/100 · Thin
bugfix: allow setting block_h from tmp seed
✓ Descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This is a bugfix for the COLDCARD's 'SSSP' (a spending-policy/velocity-limit feature). Previously, when a user was operating with a temporary seed, the device could not update the stored 'last signed block height' after signing a transaction. That meant a temporary-seed session could not advance the anti-rollback counter, so later signing attempts could be wrongly rejected as 'rewound' or could, in some configurations, leave the velocity-limit tracking stale. The fix lets the block-height update be saved to the shared settings area even when the current active key is a temporary seed, rather than requiring the master seed's settings area.

Recommended action

Treat as a low-to-moderate security bugfix. Review that allowing `_master_only=False` for the block-height update does not inadvertently let a temporary seed overwrite other master-seed policy fields; the diff shows only `block_h` is updated this way, which is appropriate. Ensure the change is included in the next release and that the new regression tests pass.

Security signals we found

01

Fixes a functional bug in a security feature (velocity limit / anti-rollback tracking)

02

Changes persistence scope of a security-relevant setting (block_h) from master-only to allow temporary-seed updates

03

Moves SSSP block-height update out of CCC-exclusive branch so it always runs when SSSP is enabled

04

Adds regression tests for temporary-seed block-height updates and rewound-locktime detection

Risk score

Why this scored 44/100

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