-
Notifications
You must be signed in to change notification settings - Fork 86
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
[Framework] Native function support deriving multi-sign address #2295
Comments
Secp256k1 public key can be converted to bitcoin p2tr and p2pkh. Should it be handled for all cases or just p2tr and p2pkh addresses from the public key bytes? |
To verify it, convert the pk bytes to the bitcoin address (address type unknown at the time) and check if it's the same address with the first |
The native function definition is changed. #2294 |
I will change it to |
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
…eys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey.
* [gh-2295] from verify_with_pk to verify_bitcoin_address_with_public_key. * [gh-2295] add derive_multi_sign_address. * [gh-2295] add derive_multisig_xonly_pubkey_from_public_keys and derive_bitcoin_taproot_address_from_multisig_xonly_pubkey. * [gh-2295] add functions of multisig xonly pubkeys. * [gh-2295] roolback from parse to new. * [gh-2295] make the newly added functions optional. * [gh-2295] fix move args. * [gh-2295] add tests and leave function unchanged. --------- Co-authored-by: Feliciss <10203-feliciss@users.noreply.0xacab.org>
#2294
The text was updated successfully, but these errors were encountered: