Step-by-step

  1. Find which ecosystem you care about. EVM vs Solana vs Bitcoin vs TRON vs XRP use different curves or coin types. Matching the wrong path looks like a zero balance.
  2. Read the path for account 0 in the widget. Index 0 is the first Receive address. “Add account” increments the index in the path (Solana hardens that index).
  3. Compare Receive in GaurdWallet with the old wallet. If they match, the path is the one that wallet used. If not, you may have imported a private key elsewhere — that key is not in the mnemonic.
HD derivation path (account 0)

Paths GaurdWallet actually derives. Solana is SLIP-0010 ed25519 (Phantom-compatible); Bitcoin is BIP-84 native SegWit, not BIP-44 legacy.

Paths we actually derive

From packages/core DERIVATION_PATHS:

EVM        m/44'/60'/0'/0/{index}     BIP-44, MetaMask-compatible
Bitcoin    m/84'/0'/0'/0/{index}      BIP-84 P2WPKH bc1…
Litecoin   m/84'/2'/0'/0/{index}      BIP-84 ltc1…
Solana     m/44'/501'/{index}'/0'     SLIP-0010 ed25519, Phantom-compatible
TRON       m/44'/195'/0'/0/{index}    BIP-44, TronLink-compatible
XRP        m/44'/144'/0'/0/{index}    BIP-44 secp256k1, classic r-address
Info

Dogecoin, Dash and Bitcoin Cash adapters exist in code (BIP-44 coin types 3, 5, 145) but are hidden in the UI until indexers can be proxied. Do not expect those addresses in Receive today.

What paths cannot do

They cannot move funds. They cannot reconstruct a MetaMask account that was imported from a raw private key. They cannot add a BIP-39 passphrase if you never typed one — GaurdWallet Import has no passphrase field, so passphrase wallets look empty.

Old wallet behaviorGaurdWallet result
Standard MetaMask account 0Same 0x
Phantom Solana account 0Same base58
Bitcoin legacy 1… from another pathNot derived — Receive is bc1
Hardware account not on the seedNot imported
Warning

Websites that ask for a seed to “show all derivation paths” are phish. Path math belongs in wallet software you launched on purpose.

FAQ

Is Bitcoin BIP-44 in GaurdWallet? No. Bitcoin is BIP-84 native SegWit. BIP-44 BTC would be a different 1… account. We document that gap instead of silently deriving both.

Why is Solana’s index in a different path slot? SLIP-0010 / Phantom convention: m/44'/501'/{account}'/0'. EVM puts the address index at the last component.

Can I type a custom path? Not in the current UI. You get the standard paths above. Custom paths would break portability claims.