-
Notifications
You must be signed in to change notification settings - Fork 136
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
Support for SLIP132's custom BIP32 prefixes #87
Comments
@afk11 thanks for raising this - agreed, libwally should allow serialization and deserialization for non-bip32 If needed, at the moment it could be implemented with a small workaround, eg in
|
Thanks for the response! I experimented with allowing developer provided definitions, and adding a pointer to a definition on ext_key. If no definition is set, the previous code working with BIP32_VER_MAIN_PUBLIC/BIP32_VER_MAIN_PRIVATE/etc is used: master...afk11:bip32-versions I had the same thoughts regarding bip32_key_unserialize, but since ^ adds extra arguments I went with separate functions for now. I'm pretty sure bip32_key_unserialize could populate the definition for whatever network it determines, and hence we could rule out special cases for keys with and without definitions. Let me know what you think anyway! |
At least trezor and electrum support SLIP132 base58 prefixes for extended keys, which indicate the script type to be derived.
I think it could be worth adding a flags parameter to bip32_key_from_base58[,_alloc], otherwise could expose the behavior through a separate function and avoid the BC break?
The text was updated successfully, but these errors were encountered: