[ad_1]
I am making an attempt to duplicate a few of the Electrum’s functionalities so as to assist me perceive the Bitcoin protocol. Based on what I gathered from BIP-32 there are 3 baby key derivation features:
- non-public dad or mum key –> non-public baby key
- public dad or mum key –> public baby key
- non-public dad or mum key –> public baby key
I began with the next pattern mnemonic: historical inflict mimic valve baggage physician march sort out hour hazard shoot city.
I’ve efficiently derived the grasp non-public key and grasp public key. Nevertheless, when I attempt to derive the general public key related to the trail proven as m/0/0 by the pockets, the outcomes do not match. I’ve tried many code tweaks with a number of completely different outcomes. The anticipated outcomes are:
- public key: 022586d491bc387b161959e25d05772e98814da69215a3152b54e4d1ae0c1a4168
- deal with: bc1q83ljq9ad7rck4vdz0l7f7rr2zsprgn8rtvpmpa
I consider this is because of misunderstanding of the features themselves. A few of the factors that aren’t clear to me:
- Why are the chain codes equivalent in the event that they appear to be obtained by completely different processes?
This extension, known as the chain code, is equivalent for corresponding non-public and public keys, and consists of 32 bytes.
- Aren’t public keys typically anticipated to be independently derived from non-public keys by scalar multiplication? There appears to be two extra routes to derive prolonged public baby keys, specifically, both from a public dad or mum key or non-public dad or mum key, and by completely different means, in line with BIP-32.
- The non-public dad or mum key –> public baby key route includes a “neutered” key. What secret’s “neutered” and what’s this?
[ad_2]