-
Notifications
You must be signed in to change notification settings - Fork 10
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
Allow custom coin configuration for BIP49 or others #4
Comments
Hi, thanks Different coins use different cryptographic standards, and depending on that, you can use specific tools for key generation.
There are also specific tools for certain coin standards, like: which coin do you need? |
I'd like to generate keys for the Electra Protocol layer 2 (Omni XEP). |
Bip49 / Slip44 / secp256k1 |
Apologies for the delay. Could you please clarify exactly what you need? I’ll review it and either add it to the package or submit a pull request. |
@mrtnetwork, I need to generate wallets for crypto not listed in your project. Basically, this: |
I will consider for the next update |
Thank you, @mrtnetwork. If you're planning to add support for the Electra protocol, I’d recommend holding off for now as I'm still creating and testing the wallet. |
Hi @mrtnetwork, I created a PR for this repository and another for bitcoin_base. Both to complete the integration with OmniXEP. Many thanks! |
It would still be nice to have a generic interface, so people can add their own coin config, without needing to submit a PR. |
@mrtnetwork, are you planning to release a new version of blockchain_utils and bitcoin_base soon? I'd love to get rid of my forks and launch OmniXEP mobile wallet without them, hehe. |
hi, a week ago I published them in pub dev with OmniXEP features. |
Oh, nice, I'll take a look. Thanks! |
Thanks for the awesome library!
I was wondering if there's a way to use BIP49 with a configuration not listed here.
If not, would it be possible to add support for new cryptocurrencies in this library?
It seems like the
fromSeed
method could potentially accept a custom configuration.The text was updated successfully, but these errors were encountered: