BIP32 amendment: base58chk-encoded extended keys are always 111 chars #1584
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Replaces #727. The description below is copied from that PR.
Base58chk-encoded extended keys are always 111 characters long. Amend wording of BIP32 accordingly.
Diff:
-This results in a Base58-encoded string of up to 112 characters.
+This results in a Base58-encoded string of exactly 111 characters.
Proof:
Version bytes:
0x0488b21e
(“xpub”),0x0488ade4
(“xprv”),0x043587cf
(“tpub”),0x04358394
(“tprv”)Largest version byte is
0x0488b21e
, smallest0x04358394
.Largest “possible” key:
Smallest “possible” key: