Duplicate account private keys from bip32 / bip44 derivation

From the BIP32 spec,

In case parse256(IL) ≥ n or ki = 0, the resulting key is invalid, and one should proceed with the next value for i. (Note: this has probability lower than 1 in 2^127.)

and it seems that the bip32 library automatically selects the next i in the sequence:

// if parse256(IL) >= n, proceed with the next value for i
if (!ecc.isPrivate(IL)) return this.derive(index + 1);

(permalink)

Does this mean that when deriving the keys for different accounts, if at the account level (as per BIP44) an i is "skipped", the "skipped" account and the next valid account will have the entirely same tree of keys?



from Recent Questions - Bitcoin Stack Exchange https://ift.tt/UZJln76
via IFTTT

Popular posts from this blog

Bitcoin Mining Could Be Strengthening The Ruble, Russian Central Bank Says

Crypto Exec Warns Tokenization Is Moving Faster Than Expected

Bitwise Clients Pour $69M Into Solana as Bulls Fight to Reclaim $200 Resistance Zone