How to find the derivation path for a hardware wallet?

Finding the Derivation Path

1. Hardware wallets rely on standardized derivation paths to generate addresses from a single seed phrase. These paths follow BIP-32, BIP-44, BIP-49, and BIP-84 specifications, each corresponding to different address types and coin protocols.

2. The most common path for Bitcoin legacy addresses is m/44'/0'/0'/0. For Bitcoin P2SH-segwit, it shifts to m/49'/0'/0'/0, while native segwit uses m/84'/0'/0'/0. Each apostrophe denotes a hardened derivation level, critical for security and compatibility.

3. Ethereum does not use hierarchical deterministic (HD) derivation in the same way. Most hardware wallets default to m/44'/60'/0'/0, but some implementations may omit the account index or add custom layers depending on the wallet firmware and blockchain explorer integration.

4. Solana and other non-UTXO chains often bypass BIP-compliant paths entirely. Instead, they derive keys directly from the mnemonic using SLIP-0010 or algorithm-specific logic. Users must consult device-specific documentation rather than assume universal path conventions.

5. Multi-coin wallets like Ledger and Trezor maintain internal mapping tables that assign distinct paths per asset. These mappings are embedded in firmware and exposed through their desktop or web interfaces—never hardcoded into user-facing settings without verification.

Device-Specific Documentation Sources

1. Ledger’s official support site publishes detailed path references per coin under its “Developer Documentation” section. Paths are verified against actual firmware builds and updated with each major release.

2. Trezor Suite displays derivation paths during address export if advanced settings are enabled. The interface reveals whether the wallet is using BIP-44, BIP-49, or BIP-84 based on the selected coin and receive address type.

3. Coldcard devices show derivation paths directly in the “Addresses” menu when browsing extended public keys. Users can toggle between legacy, segwit, and taproot modes to observe path variations.

4. BitBox02 provides path information only via its command-line tool bitbox-cli. The output includes full HD path strings alongside xpubs and address previews for each supported network.

Verification Through Public Key Export

1. Exporting an extended public key (xpub, ypub, zpub) from the device confirms the active derivation scheme. A zpub always indicates BIP-84; a ypub signals BIP-49; an xpub alone does not specify the standard—it could be BIP-44 or older.

2. Tools like Ian Coleman’s BIP39 tool allow manual entry of the mnemonic and selection of known paths to compare generated addresses against those displayed on the hardware wallet screen.

3. Blockchain explorers such as Blockstream Green or Mempool.space accept xpubs and automatically detect associated derivation logic when scanning for transaction history—offering indirect validation of path usage.

4. Electrum and Sparrow Wallet let users manually input derivation paths when importing hardware wallets. If addresses match across both tools and the physical device, the path is confirmed correct.

Firmware and App Version Dependencies

1. Older firmware versions of Ledger Nano S shipped with incomplete BIP-84 support. Upgrading to version 2.1+ was required to enable native segwit path handling without workarounds.

2. Trezor Model T firmware 2.5.0 introduced dynamic path switching based on coin selection in the web interface. Prior versions locked users into fixed BIP-44 unless manually overridden via debug mode.

3. Some third-party apps like Exodus or Coinomi hardcode paths and ignore device-reported standards. This causes mismatches unless users manually configure matching paths inside the app settings.

4. Air-gapped signing tools such as Specter Desktop fetch derivation rules directly from device firmware metadata, ensuring alignment with current implementation rather than relying on external assumptions.

Frequently Asked Questions

Q: Can I change the derivation path after initializing my hardware wallet?A: No. The path is determined at setup time by the firmware and application layer. Changing it would require resetting the device and re-importing the seed with new software expectations.

Q: Why do two different wallets show different addresses for the same mnemonic?A: They likely use divergent derivation paths or interpret BIP standards differently—especially around account index handling or hardened vs. non-hardened levels.

Q: Is m/44'/0'/0'/0 the same across all Bitcoin wallets?A: Not universally. Some wallets increment the account index beyond zero by default, while others treat the third field as purpose rather than account—leading to address divergence even with identical mnemonics.

Q: Do testnet coins use separate derivation paths?A: Yes. Testnet Bitcoin typically uses m/44'/1'/0'/0, where the coin type changes from 0 to 1. Other testnets follow similar logic but vary by implementation.