-
Notifications
You must be signed in to change notification settings - Fork 56
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
merge queue: embarking main (958fde3) and #730 together #775
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This commit contains changes to the frost-core crate which allow ciphersuites to better customize how signatures are computed. This will enable taproot support without requiring major changes to existing frost ciphersuites. Co-authored by @zebra-lucky and @mimoo This work sponsored by dlcbtc.com and lightspark.com
Co-authored by @zebra-lucky and @mimoo This work sponsored by dlcbtc.com and lightspark.com
Co-authored by @zebra-lucky and @mimoo This work sponsored by dlcbtc.com and lightspark.com
Uses r = e99ae2676eab512a3572c7b7655d633642a717250af57a7e0ccd5f9618b69f3f
With a couple of small adjustments to the code, we can remove the need for this extra associated type on the Ciphersuite crate. Accepting signature with odd-parity nonce values is OK, because BIP340 discard the nonce parity bit anyway.
…add-secp256k1-tr
…tation Thanks to @conradoplg for spotting this. The internal key is supposed to be represented as an even-parity point when adding the TapTweak point t*G. I added a regression test to ensure the tweaked verifying key and its parity match the BIP341 spec.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🎉 This pull request has been checked successfully and will be merged soon. 🎉
Branch main (958fde3) and #730 are embarked together for merge.
This pull request has been created by Mergify to speculatively check the mergeability of #730.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.
Required conditions of queue
main
for merge:#approved-reviews-by >= 1
[🛡 GitHub branch protection]#changes-requested-reviews-by = 0
[🛡 GitHub branch protection]#review-threads-unresolved = 0
[🛡 GitHub branch protection]base=main
Required conditions to stay in the queue:
#approved-reviews-by >= 1
[🛡 GitHub branch protection]#changes-requested-reviews-by = 0
[🛡 GitHub branch protection]#review-threads-unresolved = 0
[🛡 GitHub branch protection]