How to find your "Derivation Path" on Ledger? (Technical Settings)

Understanding Derivation Paths in Ledger Devices

1. A derivation path is a hierarchical string used to generate multiple cryptocurrency addresses from a single seed phrase. It follows the BIP-32, BIP-44, BIP-49, or BIP-84 standards depending on the coin and wallet configuration.

2. Ledger devices store private keys using deterministic key derivation. Each app installed—such as Bitcoin, Ethereum, or Solana—uses its own default path defined by the Ledger Live application and firmware logic.

3. The path format typically appears as m/44'/60'/0'/0/0 for Ethereum (BIP-44), while Bitcoin legacy uses m/44'/0'/0'/0/0 and Bitcoin SegWit (P2SH) uses m/49'/0'/0'/0/0.

4. These paths are not user-configurable within Ledger Live’s GUI but are hardcoded per app and can be inspected via developer tools or SDK integrations.

5. Misalignment between the expected derivation path and the one used by an external wallet or dApp will result in address mismatches and failed transaction signing.

Accessing Derivation Path via Ledger Live Desktop

1. Open Ledger Live and ensure your device is connected and unlocked with the correct PIN.

2. Navigate to the Accounts tab and select the specific cryptocurrency account you want to inspect.

3. Click the three-dot menu next to the account name and choose View address or Advanced settings, depending on the version.

4. In newer versions of Ledger Live, the full derivation path is displayed under Technical details when viewing the receive address or during account setup confirmation.

5. For Ethereum-based tokens, the path shown is usually m/44'/60'/0'/0, indicating the account-level base before index enumeration.

Using Ledger Developer Tools and CLI

1. Install the @ledgerhq/hw-app-eth or @ledgerhq/hw-app-btc package via npm if building custom integrations.

2. Use the getAddress method with explicit path parameters to retrieve public keys at known indices like m/44'/60'/0'/0/0.

3. Run ledgerctl or ledger-live CLI commands with --debug flag to log low-level APDU exchanges including path information.

4. When interacting with the device through WebUSB in browser environments, the derivation path is passed as a 5-element uint32 array corresponding to each depth level.

5. Developers must match these values precisely—any deviation triggers a security error or returns an incorrect address.

Derivation Path Variants Across Chains

1. Bitcoin Legacy (P2PKH): m/44'/0'/0'/0/0

2. Bitcoin SegWit (P2SH): m/49'/0'/0'/0/0

3. Bitcoin Native SegWit (Bech32): m/84'/0'/0'/0/0

4. Ethereum: m/44'/60'/0'/0/0

5. Solana: Uses m/44'/501'/0'/0' with Ed25519 key derivation instead of BIP-32 hardened notation.

Frequently Asked Questions

Q1. Can I change the derivation path used by Ledger Live?No. Ledger Live enforces standardized paths per coin type and does not allow manual override. Custom paths require third-party tools like MyEtherWallet or MetaMask with Ledger support enabled.

Q2. Why do some dApps show different addresses than Ledger Live?This occurs when the dApp assumes a non-standard path—for example, using m/44'/60'/0'/0 instead of m/44'/60'/0'/0/0. Always verify the path documented by the dApp provider.

Q3. Does Ledger support BIP-122 for Bitcoin Cash?Yes. Bitcoin Cash uses m/44'/145'/0'/0/0, which is supported in Ledger Live since firmware version 1.10.0 and later.

Q4. How do I verify the derivation path used by a hardware wallet recovery?Use the same seed phrase in a compatible software wallet like Electrum or MyCrypto, manually inputting the exact path. Compare resulting addresses with those shown on Ledger Live or device screen.