1
0
mirror of https://github.com/trezor/trezor-firmware.git synced 2024-12-22 14:28:07 +00:00

docs: fix markdown syntax in coins/readme

This commit is contained in:
Pavol Rusnak 2018-08-28 16:16:43 +02:00
parent af63104d21
commit 92eb6b8fe1
No known key found for this signature in database
GPG Key ID: 91F3B339B9A02A3D

View File

@ -1,6 +1,4 @@
List of used BIP-44 derivation paths
------------------------------------
# List of used BIP-44 derivation paths
| coin | curve | getPublicKey | getAddress | sign | derivation | note |
|----------------|----------------|----------------|------------------|------------------|-----------------|--------------|
@ -13,10 +11,8 @@ List of used BIP-44 derivation paths
| NEM | ed25519 | - | 44'/43'/a'/0'/0' | 44'/43'/a'/0'/0' | SLIP-0010 | [5](#NEM) |
| Monero | ed25519 | 44'/128'/a'<sup>[6](#Monero)</sup> | 44'/128'/a' | 44'/128'/a' | SLIP-0010 | |
## Notes
1. <a name="ETHPublicKey"></a> 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. <a name="Ripple"></a> 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`.
@ -31,7 +27,4 @@ List of used BIP-44 derivation paths
7. <a name="BitcoinDiagram"></a> With some exceptions. The following diagram shows a path should be validated for Bitcoin-like coins:
![](bitcoin-path-check.svg)
![bitcoin-path-check](bitcoin-path-check.svg)