-
Notifications
You must be signed in to change notification settings - Fork 45
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
Derandomize RPO-STARK DSA #358
Conversation
Question not related to this PR: could the same methodology be used to make Falcon signature deterministic? Or is there something about the Flacon signatures that make it inherently impossible to do this. |
Yes, the same principle can be applied to Falcon as well though it will require a bit of care as signature generation uses a delicate sampling procedure and we would have to derandomize it fully. The key thing that we would have to insure is that the floating point arithmetic is stable across platforms, this is in addition to the need to build the seed using the above methodology. The above is well explained here especially Section 2 and the issue of robustness across devices of the sampling procedure is analyzed in Section 3.4.2. So the short answer is yes we can do it but we have to be more careful than the above. |
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good! Thank you!
Describe your changes
Derandomizes the RPO-STARK DSA in a similar manner to the proposal RFC6979 for ECDSA.
Once the issue of how to seed the salted Merkle tree vector commitment scheme in Winterfell is solved then this will be ready for review.
Checklist before requesting a review
next
according to naming convention.