Advanced reference · not the starting point
Similar-looking backups can follow different rules.
Bitcoin wallets do not all turn words into keys the same way. Record the format and recovery context instead of assuming that “12 words” identifies everything.
Core terms
- Recovery mnemonic
- A human-readable encoding used to recreate secret material. It is not automatically BIP39.
- BIP39 entropy
- The 128–256 source bits encoded with a short checksum into 12–24 words.
- BIP39 seed
- The 512-bit PBKDF2 output derived from the mnemonic and optional passphrase. Its width does not retroactively add entropy to a weak mnemonic source.
- BIP32 root
- The master key and chain code from which an HD wallet derives a tree of keys.
- Derivation and policy data
- The paths, scripts, network, key origins, and thresholds a wallet may need to find the intended funds.
Formats and control structures
BIP39 + BIP32
BIP39 encodes source entropy as words and derives a seed. BIP32 turns seed material into a hierarchical key tree. They solve different steps and do not define every wallet-recovery detail.
Electrum seeds
Electrum uses a versioned seed system of its own. A phrase that resembles BIP39 may follow Electrum’s rules instead, so recovery software and format metadata matter.
Multisig
Multisig requires a threshold of independent keys. It distributes control and device trust; it is not “more entropy.” Preserve the wallet policy, descriptors, key origins, and enough keys.
SLIP39
SLIP39 encodes threshold shares of a master secret. Its shares are not ordinary pieces of a BIP39 phrase and are largely incompatible with BIP39 restoration.
BIP85
BIP85 deterministically derives new entropy from one BIP32 root. It can organize many wallets, while concentrating all derived material under one root backup.
Codex32 / BIP93
Codex32 proposes a checksummed base32 seed format with optional threshold sharing. BIP93 remains draft material and is included as context, not as a default recommendation.