An empty wallet after entering a passphrase does not establish that the original funds have disappeared. With a BIP39 passphrase, a different entry produces a different wallet. A typing error can therefore lead to an apparently successful opening with no familiar balance, rather than an incorrect-password warning.
| What you need to know |
|---|
| A BIP39 passphrase is an optional input alongside the recovery words. |
| Different passphrases produce different valid wallets. |
| Trezor says passphrases are case-sensitive and are not stored on the device. |
| Access to the same hidden wallet requires the original backup and exact passphrase. |
The BIP39 specification describes how mnemonic recovery words are converted into a seed. An optional passphrase participates in that conversion; without one, the passphrase input is an empty string. The document explicitly says every passphrase generates a valid seed. This is why a wallet opening successfully is a weak test of whether the intended passphrase was supplied.
A different wallet can look like a failed recovery
Imagine a person who created a hidden wallet, received funds there and later restored the recovery words. If they now supply a different passphrase, the specification’s rule leads to a different seed. An empty result would fit that mismatch. It would not, on its own, distinguish a typing error from a deliberately separate wallet or prove what happened to the original assets. This is a hypothetical comparison, not an account of a particular recovery.
Trezor’s passphrase guide makes the user-facing consequence explicit: a mistyped passphrase opens a different wallet, most likely an empty one. It also says the entries are case-sensitive. The device does not store the passphrase, and access to the same hidden wallet needs both the correct wallet backup and the exact original passphrase. Restoring the words alone therefore leaves one required input unresolved.
There are two separate checks in that example. First, did the restored backup reproduce the wallet setup? Second, did the passphrase reproduce the particular hidden wallet? A successful screen transition only answers whether the software accepted the current input. It does not answer the second question. Keep those questions separate when describing the problem to support; “my wallet opened” and “my expected wallet opened” convey different evidence.
Trezor warns that a forgotten passphrase cannot be recovered and recommends keeping a secure record and testing it. Its documentation also treats the feature as an advanced, optional choice. The protection brings an additional recovery dependency: the words and passphrase must both remain available to the owner. An extra secret is useful only if the owner can preserve it accurately enough to reopen the intended wallet.
This explanation concerns BIP39 passphrases and the documented Trezor implementation. It does not establish that every wallet password follows the same design. Before interpreting an empty result, identify which feature the wallet calls a password or passphrase and consult that product’s recovery instructions. The diagnostic question is whether the original inputs were reproduced, not whether the application displayed a password error.
