← Back to Bitcoin Improvement Proposals
BIPinformationalkey-management

Fix bip85

1. changed `parse256(IL) ≥ n or ki = 0` --to--> `parse256(IL) is 0 or ≥ n ` as there is no new child key `ki` created via `parse256(IL) + kpar (mod n)` therefore it should be clear that we want to check if `parse256(IL)` is not 0 as in master key generation (bip32) not some `ki` that is not even defined. 2. also added incorrect key warning to XPRV part where it should be checked either 3. incorrect key warning is now placed in footnotes

No reviews
scgbckbone·Updated Aug 1, 2020·0 reviews·0 attestations·View source
Collections:BIPs — Merged

Specification

  1. changed parse256(IL) ≥ n or ki = 0 --to--> parse256(IL) is 0 or ≥ n as there is no new child key ki created via parse256(IL) + kpar (mod n) therefore it should be clear that we want to check if parse256(IL) is not 0 as in master key generation (bip32) not some ki that is not even defined.

  2. also added incorrect key warning to XPRV part where it should be checked either

  3. incorrect key warning is now placed in footnotes

Discussion (0 threads)

Loading discussions...