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

feat(core,legacy): restrict xpub export

Public commit record

What the developer wrote

Authored by Petr Susil

80/100 · Strong
feat(core,legacy): restrict xpub export

Quantum computers may break exported xpubs. Warn before exporting xpubs
shallower than 2 levels (except known third-party paths) and of SLIP-15,
SLIP-16 and BIP-85.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 0b594247cd3342949b4888bb1f4e89dc641f8384)
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a warning to Trezor devices when a user tries to export an extended public key (xpub) from a path that is considered risky in a future quantum-computing scenario. It does not block the export, but it makes the user confirm they understand the risk. The affected paths are very shallow ones (less than two derivation levels) and paths used for encryption keys or derived passwords (SLIP-15, SLIP-16, BIP-85). Some well-known third-party uses of shallow paths are allowed without a warning. This is a hardening change, not a fix for an active bug or exploit.

Recommended action

Users should upgrade to a firmware version containing this commit if they want the additional warnings. Developers integrating with Trezor should review whether their xpub export paths are on the allowed-purpose whitelist; if not, their users will see a new warning. No immediate mitigation is required for currently deployed devices because the threat model is future quantum-computing based and the export is not blocked.

Security signals we found

01

New user-facing warning for xpub export from restricted derivation paths

02

Restricted paths include SLIP-15, SLIP-16, BIP-85, and paths shorter than two levels

03

Hardening is explicitly not treated as protection against a quantum attacker

04

Allowed-purpose whitelist preserves compatibility with third-party workflows

05

Tests added for both allowed and restricted paths, including confirmation/rejection flows

06

Changelog entries tagged as .security

Risk score

Why this scored 46/100

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