arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-26 17:38:39 +00:00
Code Issues Releases Wiki Activity
75c14433de
trezor-firmware/docs/coins
History
Pavol Rusnak 92eb6b8fe1
docs: fix markdown syntax in coins/readme
2018-08-28 16:16:43 +02:00
..
bitcoin-path-check.svg docs: list of used derivation paths 2018-08-28 16:12:13 +02:00
README.md docs: fix markdown syntax in coins/readme 2018-08-28 16:16:43 +02:00

README.md

List of used BIP-44 derivation paths

coin curve getPublicKey getAddress sign derivation note
Bitcoin secp256k 44'/0'/a' 44'/0'/a'/y/i 44'/0'/a'/y/i BIP-32 7
Ethereum secp256k 44'/60'/a'{/0}1 44'/60'/a'/0/i 44'/60'/a'/0/i BIP-32
Ripple secp256k - 44'/144'/a'/0/i 44'/144'/a'/0/i BIP-32 2
Stellar ed25519 - 44'/148'/a' 44'/148'/a' SLIP-0010 3
Cardano ed25519 44'/1815'/a' 44'/1815'/a'/0/i 44'/1815'/a'/0/i Cardano's own4
Lisk ed25519 44'/134'/a' 44'/134'/a' 44'/134'/a' SLIP-0010
NEM ed25519 - 44'/43'/a'/0'/0' 44'/43'/a'/0'/0' SLIP-0010 5
Monero ed25519 44'/128'/a'6 44'/128'/a' 44'/128'/a' SLIP-0010

Notes

  1. This should probably be 44'/60'/a', but unfortunately MyEtherWallet sends 44'/60'/a'/0. So for backwards compatibility we allow both options. trezor.wallet.io sends 44'/60'/a'/0 for MEW compatibility.

  2. Although Ripple does not have the concept of change, it uses secp256k and has normal derivation defined. For interoperability reasons we use 44'/144'/a'/0/i.

  3. Defined by Stellar themselves in their SEP-0005.

  4. Which allows normal derivation on ed25519.

  5. NEM's path should probably be 44'/60'/a', but due to historical reasons this is set to 44'/60'/a'/0'/0'.

  6. Actually it is GetWatchKey for Monero.

  7. With some exceptions. The following diagram shows a path should be validated for Bitcoin-like coins:

bitcoin-path-check