Skip to content
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

Guidance on Implementing MuSig in a Taproot Keypath Spend #1959

Open
Minghell0x opened this issue Jul 13, 2023 · 0 comments
Open

Guidance on Implementing MuSig in a Taproot Keypath Spend #1959

Minghell0x opened this issue Jul 13, 2023 · 0 comments

Comments

@Minghell0x
Copy link

Minghell0x commented Jul 13, 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.

@Minghell0x 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
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant