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

bip-tapscript: merkle key tree isn't exactly a replacement for multisig #97

Closed
sipa opened this issue Oct 19, 2019 · 1 comment · Fixed by #109
Closed

bip-tapscript: merkle key tree isn't exactly a replacement for multisig #97

sipa opened this issue Oct 19, 2019 · 1 comment · Fixed by #109

Comments

@sipa
Copy link
Owner

sipa commented Oct 19, 2019

Review comment by @gmaxwell:

Even without MuSig, due to the signature hash committing to the tapleaf hash, signers must commit up front to the exact subset that will be signing. That means you can't just give a signature to the other signers and not care about who will complete it. A solution is providing signatures for all matching leaves, but this may be unreasonable for large multisig.

@sipa
Copy link
Owner Author

sipa commented Oct 21, 2019

See #109.

@sipa sipa closed this as completed in #109 Oct 23, 2019
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

Successfully merging a pull request may close this issue.

1 participant