doc: nest the example

This commit is contained in:
Vlad Stan 2023-04-10 11:53:38 +03:00 committed by GitHub
parent 0c302bfccd
commit 206d25c8a5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

17
704.md
View File

@ -33,13 +33,16 @@ m / purpose' / conin_type'`/ part1' / part2' / ... / part8'
- the reason for splitting is that each level of the path can have a max value of 2<sup>32</sup>-1
- the reason for using the peer's (`Bob`) public key is to always arive at the same value even if prio state is lost
When client `Alice` wants to build its `dm parent key` for `Bob` it has to:
- get the public key of `Bob` (in hex). Eg: `3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d`.
- split the public key hex string in 8 chunks:
- `3bf0c63f`, `cb934634`, `07af97a5`, `e5ee64fa`, `883d107e`, `f9e55847`, `2c4eb9aa`, `aefa459d`
- derive the `dm parent key`: `m/25709'/1237'/3bf0c63f'/cb934634'/.../aefa459d'`
<details>
<summary><b>Example</b></summary>
For example, if Alice wants to build its <code>dm parent key</code> for Bob she has to:
<ul>
<li>get the public key of `Bob` (in hex). Eg: <code>3bf0c63fcb93463407af97a5e5ee64fa883d107ef9e558472c4eb9aaaefa459d</code></li>
<li>split the public key hex string in 8 chunks:</li>
- <code>3bf0c63f</code>, <code>cb934634</code>, <code>07af97a5</code>, <code>e5ee64fa</code>, <code>883d107e</code>, <code>f9e55847</code>, <code>2c4eb9aa</code>, <code>aefa459d</code>
<li>derive the <code>dm parent key</code>: <code>m/25709'/1237'/3bf0c63f'/cb934634'/.../aefa459d'</code></li>
</ul>
</details>
dm/<action>/index
send, receive, marketplace