Updated · Technical content and source links reviewed.
BIP32 derives a tree of wallet keys, BIP38 encrypts an individual private key, and BIP39 turns mnemonic words into a seed. These standards solve different problems and are not interchangeable backup formats.
BIP32: hierarchical deterministic keys
BIP32 describes deriving child keys from a master key and chain code. It does not require a human-readable word phrase. A derivation path identifies a branch of that tree, so restoring a seed with the wrong path can produce different addresses.
An extended public key can derive supported public child keys and expose address history, but cannot normally sign transactions. It should still be treated as privacy-sensitive. An extended private key can expose many descendant keys and must remain secret.
BIP38: encrypted private keys
BIP38 specifies a passphrase-protected private-key record, often encountered with paper wallets. Recovery needs the encrypted record and its passphrase, or a usable alternate copy of the original key. It is not a seed phrase and should not be pasted into a mnemonic recovery field.
BIP39: mnemonic phrases and an optional passphrase
BIP39 defines mnemonic lengths of 12, 15, 18, 21 or 24 words, drawn from a 2,048-word list. A checksum helps detect some transcription errors. The words and an optional passphrase are processed to derive a binary seed.
The passphrase is not restricted to one dictionary word. A different passphrase produces a different wallet without necessarily displaying an error. A valid checksum confirms format consistency, not that you have restored your intended accounts.
Why “BIP39 compatible” is not the whole story
The same phrase can still show different accounts when software uses different derivation paths, account indexes, networks or script types. Imported private keys may not be covered by the phrase at all. Match known addresses and the original wallet’s documentation.
Electrum generates its own native seed format, described in its seed-version documentation. SLIP39 shares use another backup scheme and should not be treated as ordinary BIP39 words. Identify the standard before choosing recovery software.
Which information should you preserve?
- The wallet name, version and approximate creation date.
- The original backup format and any separate imported-key backups.
- Whether an additional passphrase was used.
- Known public addresses, networks and account configuration.
Keep secret material offline. Do not test real recovery words or encrypted private keys on an unfamiliar website. For incomplete phrases, see our seed phrase recovery guide.
Request a recovery assessment
Start with your wallet type, backup filenames and a description of the problem. Do not send passwords, seed phrases or private keys in your first message. Contact Wallet Recovery Service. Our fee is 20% of funds recovered; no recovery, no fee.