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

btc: allow message signing under m/49

Public commit record

What the developer wrote

Authored by benma's agent

78/100 · Adequate
btc: allow message signing under m/49

Casa (casa.io) needs Bitcoin message signatures to verify control of
keys in the unhardened m/49 branch. The firmware currently rejects
these keypaths before prompting.

Accept m/49 and its descendants up to the existing limit of ten path
components. Use the same external service key confirmation as for m/45'
and m/48'.

Bump the firmware version to v9.30.0 for the two Bitcoin keypath changes.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit expands the BitBox02 hardware wallet's Bitcoin message-signing feature to also accept key paths starting with the unhardened purpose 'm/49'. Previously only hardened m/45' and m/48' were treated as valid 'external service' keypaths. The change is presented as a feature for Casa (casa.io) to verify control of keys. It is not a vulnerability fix; it is a deliberate relaxation of an access check, accompanied by tests and a version bump.

Recommended action

Review whether unhardened m/49 message signing aligns with the intended security model for external-service keys. Confirm that the UI warning clearly informs users they are signing on behalf of an external service, and that no other checks (e.g., script type compatibility) were inadvertently weakened. No immediate patch is indicated by the diff itself.

Security signals we found

01

Relaxation of keypath allowlist for message signing

02

Unhardened purpose m/49 added to external-service signing namespace

03

User confirmation prompt still required ('External service key')

04

Same depth limit (10 components) retained

05

Hardened m/49' explicitly rejected in tests

Risk score

Why this scored 30/100

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