Multi-chain wallets explained: one set of words, a key for every village
A multi-chain wallet uses one recovery phrase to make separate keys and addresses for many blockchains. That's convenient. It also means the same-looking address can exist on several networks, and the network you pick decides where your coins land.
There isn't just one village. Over the hill there's another, with its own notebook, its own rules and its own handwriting. And another beyond that. Each village keeps its own book, and none of them can read the others' pages.
Anna has coins in three of them. She doesn't want three sets of secret words. So her wallet does something clever: from one set of twelve words, it cuts a different key for every village, on the same ring.
That's a multi-chain wallet. One backup, many notebooks. The catch is that some villages use the same shape of door, and a payment posted to the wrong one doesn't come back by itself.
What it is
A multi-chain wallet is a wallet that holds keys for several blockchains, such as Bitcoin, Ethereum and others, all made from a single recovery phrase. You back up the words once. The wallet works out every key from them on demand, using shared standards, so other wallets that follow the same standards can rebuild the same keys.
How it works: one phrase, two addresses
Three standards do the work. BIP 39 turns your words into a long number, the seed (BIP 39). BIP 32, written by Pieter Wuille in 2012, grows a whole tree of keys from that seed, a design meant to be "interchanged between different clients" (BIP 32). BIP 44 gives the tree a fixed shape, with a separate branch for each coin (BIP 44).
Each coin's branch has a registered number. In the SatoshiLabs list, Bitcoin is 0, Ethereum is 60 and Solana is 501 (SLIP-0044).
Take the public test phrase that developers use, "abandon" eleven times and then "about". Never put money on it: everyone knows these words.
- Bitcoin branch. The path m/84'/0'/0'/0/0 (the 0 after 84 is Bitcoin) gives the address bc1qcr8te4kr609gcawutmrza0j4xv80jy8z306fyu. That's the official test vector in BIP 84 (BIP 84).
- Ethereum branch. The path m/44'/60'/0'/0/0 gives 0x9858EfFD232B4033E47d90003D41EC34EcaEda94. We derived it ourselves with an open-source BIP 32 library on 18 November 2026, using the same library that reproduces the BIP 84 test vector above.
- Same words, unrelated addresses. Nobody can tell from the outside that the two belong together. Different branch, different key, different notebook.
Now the twist. On Ethereum and on the many networks that copied its design, often called EVM networks, one key gives the same address everywhere. MetaMask's help pages say it plainly: your phrase "generates the same address across all EVM-compatible networks" (MetaMask). Since EIP-155 in 2016, each signed transaction carries a chain ID, so a payment signed for one of these networks can't be replayed on another (EIP-155). Same address, separate notebooks.
Why it matters
One backup for many chains is a real gain. Fewer pieces of paper, fewer chances to lose one.
But the same address on many networks means a sender must choose the network, and a wrong choice is easy to make. MetaMask's guidance sorts the outcomes. Sent to your own address on the wrong EVM network? "The tokens are not lost": switch the wallet to that network and they're there. Sent to a non-EVM network? "It's likely your tokens are gone forever." Sent to a contract address? "There is no guarantee of recovery."
Exchanges add one more layer. A deposit address is shown for a named network. Send on another and you depend on the exchange's support team, if it can help at all.
Where people get it wrong
- "My wallet is multi-chain, so I can send anything anywhere." The wallet holds many keys. Each payment still lives in one notebook only.
- "Same address, same account." On EVM networks the address matches, but the balances are separate. Ten coins on one network are zero on the next.
- "One phrase restores everything in any app." Only if the other app uses the same standards and paths. Our article on derivation paths explains why coins sometimes seem to vanish after a restore.
- "The network field is a detail." It's the most important field after the amount.
Read the gate, not just the address
Before every payment, read three things in this order: the network, the address, the amount. If the receiver gave you an address without naming the network, ask. If the network dropdown has a name you don't recognise, stop.
And send a small amount first. A multi-chain wallet gives you a key for every village. It doesn't tell you which village you're standing in.
Frequently asked questions
What is a multi-chain wallet?
A wallet that holds keys for several blockchains, created from a single recovery phrase. It follows standards such as BIP 32, BIP 39 and BIP 44, so one backup can rebuild the keys for every chain it supports.
Why is my address the same on Ethereum and other networks?
Ethereum and networks built on the same design, called EVM networks, turn one key into the same address. The balances are still separate, because each network keeps its own ledger.
What happens if I send tokens on the wrong network?
If you sent to your own address on another EVM network, switching the wallet to that network usually shows the tokens. Sending to a non-EVM network or to a contract address can mean the tokens can't be recovered. If an exchange address was involved, ask the exchange.
Is one recovery phrase for all my coins a risk?
It's a single point of failure: whoever gets the words gets every chain at once. It also means one good backup protects everything. The answer is careful storage of that one phrase.
Can I restore a multi-chain wallet in another app?
Often, if the other app follows the same standards and derivation paths. Check which chains and paths it supports before you rely on it, and test with a small amount.
Sources
- BIP 32, Hierarchical deterministic wallets (Pieter Wuille)
- BIP 39, Mnemonic code for generating deterministic keys
- BIP 44, Multi-account hierarchy for deterministic wallets
- BIP 84, Derivation scheme for P2WPKH based accounts (test vectors)
- SLIP-0044, Registered coin types for BIP-0044 (SatoshiLabs)
- EIP-155, Simple replay attack protection (Vitalik Buterin, 2016)
- MetaMask Help Center, Funds sent on the wrong network

