Derive child BIP32 extended private/public key
See original GitHub issueFirst, I don’t know whether this tool is able to derive child BIP32 extended private/public key?
Second, is BIP32 Root Key
used as an input field? This seems to be weird/confusing to me, because the the extended key fed by the user may not be the “root” key. I saw that BIP32 serielization format contains a “depth” field.
Did I misunderstand something?
Issue Analytics
- State:
- Created 4 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
The math behind BIP-32 child key derivation - Medium
Each node of the tree can be represented with an “extended private key”, which can be used to generate all children, grandchildren, etc....
Read more >How to derive public child keys from public parent keys with ...
This gives us two ways to derive a child public key: either from the child private key, or directly from the parent public...
Read more >Extended Keys - Learn Me A Bitcoin
Both extended private keys and extended public keys can derive children, each with their own unique index number. There are 3 methods for...
Read more >BIP 0032 - Bitcoin Wiki
4.1 Conventions; 4.2 Extended keys; 4.3 Child key derivation (CKD) functions. 4.3.1 Private parent key → private child key; 4.3.2 Public parent key...
Read more >4. Keys, Addresses, Wallets - Mastering Bitcoin [Book] - O'Reilly
In bitcoin, we use public key cryptography to create a key pair that controls access to bitcoins. The key pair consists of a...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Thank you for such a good detailed answer
BIP32 defines a 4-byte prefix called “version bytes” for encoding extended public and private keys. BIP32 only defines these for BTC mainnet and testnet which end up base58 encoded as
xprv
,xpub
,tprv
andtpub
. Even when you change to a different coin, their version bytes could be different (say IOP extended public keys start withdyw
). BIP84 simply redefined these version bytes so the end-user can see from the first characters what kind of scripts are needed to spend coins that belong to those private keys.If you decode both the xprv and zprv root keys, you will find out that they only differ in the first 4 bytes (version) and the last 4 bytes (checksum). Starting from mnemonic “steak road wreck man core squeeze bubble angry coffee race manual path defense beach chuckle” you get these bytes: