The Path Numbers Behind Hierarchical Wallet Addresses

On February 11, 2012, BIP32 turned hierarchical wallet path numbers into coordinates: each integer selects one deterministic child key from a seed-rooted tree. The mechanism replaced the operational burden of backing up fresh, unrelated keys with repeatable derivation from an extended key, which combines a key with a 32-byte chain code. A path does not live onchain, move liquidity or set a fee. It tells wallet software which keys to derive; the resulting public key or script becomes an address.

What do the numbers in a wallet derivation path mean?

In a common BIP44 path such as m/44'/0'/0'/0/17, each number names a branch below the master node, m. BIP44, assigned on April 24, 2014, gave five levels standard meanings so independently built wallets could find the same keys:

• 44' identifies the BIP44 layout, rather than another wallet purpose.
• 0' selects Bitcoin's registered coin type; Ether uses 60'.
• 0' selects the first logical account.
• 0/17 selects the external receiving chain and its eighteenth address, because indexing starts at zero; change conventionally uses branch 1.

The numbers are inputs to child-key derivation, not account balances or blockchain IDs. Reusing a seed with a different path therefore produces a valid but different wallet—one reason a correct recovery phrase can appear empty in mismatched software.

Why are some path numbers hardened?

Apostrophes mark hardened children, which can be derived only from private parent material. BIP32 reserves indices from 0 through 2,147,483,647 for normal children and the upper half of the 32-bit range for hardened children; writing 44' is shorthand for adding 2,147,483,648.

Normal derivation lets a payment server receive an extended public key and generate new deposit addresses without holding a spending key. That is useful separation, but it creates a sharp risk boundary: BIP32 warns that a parent extended public key plus any descendant non-hardened private key can reveal the parent private key. Hardened account branches block that route upward, at the cost of preventing public-only derivation across the boundary.

Do derivation paths change liquidity or transaction fees?

Derivation paths do not change liquidity or fees; they change control, bookkeeping and exposure. In the operating model of universal bridge merchants, a merchant can assign separate branches to networks, counterparties or settlement roles. The merchant still supplies inventory and bears inventory, custody and settlement risk. Users or the service pay transaction costs; validators or miners collect network fees, while the merchant may collect a quoted spread or service fee. None of those economics is encoded in the path.

Why do path numbers matter for wallet builders?

They matter because convention turns deterministic mathematics into interoperability. Before a shared hierarchy, software could derive perfectly valid trees that other software did not know where to scan. BIP44 improved portability, account separation and watch-only operations, but its discovery convention stops after 20 unused external addresses, so aggressive address issuance can strand funds from a default scan.

The practical verdict is that path numbers are infrastructure metadata, not cosmetic labels: builders should version, store and export the exact derivation policy alongside seed backups. What remains unknowable from a seed alone is which competing purposes, coin types, accounts or custom branches an application used. Determinism recreates keys; convention is what makes them discoverable.