Trezor Model T Passphrase Loss: 0.7175 BTC On-Chain, Inaccessible
BlockedWallet passphrase could not be recalled or recovered — access was permanently blocked.
In late December 2025, jwsutherland transferred approximately 0.7175 BTC from the Canadian exchange Newton to a native SegWit (bech32) address generated by a Trezor Model T hardware wallet. The transaction confirmed and the balance remained visible on the blockchain via Blockchair. However, when the user attempted to spend or access the funds, the Trezor Model T could not derive the address using the confirmed 12-word BIP-39 recovery seed and standard recovery procedures.
The user verified that they possessed only one Trezor device, the seed phrase was correct, and attempting an incorrect passphrase opened a valid but empty wallet—expected behavior under BIP-39 specification. These facts suggested the address had been created under a passphrase-protected hidden wallet, or the address derivation path (BIP44, BIP49, or BIP86 with specific account indices) was no longer reproducible from the Trezor interface.
Trezor Suite's design prevents loading additional accounts once an empty Bitcoin account exists, creating a practical barrier to systematic testing. Forum contributors suggested brute-force passphrase recovery using third-party tools and testing multiple derivation paths in Sparrow Wallet. Address verification was complicated by some block explorers incorrectly rejecting the bech32 format during initial diagnosis.
By December 29, 2025, no resolution was achieved. The incident exemplifies a custody vulnerability inherent to single-device, passphrase-protected hardware wallets: loss of one authentication factor (passphrase) combined with absence of pre-funding verification procedures creates permanent inaccessibility despite correct seed recovery and on-chain proof of ownership.
| Stress condition | Passphrase unavailable |
| Custody system | Hardware wallet with passphrase |
| Outcome | Blocked |
| Documentation | Partial |
| Year observed | 2025 |
| Country | Canada |
Why passphrases fail years after they are set
The failure mode documented consistently across observed cases is temporal: the passphrase is set with confidence, not used for an extended period, and then cannot be reproduced exactly when needed. A single character difference — different capitalization, an added space, a slightly different special character — produces a different wallet with a zero balance. The holder may be certain they remember the passphrase while being unable to produce the exact string that was originally set.
What makes this particularly difficult is that there is no signal at the moment of failure. A wrong passphrase does not produce an error message. It opens an empty wallet. The holder sees a zero balance and typically concludes the passphrase was wrong — but without knowing which part was wrong, or by how much.
Professional passphrase recovery services can attempt permutations when the holder has partial information: they remember the general structure, typical patterns they use for passwords, the approximate length, or that it included a specific word. Recovery from total non-recollection is not feasible.
The preventive action is to store a passphrase record — not with the seed phrase, which would defeat its security purpose, but in a separate secure location accessible to the holder and potentially a designated recovery person. A passphrase that exists only in memory has a time horizon: it will eventually be forgotten, and the timing is unpredictable.
Translate