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

ledger: support BIP388 policy signing

Public commit record

What the developer wrote

Authored by Sjors Provoost

68/100 · Adequate
ledger: support BIP388 policy signing

Reconstruct each registered wallet policy and pass its registration HMAC
when signing the PSBT. Inferred policies continue to be signed alongside
registered policies.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit updates the Ledger hardware wallet support in HWI so that newer Ledger devices can sign Bitcoin transactions using registered BIP388 wallet policies. Previously, any attempt to use registered descriptors with a Ledger was blocked with an error. The change removes that blanket block for modern Ledger apps and adds logic to reconstruct each registered wallet policy and include its registration proof when signing. Inferred policies still work as before. This is a feature addition, not a fix for an active vulnerability, but it touches security-sensitive signing code.

Recommended action

Review the WalletPolicy reconstruction logic for correctness, ensure the registration HMAC is validated before signing, and confirm that descriptor-derived address types cannot be manipulated to downgrade security. Consider adding tests covering registered-policy signing on both legacy and modern Ledger clients.

Security signals we found

01

Change removes an explicit error path for registered descriptors, increasing supported functionality

02

Adds reconstruction of registered wallet policies and propagation of registration HMACs during PSBT signing

03

Touches hardware-wallet signing path where incorrect policy handling could lead to signing unintended transactions

04

No explicit bug fix or vulnerability disclosure in commit message or diff

Risk score

Why this scored 31/100

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