No, a seed phrase and a private key are not the same thing. A seed phrase, usually 12 or 24 words, is the backup that rebuilds a whole wallet: the wallet derives its accounts' private keys from it. A private key is the signing secret for one account, 64 hex characters on Ethereum. Three caveats: accounts imported with a private key sit outside the phrase, an optional passphrase turns the same words into a different wallet, and a leaked key plus an extended public key can reach a whole account.
- Are they the same? No. One phrase, many keys.
- Can you get a private key from a seed phrase? Yes, by restoring the phrase in a compatible wallet and exporting that account's key.
- Can you get a seed phrase from a private key? No. A private key does not reveal the seed or the words.
Seed phrase, private key and the other wallet secrets, side by side
| Item | What it is | What holding it lets someone do |
|---|---|---|
| Seed phrase (Secret Recovery Phrase) | 12 or 24 words (BIP-39 also allows 15, 18 or 21) that encode the wallet's starting randomness | Recreate every account the wallet derived from it |
| Private key | The signing secret for one account; 64 hex characters on Ethereum | Control the assets in that one account |
| Public address | Where payments are sent; on Ethereum, 42 characters starting with 0x, derived from the public key | Pay you |
| Extended public key (xpub) | The master public key of one account | Generate every address in that account and track its transactions |
| Wallet password or PIN | A lock on the app on one device | Open that copy of the wallet; MetaMask says the password "does not recover your wallet" |
| Passphrase (optional) | Extra text mixed in when the seed is made | Together with the words, open a different wallet |
Only the first two rows give control of funds on their own. Ledger's explainer draws the line in a short passage: someone with a single private key "will only be able to move assets in that specific account", while "anyone with your seed phrase has instant access to every private key". Phantom's help center says the same from the other side: the recovery phrase "can regenerate every account and address in your wallet, while a private key is limited to one address."
How 12 words become keys, and why it only works one way
BIP-39, the standard Phantom names for its 12-word phrase and Trezor for its 12- and 24-word backups, starts with randomness, not words. The wallet generates 128 to 256 random bits, adds a short checksum taken from their SHA256 hash, and cuts the result into 11-bit pieces. Each piece is a number from 0 to 2,047 that picks one word from a list of 2,048. The standard is meant to carry computer-generated randomness, not sentences people make up.
Next, the words are stretched into a 512-bit seed. BIP-39 runs them through a function called PBKDF2 2,048 times and mixes in any passphrase. BIP-32 then grows that seed into a tree of keys.
A path picks one branch of the tree. In 44'/60'/0'/0/0, the Ethereum example in Ledger's developer blog, 44 is the BIP-44 purpose, 60 is Ether's coin type in the SLIP-44 registry (Bitcoin's is 0), and the last three numbers are the account, the change branch and the address index. On Ethereum, the private key at the end of that path produces a public key, and the address is the last 20 bytes of that key's Keccak-256 hash with 0x in front: 42 characters.
The tree only works downward. BIP-32 says that given a child key, "an attacker cannot find the parent private key" short of brute force, and the seed sits above every key in the tree. To get a private key from a seed phrase, restore the phrase in a compatible wallet and export the account's key; in MetaMask that is the account's three-dot menu, then Account details, then Private key, after you enter your MetaMask password. MetaMask says the exported key can import and export "that account, and that account only, into another wallet". Going the other way is not possible: a private key does not reveal the seed, and the one BIP-32 exception, covered below, still stops at the account.
Because the checksum is appended to the end of the random bits, it lands in the last word. It is one bit for every 32 bits of randomness, so most random combinations of list words fail it:
| Words | Random bits | Checksum bits | Share of random word sequences that pass the checksum |
|---|---|---|---|
| 12 | 128 | 4 | one in 16 |
| 15 | 160 | 5 | one in 32 |
| 18 | 192 | 6 | one in 64 |
| 21 | 224 | 7 | one in 128 |
| 24 | 256 | 8 | one in 256 |
BIP-39 tells software to "issue a warning if it is invalid", so most mistyped words are caught. Not all of them: on a 12-word phrase, about one random combination in 16 passes, so an accepted phrase can still be the wrong one. The word list also helps when you copy words by hand. It was chosen so that "it's enough to type the first four letters to unambiguously identify the word".
Same words, different accounts: the derivation path
Restoring a phrase in a second app does not promise the same accounts, because the path is a choice each wallet makes on top of the standard. MetaMask's help center says that when you import a phrase, it "only supports the default BIP-44 derivation path (m/44'/60'/0'/0)". Ledger's paths appear in MetaMask only when a Ledger device is connected, as a choice between Legacy (MEW/MyCrypto), Ledger Live and BIP44, and MetaMask's Trezor integration supports only BIP44. MetaMask's restore guide adds that only accounts "originally created from the same SRP" come back automatically; accounts imported via private keys, JSON files or connected hardware wallets "must be manually re-added".
BIP-44 itself tells software to "discover all used accounts after importing the seed". Bitcoin adds its own layer: Ledger's blog lists purpose 44 for legacy accounts, 49 for SegWit, 84 for native SegWit and 86 for Taproot, all under one phrase. If a restored wallet looks empty, the path, the network and a forgotten passphrase are worth checking before you decide the words are wrong. On Ethereum, each derived account also keeps its own transaction counter, the nonce; our explainer on pending transactions and the nonce queue covers what that means when a transfer stalls.
What four wallet makers say the words do not bring back
"The phrase covers everything" is only true for accounts the wallet derived from that phrase. Each maker's help pages draw the edges a little differently.
| Wallet | Phrase | Not restored by the words alone |
|---|---|---|
| MetaMask | 12 words | Accounts imported with a private key or JSON file, and connected hardware wallets |
| Phantom | 12 words (BIP-39) | Accounts imported with a private key |
| Ledger | 24 words | Accounts opened under a passphrase, unless you also have the passphrase |
| Trezor | 12 or 24 words (BIP-39) or 20 words (SLIP-39), depending on model | Passphrase wallets, unless you also have the passphrase |
The makers' own wording is direct. MetaMask says imported accounts are "NOT INCLUDED under the Secret Recovery Phrase", and that the password "unlocks local access only". Phantom tells users: "If you imported additional private keys, back up each one separately." Ledger stores private keys "offline in a Secure Element chip", and its passphrase "creates an entirely different set of accounts". Trezor's multi-share backups can have up to 16 shares, for example any 3 of 5.
Imported keys and passphrases are the two places a words-only backup falls short. MetaMask and Phantom both say the phrase does not carry imported accounts, so a backup plan built only around the words leaves them out. A passphrase is a second secret that changes which wallet the same words open, and Trezor's support page explains why a typo is so confusing: "Every string of characters opens some wallet, so Trezor Suite cannot tell you which character is wrong." You see "an empty wallet because that passphrase has no funds", while "the wallet holding your funds is untouched".
When one private key can expose a whole account
"One key, one account" is true for a key on its own. BIP-32 lists a weakness that "may not be immediately obvious": knowing a parent extended public key "plus any non-hardened private key descending from it is equivalent to knowing the parent extended private key (and thus every private and public key descending from it)." In BIP-44 terms, change and address index are the non-hardened levels; the apostrophe in a path marks the hardened ones. Put the rule and the layout together: a private key for one address, plus the xpub of the account it sits in and the address's position in that account, lets someone compute the account's extended private key, and with it every private key and address in that account. It does not reach other accounts or the seed, because hardened derivation sits at the account level so that "a leak of account-specific (or below) private keys never risks compromising the master or other accounts."
That is why BIP-32 says extended public keys "must be treated more carefully than regular public keys". Ledger's support page treats the xpub as a privacy matter first: "With your xpub, anyone can track all past and future transactions of the account." Ledger Wallet uses each account's xpub to generate its addresses and add up their balances, and lets you copy it from the account's settings (the Advanced tab on desktop, Advanced logs on mobile). Wherever a wallet lets you copy an xpub, the practical rule is to never share it alongside an exported key from the same account. On Bitcoin, where one account spreads across many addresses numbered from index 0, our piece on why small deposits can make a payment expensive picks up the spending side.
One phrase, several wallets: the 2022 Slope leak
The reach of a single phrase showed up on Solana in 2022. The Solana Foundation's incident update, dated August 8, 2022, says that from 22:37 UTC on August 2 and for about four hours, attackers "drained 9,231 wallets of approximately $4.1 million worth of assets". According to the update, "private key material from these Slope users was inadvertently transmitted by the Slope app to an application monitoring service", though exactly how the attacker obtained it was still under investigation. The Foundation did not believe the problem was tied to any wallet implementation "other than Slope’s", and it warned that "all a user had to do to become vulnerable was import their seed phrase into the Slope app".
The damage did not stay inside Slope. Affected users on other software wallets "such as Phantom and Solflare" may have been hit because of "reuse of seed phrases generated or stored within Slope", and any impact on Ethereum wallets was likely due to the same reuse, since both Ethereum and Solana use BIP-39 phrases. Hardware wallets, used with or without Slope, were not impacted. That is the seed phrase versus private key difference in one incident: a phrase handled by one app put other software wallets that reused it at risk. A wallet password, which MetaMask describes as unlocking "local access only", would not have protected a phrase that was already exposed.
What to do depends on which secret leaked
| What may have leaked | What is exposed | Common security response |
|---|---|---|
| Seed phrase | Every account derived from it, in every app and on every network where it was used | Create a new wallet with a new phrase on a trusted device and move funds out of each derived account |
| One private key | The assets in that account, and the whole account if its xpub is also out | Move that account's funds to an address the leaked key does not control |
| Extended public key | The account's transaction history, past and future | Stop sharing it; Ledger suggests moving coins to a new account with a new xpub for future privacy |
| Wallet password or PIN | The app on that device | Change it, and treat the phrase as exposed if the device itself may be in someone else's hands |
For a backup plan, treat the written phrase as the wallet itself and keep it off the internet; MetaMask's case for handwriting it is that it "cannot be stolen online". Export private keys only when an app genuinely needs one, since each export is another copy of a secret the phrase already covers. If you hold imported accounts, either back up each key separately, as Phantom advises, or move those funds into an account derived from the phrase so that one backup covers them. Add a passphrase only if you will store it as carefully as the words. Signing requests are a separate risk that no backup choice fixes; our guide to token approvals and how to revoke them covers that side.
Sources
- Bitcoin Improvement Proposals · BIP-39: Mnemonic code for generating deterministic keys — Entropy, checksum and word-count table, 2,048-word list, PBKDF2 conversion to a 512-bit seed, passphrase behaviour
- Bitcoin Improvement Proposals · BIP-32: Hierarchical Deterministic Wallets — Child keys do not reveal the parent; the extended public key plus non-hardened private key weakness; hardened account level
- Bitcoin Improvement Proposals · BIP-44: Multi-Account Hierarchy for Deterministic Wallets — Path levels, hardened and public derivation by level, account discovery after import
- Bitcoin Improvement Proposals · BIP-84: Derivation scheme for P2WPKH based accounts — The zpub prefix for extended public keys
- SatoshiLabs · SLIP-0044: Registered coin types for BIP-0044 — Coin type 0 for Bitcoin and 60 for Ether
- ethereum.org · Ethereum accounts — Private key of 64 hex characters, 42-character address from the Keccak-256 hash, nonce
- MetaMask Help Center · How to secure your Secret Recovery Phrase and password — 12-word SRP, password unlocks one device only, one private key per account, handwriting the phrase
- MetaMask Help Center · How to export an account's private key — Menu path to reveal one account's private key
- MetaMask Help Center · How to import a seed phrase from another wallet — Only the default BIP-44 path when importing a phrase; Ledger and Trezor path options
- MetaMask Help Center · How can I reset my password? — Imported accounts are not included under the Secret Recovery Phrase
- MetaMask Help Center · How to add missing accounts after restoring with a Secret Recovery Phrase — Which accounts come back automatically after a restore
- Phantom Help Center · Difference between a Secret Recovery Phrase and a private key — 12-word BIP-39 phrase, phrase regenerates every account, imported accounts not covered
- Phantom Help Center · View your recovery phrase or private keys — Back up each imported private key separately
- Ledger Support · 24-word Secret Recovery Phrase — Ledger's 24-word phrase
- Ledger Academy · An offline key is the only key — Private keys stored offline in a Secure Element chip
- Ledger Academy · Passphrase: an advanced security feature — A passphrase creates a different set of accounts
- Ledger Academy · Private keys vs seed phrase — One private key moves one account; the seed phrase reaches every private key
- Ledger · Understanding crypto addresses and derivation paths in Ledger Live — Example path 44'/60'/0'/0/0 and Bitcoin purposes 44, 49, 84 and 86
- Ledger Support · Extended public key (xPub) — The xpub as an account's master public key, privacy, moving to a new account
- Trezor · Understanding Trezor wallet backups: 12, 20 or 24 words — BIP-39 and SLIP-39 backups by model, multi-share limits
- Trezor Support · Fix passphrase wallet problems in Trezor Suite — Every passphrase opens a wallet; a typo shows an empty wallet
- Solana Foundation · 8/2/2022 Slope Wallet Incident Update — The August 2022 drain of 9,231 wallets and seed phrase reuse across wallets
Editorial note
This article was prepared with the help of AI tools and checked against the sources listed above on 2026-11-04. Worked examples are illustrative unless a source is cited. Read our editorial standards, or tell us if you spot an error.