-
Notifications
You must be signed in to change notification settings - Fork 271
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
ECDSA adaptor signature implementation #292
Comments
I assume you're not aware of BlockstreamResearch/secp256k1-zkp#117 ? (libsecp256k1-zkp is a fork of libsecp256k1 that adds some features that probably would not be accepted into libsecp256k1 at this point because they may not relevant enough to the Bitcoin ecosystem, or it's simply too early to have them in libsecp256k1.) |
No, definitely was not 🤦 I did a search for ECDSA adaptor signature implementations before I got started, but didn't find that impl. At least now I thoroughly understand how ECDSA adaptor signatures work... Thanks for the link. Their impl doesn't appear to contain a proof for |
That's an interesting point. Just reply in the PR there. It was merged just earlier this week. |
Ok, will do. |
Hello, I was searching for the implementation of Schnorr adaptor signatures and came across this conversation. Can I ask where I can find it? I checked https://github.com/BlockstreamResearch but didn't find any clues. I would be glad if anyone could help me with this. I find this conversation relevant, so I'm posting here. |
See this issue: BlockstreamResearch/secp256k1-zkp#191 Spoiler: There is no implementation. |
I've recently implemented the ECDSA adaptor signature scheme from Generalized Bitcoin-Compatible Channels.
The library solely depends on
rust-secp256k1
, and I made some changes to expose some necessary functions. In your contributing guide, it suggests making all crypto contributions upstream to the Clibsecp256k1
library. Would the changes I've made torust-secp256k1
(geneferneau/rust-secp256k1@2e6e833) be welcome as a PR here, or should I upstream by re-implementing ECDSA adaptor signatures inlibsecp256k1
?My next steps are to implement Schnorr adaptor signatures, so same questions there.
Thanks for any feedback.
The text was updated successfully, but these errors were encountered: