-
Notifications
You must be signed in to change notification settings - Fork 4
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
MP-ECDSA #37
Conversation
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.
Some scaffold looks OK, but generally doesn't seem like the approach you've taken is correct given the new architecture. There is no base DKG anymore and it does not rotate on sessions. The client API from dkg-substrate
is not being included in Tangle mainnet at all. There will be no best authorities, next best authorities, signature thresholds, etc. Everything should be tied to a job. After receiving job details we should execute keygen or signing protocols. CC @1xstj
…etween keygen and signing), begin adding public key gossip phase
Looks good. @tbraun96 lets rename webb-gadget to gadget-common and move the client.rs implementation there. Which will be reusable between all gadgets. |
Rename webb-gadget to gadget-common Make keystore more generalized
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! Just one comment about std feature, to avoid any conflicts when compiling tangle node/runtime.
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.
LGTM!
Closes #26