-
Notifications
You must be signed in to change notification settings - Fork 208
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
Implement sign-to-contract scheme for BIP-340 signatures #154
Comments
I have a very old implementation that adds sign-to-contract commitments to the schnorrsig module bitcoin-core/secp256k1#589. Way after this PR was opened, we added the |
Excellent, thank you! But how do you think, can we do that in the original library? It will be really preferable for me to have it there. |
I think it could be reasonably added to upstream libsecp since it doesn't require a separate module. |
Thank you. I rebased your commits with fixups on the master in https://github.com/LNP-BP/secp256k1/tree/schnorr-commitments Now I will integrate these types into existing custom signature type following your way of doing that on this PR |
@dr-orlovsky what is the status of your work? Do you plan on continuing it? I'd be very interested in using this to implement the antiklepto/anti-exfil protocol in the BitBox02 for Schnorr sigs (it's already deployed for ECDSA sigs). |
Hi @benma! Yes, I would like to continue, but in the mean time I am out of timing capacity to do that :( Feel free to grab it if you'd like... |
@dr-orlovsky thanks, I'll take this task then |
I opened a draft implementation here: bitcoin-core/secp256k1#1140 |
The library already has an API for sign-to-contract signature tweaks for ECDSA, but not BIP-340 Schnorrs. This issue is to colect a feedback on the best way of its implementation before I will start work on a PR.
The text was updated successfully, but these errors were encountered: