Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BIP 32: Test vectors for leading zeros #497

Merged
merged 2 commits into from
Mar 6, 2017

Conversation

iancoleman
Copy link
Contributor

These additional test vectors will ensure all future implementations are compliant with bip32.

See iancoleman/bip39#58 and bitpay/bitcore-lib#47

Possibly these test vectors may be useful also:

bitcoinjs-lib test for this issue

bitcore-lib test for this issue (pending merge)

These additional test vectors will ensure all future implementations are
interoperable.
See iancoleman/bip39#58
and bitpay/bitcore-lib#47
@sipa
Copy link
Member

sipa commented Feb 24, 2017

ACK.

I've verified these test vector myself by implementing them in Bitcoin Core's unit test framework.

Thanks for figuring out the cause of the divergence between clients.

schildbach pushed a commit to schildbach/bitcoinj that referenced this pull request Feb 25, 2017
schildbach pushed a commit to schildbach/bitcoinj that referenced this pull request Feb 25, 2017
@schildbach
Copy link
Contributor

ACK. I just added this test vector to bitcoinj (bitcoinj/bitcoinj#1342).

braydonf added a commit to braydonf/btcjs that referenced this pull request Mar 1, 2017
From vectors added in bitcoin/bips#497
@braydonf
Copy link

braydonf commented Mar 1, 2017

ACK. Also added in bitpay/bitcore-lib#97

@luke-jr luke-jr merged commit ead6fb2 into bitcoin:master Mar 6, 2017
schildbach pushed a commit to bitcoinj/bitcoinj that referenced this pull request Mar 6, 2017
schildbach pushed a commit to bitcoinj/bitcoinj that referenced this pull request Aug 24, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants