arno/trezor-firmware
1
0
Fork 0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-11-13 19:18:56 +00:00
Code Issues Releases Wiki Activity

docs: coin paths final modifications (hopefully)

Browse Source
This commit is contained in:
Tomas Susanka 2018-08-29 17:03:58 +02:00
parent f8f1a62563
commit fc4b71ae06
1 changed files with 18 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

32
docs/coins/README.md
View File

@ -1,30 +1,34 @@
# BIP-44 derivation paths
Each coin uses [BIP-44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) derivation path scheme. If the coin does not support normal derivation (because the underlying curve does not support it for example) we're using Stellar's [SEP-0005](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md). In a nutshell, these paths are derived using [SLIP-0010](https://github.com/satoshilabs/slips/blob/master/slip-0010.md) and have only three-part BIP-44 path `44'/c'/a'`.
Each coin uses [BIP-44](https://github.com/bitcoin/bips/blob/master/bip-0044.mediawiki) derivation path scheme. If the coin supports normal derivation we use [BIP-32](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki). If not (because the underlying curve does not support it for example) we're using Stellar's [SEP-0005](https://github.com/stellar/stellar-protocol/blob/master/ecosystem/sep-0005.md). In a nutshell, these paths are derived using [SLIP-0010](https://github.com/satoshilabs/slips/blob/master/slip-0010.md) and have only three-part BIP-44 path `44'/c'/a'`.
## List of used 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](https://github.com/bitcoin/bips/blob/master/bip-0032.mediawiki) | [4](#BitcoinDiagram) |
| Ethereum | secp256k | 44'/60'/a' | 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 | |
| Stellar | ed25519 | - | 44'/148'/a' | 44'/148'/a' | [SLIP-0010](https://github.com/satoshilabs/slips/blob/master/slip-0010.md) | |
| Cardano | ed25519 | 44'/1815'/a' | 44'/1815'/a'/0/i | 44'/1815'/a'/0/i | [Cardano's own](https://cardanolaunch.com/assets/Ed25519_BIP.pdf)<sup>[1](#Cardano)</sup> | |
| Lisk | ed25519 | 44'/134'/a' | 44'/134'/a' | 44'/134'/a' | SLIP-0010 | |
| NEM | ed25519 | - | 44'/43'/a' | 44'/43'/a' | SLIP-0010 | [2](#NEM) |
| Monero | ed25519 | 44'/128'/a'<sup>[3](#Monero)</sup> | 44'/128'/a' | 44'/128'/a' | SLIP-0010 | |
| Bitcoin | secp256k | 44'/0'/a' | 44'/0'/a'/y/i | 44'/0'/a'/y/i | BIP-32 | [6](#BitcoinDiagram) |
| Ethereum | secp256k | 44'/60'/0' | 44'/60'/0'/0/i | 44'/60'/0'/0/i | BIP-32 | [1](#Ethereum)|
| Ripple | secp256k | - | 44'/144'/a'/0/0 | 44'/144'/a'/0/0 | BIP-32 | [2](#Ripple) |
| Cardano | ed25519 | 44'/1815'/a' | 44'/1815'/a'/0/i | 44'/1815'/a'/0/i | [Cardano's own](https://cardanolaunch.com/assets/Ed25519_BIP.pdf)<sup>[3](#Cardano)</sup> | |
| Stellar | ed25519 | - | 44'/148'/a' | 44'/148'/a' | SLIP-0010 | |
| Lisk | ed25519 | 44'/134'/a' | 44'/134'/a' | 44'/134'/a' | SLIP-0010 | |
| NEM | ed25519 | - | 44'/43'/a' | 44'/43'/a' | SLIP-0010 | [4](#NEM) |
| Monero | ed25519 | 44'/128'/a'<sup>[5](#Monero)</sup> | 44'/128'/a' | 44'/128'/a' | SLIP-0010 | |
Paths that do not conform to this table are allowed, but user needs to confirm a warning on Trezor. For getPublicKey we do not check if the path is followed by other non-hardened items (anyone can derive those anyway). This is beneficial for Ethereum and its MEW compatibility, which sends `44'/60'/a'/0` for getPublicKey.
Paths that do not conform to this table are allowed, but user needs to confirm a warning on Trezor. For getPublicKey we do not check if the path is followed by other non-hardened items (anyone can derive those anyway). This is beneficial for Ethereum and its MEW compatibility, which sends `44'/60'/0'/0` for getPublicKey.
## Notes
1. <a name="Cardano"></a> Which allows normal derivation on ed25519.
1. <a name="Ethereum"></a> We believe we should use `44'/60'/a'` for Ethereum, because it is account-based, rather than UTXO-based. Unfortunately, lot of Ethereum tools (MEW, Metamask) do not use such scheme and set `a = 0` and then iterate the address index `i`. Therefore for compatibility reasons we use the same scheme: `44'/60'/0'/0/i` and only the `i` is being iterated.
2. <a name="NEM"></a> NEM's path should be `44'/60'/a'` as per SEP-0005, but we allow `44'/60'/a'/0'/0'` as well for compatibility reasons with NanoWallet.
2. <a name="Ripple"></a> Similar to Ethereum this should be `44'/144'/a'`. But for compatibility with other HW vendors we use `44'/144'/a'/0/0`.
3. <a name="Monero"></a> Actually it is GetWatchKey for Monero.
3. <a name="Cardano"></a> Which allows normal derivation on ed25519.
4. <a name="BitcoinDiagram"></a> It is a bit more complicated for Bitcoin-like coins. The following diagram shows how path should be validated for Bitcoin-like coins:
4. <a name="NEM"></a> NEM's path should be `44'/60'/a'` as per SEP-0005, but we allow `44'/60'/a'/0'/0'` as well for compatibility reasons with NanoWallet.
5. <a name="Monero"></a> Actually it is GetWatchKey for Monero.
6. <a name="BitcoinDiagram"></a> It is a bit more complicated for Bitcoin-like coins. The following diagram shows how path should be validated for Bitcoin-like coins:
![bitcoin-path-check](bitcoin-path-check.svg)