-
Notifications
You must be signed in to change notification settings - Fork 40
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
Remove reliance on secp256k1_zkp
#226
Conversation
f6af857
to
a815785
Compare
@bennyhodl: Perhaps I'm missing the point, but why does it matter where you import the types from? Whether you import transitively through
This seems impossible since we need to use ECDSA adaptor signatures to implement the DLC protocol. |
Inline with the ₿itcoin crate is best imo. For example, we cannot do #221 becuase
It should be opened in broader discussion to implement adaptor signatures to |
Wouldn't it be simpler to ask the I think what you are proposing here may not even work because, once you bump
Yeah, if ECDSA adaptor signatures were added to |
Moved to draft until |
secp256k1_zkp
complicates updatingbitcoin
to new minor version. Issues that I faced with #223. This is a better starting point for #221 & #223 will be closed if this is merged.Using
secp256k1_zkp
does not make much sense when it is exported frombitcoin
. Changes all references except theEcdsaAdaptorSignature
. Would like options to removesecp256k1_zkp
completely.