-
Notifications
You must be signed in to change notification settings - Fork 73
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
Module to handle mnemonics #3
Comments
This issue now has a bounty-address via issuETH. |
new token-transfer transaction on rinkeby with value 4.2WALL |
Token-transfer transaction on rinkeby with value 4.2WALL |
1 similar comment
Token-transfer transaction on rinkeby with value 4.2WALL |
Hello, I want to submit a PR for this but have a question regarding the project layout. Of course, it can add it as its own module but it just seems to be missing its spot. How flexible is the project layout? |
YAY
Did not yet look that deep into mnemonics - but I think there should be a module BIP-32 that depends on BIP-44 and crypto - don't you think this would work? Would love to avoid putting it in crypto as I like small modules - unix style
can you elaborate what you mean? I want it to be as flexible and modular as possible - if you have ideas - shoot! |
Thanks, |
Sounds great - happy coding!-) |
@mirceanis totally forgot: might also be interesting to @rmeissner and @fmrsabino - they already have a implementation with kethereum dependencies in their repo: https://github.com/gnosis/heimdall-android/tree/master/mnemonic - just not a big fan of having the wordlists in memory all the time there - but perhaps it could share some tests or ideas. |
Yeah, we planned to refactor and test our implementation and then also provide a PR. But of course we are happy to take another implementation ;). Concerning dependencies to bip32/bip44: imo bip39 is only to generate a seed from a mnemonic. That seed then is used to generate the root node that you can use to derive the children nodes with bip32/bip44. We kept these in different modules in our project, so that we can move small parts to other projects. |
This is the private key encrypted for the assignee: |
Currently the only open issue is to load the wordlist only when needed, right? I would propose to make bip32 and bip39 two different modules (since bip32 is not about mnemonics). Another question for me is what is the best way to handle spongycastle with proguard. Since some of the crypto algorithms used by bip39 are only available through spongycastle and we use a provider to load them we need to exclude everything from spongycastle from proguard (which I really don't want to do). In our project we directly use the spongy castle implementations (therefore we can use proguard and obfuscation since they are directly referenced). I know this might not make sense for other platforms (and maybe upcoming android versions where this is not needed). EDIT: |
No description provided.
The text was updated successfully, but these errors were encountered: