-
Notifications
You must be signed in to change notification settings - Fork 338
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
Write own BIP39 implementation #561
Comments
@jblachly I think it's too late to add this as a 2022 summer of bitcoin project, but I'll tag it as a good first issue for someone new. |
Thanks; accidentally started with that template (there was no other feature request template) and didn't realize it would add an issue tag. |
No problem, it's on my todo list to add an enhancement issue template. 😅 |
Hey, guys !! |
Hi @violet360! |
Ok cool, for sure :) |
@violet360 @Eunoia1729 How is progress on this issue so far? |
c752ccb Expose bip39::Error (志宇) Pull request description: <!-- You can erase any parts of this template not applicable to your Pull Request. --> ### Description Expose `bip39::Error` (fixes #581 ) ### Notes to the reviewers I am aware that the `bip39` module plans to be rewritten (as per #561 ), however this seems like a rather straightforward and quick change that may be useful in the short/mid term. ### Checklists #### Bugfixes: * [x] Expose `bip39::Error` ACKs for top commit: afilini: ACK c752ccb Tree-SHA512: 98b7ac1ba88aed07d9160830ee80496c32d531c15ada0e9b50a97f0883fbfced22fa83a7c7f8366aadb7e7a667d8a63dde869d31cc375206d277e55b2ec3089d
@Eunoia1729 are you stll working on this? :) |
Sorry for the late response. |
Hello @danielabrozzoni, has this been worked on? Can I pick it up? |
Nobody that I know of, you can pick it up :) |
Hey, sorry that I didn't update here but I started working on this earlier today. Should I continue? Perhaps we could work together? |
@atalw, yes we can work on it together. Can I reach out to you over discord? What is your discord handle? |
Awesome. It's |
I know we have @evanlinjin 's PR #644 in progress for this. But want to ask the question, since we already moved off of |
The problem is that the maintainer of rust-bitcoin/rust-bip39 is unresponsive to PRs |
If there are no technical reason against using rust-bitcoin/rust-bip39 then should we maintain and use a fork in the |
Sounds reasonable; alternatively if anyone has personal connections to org owners of rust-bitcoin we could lobby for an additional person to get admin permissions to the repository as co-maintainer |
@jblachly I'm going to close this issue as the rust-bitcoin/rust-bip39 crate seems to be back on track with new releases. Happy to reopen if you think more discussion is needed. |
As suggested in the code base:
bdk/src/keys/bip39.rs
Lines 14 to 17 in adf7d0c
I also recommend writing own BIP39 implementation.
In issue #399, BDK transitioned from
tiny-bip39
torust-bip39
, however, the latter package (which BDK now depends on) appears to be unmaintained or poorly maintained, with PRs and issues ignored for about a year.https://github.com/rust-bitcoin/rust-bip39
At a minimum, BIP39 wordlists, and words -> entropy -> seed generation would be valuable.
The text was updated successfully, but these errors were encountered: