-
Notifications
You must be signed in to change notification settings - Fork 17
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
Restructure library #72
Conversation
Crate direct depsDirect deps
Compared to base branchDiff
All depscargo tree
Compared to base branchDiff
|
The spec was successfully compiled. PDF is available here. |
Benchmark ResultBenchmarks
|
072a9fb
to
266f41d
Compare
cggmp21-keygen/src/progress.rs
Outdated
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.
Symlink this one similarly to hex_or_bin?
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.
Oh wait, it's gone from main protocol? Weren't we also using it to profile there?
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.
We expose this module (we have to if we want someone to do profiling), so cggmp21::progress just re-exports cggmp21_keygen::progress
.
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.
It probably should be a dedicated crate actually, maybe we'll move it soon
Did you forget to remove keygen files from |
CGGMP21 DKG has been proved to be UC-secure, and thus it can be safely reused with other UC-secure TSS implementations. To make it reusable, this PR moves DKG implementation into separate crate
cggmp21-keygen
, and key share definition into separate cratekey-share