Recovery phrase invalid error when restoring crypto wallet
Every cryptocurrency wallet restore starts with words. Twelve or twenty-four of them. But not every set of twelve words works; the 'recovery phrase invalid' error is one of the most common roadblocks in self-custody, and understanding why it happens means understanding how wallets actually create and validate these phrases.
The BIP39 standard defines a fixed list of 2048 words. Your wallet generates its phrase from that list. Each word maps to an 11-bit number. Combine those bits, and you get entropy plus a checksum. The checksum is four bits for 12-word phrases, eight bits for 24-word phrases. It means not every random twelve words form a valid phrase; the wallet checks the checksum before it does anything else.
Metaphor: your phrase must be a valid entry code. Typing nonsense is rejected outright.
Common Failure Modes
Typos and spelling errors top the list. Wallets expect exact BIP39 words. "Abandom" instead of "abandon" fails. Trust Wallet and MetaMask both enforce strict word matching; one wrong character blocks the entire restore.
Wrong word order is the second most frequent cause. A recovery phrase is sequential. Words in any other order produce different entropy. The wallet does not guess. It reads position one as entropy bit one. Shift a single word, and the checksum likely fails. Even if it passes, the derived keys will not match your original address.
Words from different phrases happens when someone writes down parts of multiple generated phrases. Putting word three from phrase one with word four from phrase two creates invalid checksums almost every time.
Clipboard malware replacing addresses is a distinct but related attack. This replaces copied addresses after a restore completes. The wallet restores fine, but funds sent to the clipboard address go to the attacker. This is not a recovery phrase invalid error; it produces a successful restore with a hijacked destination.
Wrong derivation path explains the most confusing scenario: the phrase restores, the wallet shows zero balance, but the phrase is correct. Ledger Live, Trezor Suite, and MetaMask all allow custom derivation paths. BIP44 defines paths like m/44'/60'/0'/0/0 for Ethereum. Different wallets sometimes default to different paths. Exodus and Blockchain.com use their own defaults. The error is not "invalid phrase." It is "private key does not match address." The phrase is valid. The derived addresses are wrong.
Wallet-Specific Restore Flows
MetaMask validates the phrase against the BIP39 list during input. It rejects non-list words immediately. After accepting the phrase, it scans standard Ethereum derivation paths. If balance shows zero, you may need to search additional paths manually.
Trust Wallet follows the same BIP39 checksum validation. It also supports multiple blockchains. A phrase that works for Bitcoin may not list an Ethereum balance unless you add the Ethereum wallet within the app.
Ledger devices enforce checksum validation on the hardware itself. The device screen shows each word. A typo cancels the entire entry. Ledger Live software only interacts with the device - it never sees the raw phrase. If the device accepts the phrase but shows wrong addresses, the derivation path is the likely culprit.
Trezor works similarly. Firmware validates checksums. Trezor Suite supports passphrase-protected wallets. A missing or wrong passphrase produces different addresses entirely, even with the same base phrase.
Exodus stores its own derivation path defaults. Restoring a phrase originally created on a Ledger often requires manually selecting the path. Exodus will not show an "invalid phrase" error; it restores successfully but shows zero balance.
Blockchain.com wallet uses its own non-standard derivation paths for some assets. Their support documentation acknowledges this. A phrase that works on other wallets may fail here if the addresses were derived using Blockchain.com's custom paths.
What to do when you see this error
Check the exact spelling of every word. Verify each against the BIP39 word list. Confirm the word order matches your original backup. If you wrote the words in a different order, or guessed a missing word, the error is expected.
If the phrase passes but shows zero balance, do not assume loss. Try different derivation paths. Most wallets offer an "advanced restore" or "search paths" option. Ledger Live, Trezor Suite, and MetaMask all have this capability. Start with the path your original wallet used.
The most important distinction: "recovery phrase invalid" means the phrase itself fails checksum validation. "Private key does not match address" means the phrase is valid but derives keys for a different wallet. These require different solutions. The first needs a correct phrase. The second needs the correct derivation path.
No wallet can invent missing words. No support team can bypass checksum logic. The validation is code-level, hard-coded into every BIP39 implementation. If you cannot find the exact phrase in the exact order, that wallet is lost. The checksum gives you certainty: if it passes, the phrase is structurally sound. The only question is whether it is the right phrase for your address.
Not financial advice. michimeme.com publishes market data and general information about michi. Crypto assets are volatile and you can lose everything you put in. Nothing here is a recommendation to buy, sell or hold, and we make no price predictions.
Prices are sourced from third parties and may be delayed or wrong. Verify anything you intend to act on against a primary source.