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

bugfix: ownership check needed re-run for values near max

Public commit record

What the developer wrote

Authored by scgbckbone

50/100 · Thin
bugfix: ownership check needed re-run for values near max
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a bug in the COLDCARD hardware wallet's address-ownership cache. When users tried to verify they owned an address with a very high index (near the cache limit of about 760), the first check could wrongly fail and only succeed on a second attempt. The patch also refactors how addresses are saved to the cache so exports starting in the middle of the range don't leave gaps, and it tightens BIP-21 URL parsing. The bug is a reliability issue rather than a direct theft path, but it could mislead a user into thinking a valid receive address is not theirs.

Recommended action

Treat this as a routine firmware bugfix with minor security-reliability implications. Users should upgrade to the firmware release containing this commit. Developers should verify the new ownership tests pass and that the BIP-21 parser change does not break valid payment URLs. No immediate incident response is warranted unless a user reports having rejected a valid address because the ownership check initially failed.

Security signals we found

01

Bugfix explicitly described in commit message and changelog as 'Ownership check failing to find addresses near max (~760), needed to be re-run to succeed'

02

Refactored address cache generation to avoid premature termination and cache gaps

03

Ownership search now returns provenance flag (from_cache vs freshly generated)

04

BIP-21 parser tightened to require lowercase 'bitcoin' scheme and parse query parameters before scheme

05

Multisig wallet matching now accepts a list of address formats, reducing false negatives for P2SH-wrapped segwit

06

New and expanded pytest coverage for boundary indices 760, 763, 764 and partial cache scenarios

Risk score

Why this scored 46/100

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