You import your recovery phrase into a new wallet app, expecting to see the same balance you had before, and instead you land on an empty account with a completely different address. No error message, nothing obviously wrong, just a wallet that looks like it belongs to someone else.
This is one of the more disorienting moments in self-custody, and it is more common than it should be. The good news is that your funds are almost never actually gone. What changed is the derivation path, the formula a wallet uses to turn one recovery phrase into a specific set of addresses.
One phrase, an entire tree of addresses
A recovery phrase does not encode a single private key. It encodes a seed, a large number that a wallet feeds into a standard formula to generate a whole tree of possible accounts, each with its own address and private key.
This is defined by two related standards. BIP-32 describes how to build that tree in a deterministic way, so the same seed always produces the same tree. BIP-44 describes a specific path through the tree that most wallets agree to follow, written in a format like this:
m / purpose' / coin_type' / account' / change / address_index
For Ethereum and Ethereum-compatible networks, including Base, the standard path is m/44'/60'/0'/0/0. The 44 marks it as a BIP-44 path, 60 is the coin type reserved for Ethereum, and the remaining numbers select which account and which address within that account to generate. Change the address index from 0 to 1 and you get a completely different, equally valid address from the exact same phrase.
This is also why one recovery phrase can back multiple accounts in the same wallet. Each "add account" button you have ever clicked was really just moving to the next address index along the same path.
Why two wallets can disagree
Almost every mainstream wallet, including MetaMask and Simple Base Swap, defaults to m/44'/60'/0'/0/0 for the first Ethereum-style address. Since Base uses the same address format as Ethereum, that shared standard is exactly why a phrase created in one app opens the same address in another. This portability is one of the real advantages of self-custody: you are not locked into any single product.
The friction shows up with a specific group of wallets, mainly some hardware wallet interfaces, that historically used a different path by default. Ledger Live is the best known example. Its default "Ledger Live" path increments the account number for each new address instead of the address index, which produces a different address than the standard path at the same position in the tree. Ledger also supports switching to the standard BIP-44 path, and doing so will surface the addresses you would see in MetaMask or similar wallets, but the two options are not the same tree position, so they do not show the same addresses by default.
A few older or less common wallets have made similar non-standard choices for their own historical reasons. None of this means a phrase is broken. It means two apps chose different coordinates on the same map.
What to do if this happens to you
Do not panic and do not generate a new phrase. Nothing about the funds has moved.
- Check the wallet's derivation path setting. Many wallets, especially hardware wallet apps, let you choose between a "Legacy," "Ledger Live," or "BIP-44 standard" path when importing. Switching to the standard path is usually what resolves the mismatch.
- Check the account and address index. If you had created a second or third account in your old wallet, importing the phrase somewhere new usually starts you back at address index 0. Look for an "add account" option and step forward until the address you recognize appears.
- Confirm you copied the phrase exactly. A single mismatched or misordered word produces a valid-looking but entirely different seed, and therefore a different address at every path. Recount the words and check the order against your backup.
- Never enter your phrase into a website or support agent to "fix" this. Recovering the correct address only ever requires changing a setting inside a wallet app you installed yourself. Any site or person asking you to type your phrase in to help you find your funds is a scam, covered in more detail in avoiding wallet phishing and drainer scams.
If you land on the wrong address, the funds have not disappeared. They are still sitting at the original address, on the original path, waiting for a wallet configured to look in the right place.
Why this matters even if you never see it
Most people who only ever use one wallet app never encounter this. The reason it is worth understanding anyway is that self-custody's biggest promise, that your recovery phrase works everywhere, comes with a small asterisk: everywhere, as long as the app agrees on where to look.
Before you rely on a phrase across multiple apps, it is worth doing a small test. Send a trivial, throwaway amount to the address shown in the new app first, confirm it matches what you expect, and only then treat it as your main wallet. That habit costs nothing and removes any doubt about whether two apps are actually pointing at the same account.
Base was built to make self-custody simpler, not to add another thing to memorize. Understanding derivation paths is not about needing to manage them day to day, it is about recognizing, the one time it comes up, that a different address is a settings mismatch and not a lost wallet.
Sources: imToken Help Center, What is a Derivation Path, Ledger, Understanding Crypto Addresses and Derivation Paths, MetaMask Help Center, How to import a seed phrase from another wallet