Address path (BIP32) defines how to derive private and public keys of a wallet from a binary master seed (m) and an ordered set of indices.
BIP32 derivation path:
m / 0' / 0' /k'
BIP32 extended private key represents the extended private key derived from the derivation path. An example of a BIP32 extended private key is:
xprv9v3zEm9W9QhLnMUEG9BkmpmGAf96uXh5NLMsdLWCVLur1fj26MY5ZjcXrb2aBF4U6uhzzs7Vw9jGopHxBYjsSmgozFBakbGiBgffGHunjTB
Trezor and BIP32 address paths
Trezor uses BIP44, which is based on BIP32. BIP44 dictates the derivation path:
m / purpose' / coin_type' / account' / change / address_index
Overview of standard derivation paths of recovery seeds know by the latest Trezor firmware
Cryptocurrencies
BIP44-like paths (discoverable):
- m/44'/cointype'/account'/change/address ... BIP44 P2PKH
- m/49'/cointype'/account'/change/address ... BIP49 P2WPKH-nested-in-P2SH
- m/84'/cointype'/account'/change/address ... BIP84 P2WPKH
BIP44-like paths (non-discoverable):
- m/48'/cointype'/account'/change/address ... multisig P2SH, implemented in Copay wallet, no BIP or SLIP defined
Others:
- m/48'/network'/role'/account'/key' ... SLIP48 Graphene-based blockchains
Custom cryptography
- m/13'/A'/B'/C'/D' ... SLIP13 Sign in with Trezor
- m/17'/A'/B'/C'/D' ... SLIP17 ECDH
- m/10015'/0' ... SLIP15 Trezor Wallet labeling metadata
- m/10016'/0 ... SLIP16 Trezor Password Manager metadata