Understanding Wallet Derivation Paths (What are m/44'/60'/0'/0/0?)

What Is a Derivation Path?

1. A derivation path is a sequence of numbers and symbols that defines how cryptographic keys are generated from a master seed in hierarchical deterministic (HD) wallets.

2. It acts as a roadmap instructing the wallet software where to locate a specific private key within the tree-like structure of derived keys.
3. Each segment in the path corresponds to a level in the hierarchy—starting from the root seed and descending through purpose, coin type, account, change, and address indices.
4. The apostrophe (') after a number indicates that hardened derivation is used, meaning the child key cannot be computed from the parent public key alone.
5. This design prevents exposure of higher-level keys even if a lower-level public key is compromised.

The BIP-44 Standard Explained

1. BIP-44 introduced a universal framework for organizing cryptocurrency accounts across multiple coins and tokens within a single HD wallet.

2. Its structure follows m/purpose'/coin_type'/account'/change/address, where m denotes the master node.
3. Purpose is set to 44' to signal compliance with BIP-44, distinguishing it from other standards like BIP-49 (for P2SH-segwit) or BIP-84 (for native segwit).
4. Coin type 60' specifically identifies Ethereum, following SLIP-0044’s registered value for ETH and ERC-20 tokens.
5. Account 0' refers to the first user-defined account, allowing separation of funds for different use cases without altering the seed.

Breaking Down m/44'/60'/0'/0/0

1. m represents the master key derived directly from the mnemonic phrase.

2. 44' confirms adherence to BIP-44, enabling interoperability across compliant wallets.
3. 60' specifies Ethereum as the target blockchain, covering mainnet, testnets, and token transfers.
4. 0' indicates the primary account, often labeled “Account 1” in MetaMask or Trust Wallet interfaces.
5. The first 0 without an apostrophe means external chain—the receiving addresses visible to others.
6. The final 0 is the index of the first address generated under that account and chain.

Why Hardened vs Non-Hardened Matters

1. Hardened components (ending in ') require the parent private key to derive the child private key, adding a layer of security against public key leakage.

2. Non-hardened components allow derivation using only the parent public key, useful for watch-only wallets but riskier if misused.
3. In m/44'/60'/0'/0/0, the first three levels are hardened to protect the integrity of the entire wallet structure.
4. The last two levels are non-hardened to enable efficient generation of new receiving and change addresses without exposing sensitive data.
5. Mixing hardened and non-hardened segments balances usability with cryptographic safety in everyday transactions.

Frequently Asked Questions

Q: Can I manually change the derivation path in MetaMask?A: No. MetaMask uses m/44'/60'/0'/0/0 by default and does not expose derivation path configuration to users.

Q: Does changing the account number (e.g., m/44'/60'/1'/0/0) give me a completely separate wallet?A: Yes. Each account derives its own set of addresses from the same seed but operates independently—balances and transaction history do not overlap.

Q: Why do some wallets show different addresses for the same derivation path?A: Discrepancies arise from variations in EIP-155 chain ID handling, differing interpretations of testnet parameters, or incorrect implementation of BIP-44 standards.

Q: Is m/44'/60'/0'/1/0 a valid path?A: Yes. That path points to the first change address in Account 0, typically used internally by wallets to handle transaction change outputs.