-
Notifications
You must be signed in to change notification settings - Fork 80
rename keys::{Secret, Public} #106
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
Conversation
960a873
to
87bc9d4
Compare
6f2b3fc
to
bfc0c89
Compare
Codecov ReportBase: 83.76% // Head: 82.78% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## main #106 +/- ##
==========================================
- Coverage 83.76% 82.78% -0.98%
==========================================
Files 17 17
Lines 1287 1313 +26
==========================================
+ Hits 1078 1087 +9
- Misses 209 226 +17
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
@mergify rebase |
❌ Base branch update has failedGit reported the following error:
err-code: 758C9 |
bfc0c89
to
d2e70b9
Compare
Conflicts solved |
d2e70b9
to
c9956c7
Compare
@dconnolly your changes look good, is this ready to go? |
Yeah approved; I kept getting in analysis paralysis of trying to name things better, but also correspond accurately to the accepted language around shamir secret sharing, verifiable secret sharing (commitments), verifying shares/keys, etc etc, so might as well just merged for now :P |
I can relate, we can have another pass at renaming stuff after we are up to date with the spec 😁 |
Based on #105
Closes #59
Not sure about the names, these were what made sense to me, feel free to suggest other names.