-
Notifications
You must be signed in to change notification settings - Fork 59
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
Doesn't pass BIP-0039 test vectors #21
Comments
Where in the spec did you find this example? The full list is here: https://github.com/trezor/python-mnemonic/blob/master/vectors.json Also, this library has been abandoned for a long time with tiny-bip39 taking its place. |
My apologies. Don't remember where that test vector came from. Updated with a vector from the list; same result. If the crate is abandoned, perhaps tiny-bip39 should take over the namespace bip39 or the bip39 crate should be flagged abandoned somehow. Especially if it's not spec-compliant it can cause fund loss. |
Please please please if it is not used any more can you direct people to the better crate on the main readme? |
Actually, it is "only" the v0.6.0-beta.1 that has these problems. The v0.5.1 passes all tests. My impression is that @steveatinfincia merged in pull requests from @maciejhirsz and @QuestofIranon and then regretted those braking changes on the API, so he did not pull in the actual fixes provided by them. If you prefer the API of 0.5, use this crate, if you prefer the API of 0.6, use tiny-bip39. We at Internet of People decided to go with the new API. |
Looking over at crates.io, the number of downloads for 0.6.0-beta1 is troubling. I reckon it should at very least be yanked to keep people on 0.5.1 (CC @steveatinfincia). |
The currently listed Rust implementation of BIP 39 doesn't pass the reference implementation's test vectors. See --> infincia/bip39-rs#21
The currently listed Rust implementation of BIP 39 doesn't pass the reference implementation's test vectors. See --> infincia/bip39-rs#21
This crate has a bug. I noticed it doesn't have any unit test that verifies the implementation against the test vectors in the BIP39 spec.
That example is director from the spec and it fails.
The text was updated successfully, but these errors were encountered: