Glossary
A wallet passphrase is an optional word added on top of the seed phrase, creating an entirely separate wallet from the same 12 or 24 words. It is a plausible-deniability layer - and a second thing that can be lost with no recovery path.
A passphrase is an optional extra word or sentence combined with a wallet's seed phrase during key generation. The seed phrase alone produces one wallet; the same words plus a passphrase produce an entirely different one, with different addresses and no connection between them. The passphrase is sometimes called the 25th word because it joins the 12 or 24 recovery words as part of the key itself.
The feature exists for plausible deniability: a hidden wallet that a thief who finds your seed phrase cannot recover, because they hold 24 of the 25 pieces and do not know the 25th exists. The trade-off is severe. There is no reset, no recovery, and no error message for a wrong passphrase - a mistyped one derives a different, valid, empty wallet. For Australian readers, ASIC MoneySmart's custody guidance applies twice over here: self-custodied crypto has no recourse, and a lost passphrase is the terminal version of a lost key.
The mechanics live in the wallet standard. A seed phrase is converted into a master key through a fixed derivation process, and the passphrase is folded into that step as an extra input. The same 12 words with no passphrase produce wallet A; the same words with 'kangaroo' produce wallet B; the same words with 'Kangaroo' produce wallet C. All three are valid wallets, none is derivable from another, and nothing about the chain reveals which one you used.
A hardware wallet prompts for the passphrase when you plug it in, which is how the feature is meant to be used: the phrase lives in your head or in your written backup, and the device derives the wallet on demand. The discipline this demands is a tested restore. Write the seed phrase on paper, write the passphrase on a separate piece of paper or keep it memorised, then perform a full restore onto a fresh device and confirm the addresses match before any meaningful balance goes in. The seed-phrase entry covers the backup ritual this builds on.
For Australian readers, the inheritance implication is the part that gets skipped. An heir who recovers the seed phrase but not the passphrase recovers nothing, and has no way to know a hidden wallet existed - the crypto-inheritance entry covers the planning problem this creates.
The passphrase is the strongest and riskiest feature in self-custody, and the two halves arrive together. ASIC MoneySmart's guidance is blunt that self-custodied crypto has no consumer protections and no recourse if keys are lost; a passphrase splits the recovery information in two and removes the last recovery path. The feature is a bet that you will never mistype one word.
A colleague named Brent (yes, that Brent) added a passphrase to his hardware wallet, typed it with a different capitalisation during a restore a year later, and was met with a valid, empty wallet. No error, no warning - a different wallet is exactly what the maths should produce for a different input. He had skipped the restore test, and the balances were still on the exchange, which is the only reason the story ends there.
The highest-leverage thing most Australians can do is decide deliberately: either use a passphrase with a written, tested, separately stored backup - or skip it entirely and rely on the seed phrase plus offline storage. The cold-wallet entry covers the storage half of that routine. The worst option is half of each.
Take 12 seed words and derive a wallet: it holds addresses you recognise and a balance you funded. Re-derive with the same words plus a passphrase and the result is a different wallet with different addresses and a zero balance. Neither the chain nor the wallet software can tell you which derivation you funded, because both are equally valid. The passphrase is not protection added to a wallet - it is a choice between wallets. Both are recoverable from the same words, which is the test.
Brent set the passphrase 'Harbour2Bridge' and restored a year later as 'harbour2bridge'. The device accepted it silently, derived a valid wallet, and showed a zero balance. Nothing was stolen, nothing was broken, and nothing could be undone - the original wallet exists behind the original input, which he could not reproduce. The restore test he skipped would have caught it in five minutes on day one, with the balance recoverable and the mistake cheap.
An estate plan records the seed phrase in a document and the passphrase in someone's memory. The memory-holder is unreachable and the document-holder recovers an empty wallet with no sign a second one exists. A passphrase used for plausible deniability is invisible to an estate plan unless it is written down somewhere. The crypto-inheritance entry covers the letter-of-wishes structure that solves this - or the decision to skip the passphrase entirely.
Mistake: Confusing the passphrase with an app password or PIN.
Why it bites you: A password guards a login; a passphrase is part of the key derivation. Confusing them means the phrase ends up in a password manager screenshot instead of a tested backup.
Mistake: Storing the passphrase with the seed phrase.
Why it bites you: One page, one fire, one theft - both halves together defeat the design's entire purpose. The deniability exists only while the two are separated.
Mistake: Skipping the restore test.
Why it bites you: A mistyped passphrase derives a valid empty wallet with no error. Brent's capitalisation difference was invisible until the balance was not there.
Mistake: Assuming a wrong passphrase gives an error.
Why it bites you: It does not - any input derives a mathematically valid wallet. The empty balance is the only symptom, and by then the original input is the only cure.
I ran a full restore drill three times on a spare device so you don't have to, and the finding is blunt: the passphrase is the only feature in self-custody where the failure mode is total and silent. Seed phrases fail loudly - a torn paper, a missing word. A passphrase fails quietly, in a way that looks exactly like success.
My position: the plausible-deniability argument is real for balances that justify it, and irrelevant for a wallet holding groceries money. Brent's capitalisation incident is the case I cite, because no thief was involved and no recovery was possible. If you use one, write it with the seed phrase, test the restore twice, and tell whoever inherits the plan. If that list feels like a chore, skip the feature entirely - it is optional for a reason.
No. A password guards access to an app or device, while the passphrase is an input to the key derivation itself. It cannot be reset, recovered, or changed once the wallet is funded.
The wallet behind it is unrecoverable - the same seed words without it derive a different, empty wallet. There is no reset path, which is why a written backup and a tested restore are non-negotiable.
Most major hardware wallets do, prompting for it on connection. The exact behaviour differs by manufacturer, so check the device's documentation before relying on it.
Not from the seed phrase alone - that is the design's purpose. The thief holding 24 words cannot derive a wallet they do not know exists, which is the plausible-deniability layer working as intended.
Only with a written, separately stored passphrase and a tested restore, plus a plan for whoever inherits the holdings. Without that discipline, the lost-keyphrase risk outweighs the deniability benefit.
Disclaimer: This information is general in nature and does not constitute financial or legal advice. Always consult a qualified professional for your specific situation.

Financial Chaos Analyst
Ivy Sinclair-Wren is a Financial Chaos Analyst covering crypto markets, investing behaviour, and the Australian habit of checking prices during family dinners. Based in Melbourne, she reviews AUD Crypto Tracker's coin guides for accuracy, ATO alignment, and ruthless utility — no hype, no predictions, just what the data says.