Validate decodePrivateKeyWif version and length #147
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.
The
decodePrivateKeyWif
function will currently allow a Legacy/Base58 BTC address.For example:
An example case where this might become pertinent is when a wallet scans a QR Code and has to distinguish between a WIF (for sweeping) and a Base58 Address (for sending funds to).
This PR does two things:
NOTE: I can't find a formalized spec for WIF and we might want to extend this PR a little bit.
The docs here: https://en.bitcoin.it/wiki/Wallet_import_format
... suggest that BTC might support some additional version codes:
it should be 0x80, however legacy Electrum or some SegWit vanity address generators may use 0x81-0x87
... which we might want to add to
Base58AddressFormatVersion
and also validate. Let me know if this is desired, will try to amend (unsure if we should still validate length in that case?).