A mnemonic phrase encodes wallet entropy in words so compatible software can derive a seed and recreate deterministic private keys.
A mnemonic phrase is an ordered sequence of words that encodes wallet-generation data in a human-readable form. In a BIP-39 wallet, the words encode entropy plus a checksum and are then processed, with an optional passphrase, into a seed used by deterministic key-derivation software.
The phrase is not a password that a provider can reset. In many self-custody systems, anyone who obtains the correct phrase and any required passphrase can recreate the wallet’s spending keys. It should never be shared with support personnel, entered into an unsolicited website, photographed for convenience, or published as an example.
For BIP-39, entropy length (ENT) is 128 to 256 bits in steps of 32. The checksum length is:
The mnemonic word count is:
| Words | Entropy | Checksum | Encoded bits |
|---|---|---|---|
| 12 | 128 bits | 4 bits | 132 bits |
| 15 | 160 bits | 5 bits | 165 bits |
| 18 | 192 bits | 6 bits | 198 bits |
| 21 | 224 bits | 7 bits | 231 bits |
| 24 | 256 bits | 8 bits | 264 bits |
A 12-word BIP-39 mnemonic therefore does not contain 384 bits of entropy. It represents 128 bits of generated entropy plus a 4-bit checksum.
flowchart LR
A["Generated entropy"] --> B["Checksum appended"]
B --> C["Bits mapped to ordered words"]
C --> D["Mnemonic plus optional passphrase"]
D --> E["Seed derivation"]
E --> F["Hierarchical root and child keys"]
F --> G["Addresses and signing authority"]
BIP-39 covers mnemonic generation and conversion to a seed. BIP-32 or another deterministic-wallet scheme can then derive a hierarchy of keypairs. Address formats and derivation paths are separate layers, which is why importing the same phrase into different software can show different accounts or addresses.
| Term | Role | Can it authorize spending? |
|---|---|---|
| Mnemonic phrase | Human-readable input encoding entropy and checksum | It can recreate derived spending keys in compatible software |
| BIP-39 seed | Binary output derived from mnemonic and optional passphrase | Used to generate the deterministic key hierarchy |
| Private key | Secret value used to create valid transaction signatures | Yes, for the associated key and spending conditions |
| Public key or address | Public identifier or derived destination information | No, not by itself |
| Optional passphrase | Additional input used during seed derivation | Required to recreate the intended seed when one was used |
| Wallet password or PIN | Local control for an app or device | Usually protects local access but does not replace the recovery secret |
Changing an app password does not change a previously exposed mnemonic. Conversely, knowing a wallet password may not be enough to recover the wallet after the device is lost.
A self-custody wallet device is destroyed, but the owner retained the wallet’s recovery information. On a compatible replacement, the correct phrase and passphrase recreate the deterministic key hierarchy.
The restored software initially shows no balance because it is using a different account path. After the correct wallet type and derivation settings are selected, it discovers the expected addresses and transaction history.
No assets moved during recovery. The software regenerated authorization keys and scanned the public ledger for records associated with them. This is why recovery requires both secret integrity and technical compatibility.
If the owner had entered a different optional passphrase, BIP-39 would derive a different seed rather than report a simple typo. The resulting wallet could be valid but unrelated to the intended holdings.
Backup design should follow the wallet provider’s verified documentation and the user’s custody, legal, and operational needs. A recovery phrase should not be sent to anyone claiming they need it to validate, unlock, upgrade, or investigate a wallet.
This article provides general financial and technical education, not individualized custody, cybersecurity, legal, inheritance, or investment advice.