You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am working on implementing multisig functionality using the MuSig protocol for a taproot keypath spend, and I could use some guidance.
I understand that MuSig allows for multisig transactions that are indistinguishable from regular transactions by aggregating multiple signatures into a single one that can be verified from a single public key.
I have found examples of script-path spend with multisig but these are distinguishable as multisig transactions due to the Bitcoin script. What I am looking for is a way to do this with a keypath spend to maintain the privacy advantages of single-sig transactions.
I am hoping for some guidance on how to implement these steps using the bitcoinjs library. Any code examples or general advice would be greatly appreciated.
Thank you for your help.
The text was updated successfully, but these errors were encountered:
Minghell0x
changed the title
Guidance on Implementing MuSig Multisig in a Taproot Keypath Spend
Guidance on Implementing MuSig in a Taproot Keypath Spend
Jul 14, 2023
Hello,
I am working on implementing multisig functionality using the MuSig protocol for a taproot keypath spend, and I could use some guidance.
I understand that MuSig allows for multisig transactions that are indistinguishable from regular transactions by aggregating multiple signatures into a single one that can be verified from a single public key.
I have found examples of script-path spend with multisig but these are distinguishable as multisig transactions due to the Bitcoin script. What I am looking for is a way to do this with a keypath spend to maintain the privacy advantages of single-sig transactions.
I am hoping for some guidance on how to implement these steps using the bitcoinjs library. Any code examples or general advice would be greatly appreciated.
Thank you for your help.
The text was updated successfully, but these errors were encountered: