Trezor Safe 3 & Safe 5 Invalid Recovery Seed (SLIP-39 vs BIP-39)
An "Invalid recovery seed" error on Trezor Safe 3 or Safe 5 typically indicates confusion between standard BIP-39 (12 or 24 words) and Shamir Backup SLIP-39 (20 or 33 words). Trezor Safe devices support both standards, but SLIP-39 uses an entirely different 1,024-word dictionary. Entering SLIP-39 words into a BIP-39 prompt results in immediate word rejections. Ensure you select the exact backup protocol used during device creation.
# Root Cause & Technical Architecture
Trezor Safe 3 and Safe 5 support multi-share Shamir backups defined by SatoshiLabs in SLIP-39. SLIP-39 phrases are composed of 20 or 33 words chosen from a specialized 1,024-word vocabulary designed for acoustic and visual clarity. BIP-39, in contrast, uses 12, 18, or 24 words from a 2,048-word dictionary. If a user initiates a standard BIP-39 recovery and enters SLIP-39 share words, the device throws invalid word errors because words like "academic" or "shrink" may have different index mappings or be missing entirely.
# 4-Step Actionable Diagnostic Protocol
Step-by-Step ResolutionIdentify Backup Standard: Count Total Words per Share
Count the words on your recovery sheet. 12 or 24 words indicate standard BIP-39. Exactly 20 or 33 words indicate SLIP-39 Shamir Backup.
Select Matching Restoration Mode in Trezor Suite
During device recovery setup in Trezor Suite, explicitly choose "Standard recovery" for BIP-39 or "Shamir recovery" for SLIP-39 before typing any words.
Verify SLIP-39 Threshold Requirements
If restoring a Shamir backup, ensure you have reached the required threshold of shares (e.g., 2 of 3 shares). Entering the same share twice will fail initialization.
Check Safe 3/5 Secure Element PIN Entry
Ensure the on-device touchscreen (Safe 5) or tactile buttons (Safe 3) are used to enter seed words directly onto the hardware, never into your computer browser or desktop keyboard.
# Diagnostic Verification Code / Command
textCryptographic Wordlist Specification Matrix:
Standard: BIP-39
Word Counts: 12, 18, 24 words
Dictionary Size: 2,048 words
Checksum: 4 to 8 bits SHA-256
Standard: SLIP-39 (Shamir Backup)
Word Counts: 20 or 33 words per share
Dictionary Size: 1,024 words
Checksum: 30-bit Reed-Solomon polynomial over GF(1024)Launch BIP-39 Checksum Solver
Execute client-side cryptographic simulation and parameter checks safely in your browser via native WebCrypto without sending private keys or mnemonics over the wire.
Read Full Investigation & Recovery Workflow
Explore complete architectural diagrams, edge-case failure trees, and detailed post-mortem analysis in our verified deep guide.
# Related Diagnostic Codes in Hardware & BIP-39
Related Hex StatusesLedger Stax 24-Words Invalid, Seed Phrase Typo & Wrong Word
Fix Ledger Stax 24-words invalid error and seed phrase typos. Resolve E-Ink capacitive touch entry slips, SHA-256 checksum failure, and Recovery Check.
Ledger Nano X 24-Words Invalid, Seed Phrase Wrong Word & Typo
Fix Ledger Nano X 24-words invalid and wrong word errors. Troubleshoot dual-button debounce skips, BIP-39 stem swaps, and Recovery Check validation.
Ledger Nano S Plus (S+) 24-Words Typo & Seed Phrase Wrong Word
Fix Ledger Nano S Plus 24-words typo and wrong word alerts. Resolve 2048-wordlist prefix autocomplete traps, button misses, and checksum verification.
# Frequently Asked Questions
FAQ SchemaCan I restore a 20-word Trezor Shamir backup onto a Ledger?
No. Ledger devices do not natively support SLIP-39 Shamir recovery shares without third-party offline conversion tools, as Ledger utilizes standard BIP-39.
How does Trezor Safe 5 verify a Shamir seed phrase?
Trezor Safe 5 uses a 30-bit Reed-Solomon polynomial checksum that can detect up to 3 typographical errors or 4 transpositions within any 20-word share.
What is the purpose of the Secure Element in Trezor Safe 3 and Safe 5?
The Secure Element (OPTIGA Trust M) protects against physical PIN brute-forcing and voltage glitching attacks, keeping your seed encrypted at rest.