# Importing a Wallet: Derivation Paths and Empty Balances

URL: https://www.xineee.net/derivation-paths-empty-wallet/
Published: 2026-10-27T21:21:30+00:00 | Updated: 2026-10-27T21:21:30+00:00
Verified: 2026-10-27

## Quick answer
An empty restore usually means the wallet read a different branch of the same key tree. Check the address prefix, try the common paths, then verify on-chain.

## Summary
A correct seed phrase can open an empty wallet when the derivation path differs. Try the common path values, account indices and address gaps before assuming the funds are lost.

## FAQ
Q: Can a wrong derivation path ever send funds to a stranger?
A: No. A different path produces addresses that belong to you, derived from your seed. Nothing is transferred anywhere by restoring; the wallet is only choosing what to display.
Q: How do I know which path my old wallet used?
A: Start from the address format. If you still have one receiving address, its prefix identifies the purpose value with high confidence. Wallet documentation and the original export file, if you kept one, usually name the path outright.
Q: Why does the same seed show different addresses in two wallets?
A: Because they default to different branches. Both are deriving correctly from your seed; they simply disagree about which account to open first. Set the path explicitly and they will agree.
Q: Is it safe to enter a seed into a recovery tool?
A: Only into software you trust, ideally on an offline machine, and never into a website that advertises a balance checker. A page that asks for words to show you a balance is asking for your keys.
Q: What is the twenty-address gap limit?
A: It is the convention that a wallet scans twenty consecutive unused addresses before deciding an account has no more activity. It exists to keep restores fast. Funds beyond that window on a rarely used account can be missed by a shallow scan.
Q: Could the funds have moved without me?
A: Yes, so check the address on a block explorer rather than trusting a wallet's display. If the on-chain history shows an outgoing transfer you did not authorise, the problem is no longer derivation and you should treat the seed as compromised.