-
Notifications
You must be signed in to change notification settings - Fork 10
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
Implement a key resharing protocol #96
Conversation
With key resharing protocol, they're not just HoleRanges anymore
@fjarri is attempting to deploy a commit to the entropyxyz Team on Vercel. A member of the Team first needs to authorize it. |
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## master #96 +/- ##
==========================================
+ Coverage 86.48% 87.18% +0.70%
==========================================
Files 44 45 +1
Lines 6644 7251 +607
==========================================
+ Hits 5746 6322 +576
- Misses 898 929 +31 ☔ View full report in Codecov by Sentry. |
e734616
to
e04d225
Compare
A part of #20. Not closing it yet since I'm not certain it's the best protocol to use, and it needs to be properly integrated with the rest of the framework. Also there is one pathway where a possible error is not attributable to any party - can be avoided by assuming that each party has access to public parts of keyshares of other nodes.
Merging this now because it has grown pretty big. Still more work needed to close the mentioned issues.
Public:
Internal:
HoleVec
toBTreeMap
when accumulating messages from other nodes.Finalizable
trait to handle tasks or checking whether the round can be finalized, and if not, whose messages are missing. (see Which layer should implement the check of whether a round can be finalized? #85)num_parties()
andparty_idx()
methods toRound
ShareIdx
type (a part of Support one party owning several key shares #31, decouplingPartyIdx
from the share index)