-
Notifications
You must be signed in to change notification settings - Fork 52
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
Epic: Demo for Trusted Dealer key share generation #238
Closed
6 tasks done
mpguerra opened this issue
Feb 10, 2023
· 4 comments
· Fixed by ZcashFoundation/frost-zcash-demo#2, ZcashFoundation/frost-zcash-demo#3 or ZcashFoundation/frost-zcash-demo#4
Closed
6 tasks done
Epic: Demo for Trusted Dealer key share generation #238
mpguerra opened this issue
Feb 10, 2023
· 4 comments
· Fixed by ZcashFoundation/frost-zcash-demo#2, ZcashFoundation/frost-zcash-demo#3 or ZcashFoundation/frost-zcash-demo#4
Labels
Comments
9 tasks
mpguerra
changed the title
Demo for key shares generation
Demo for Trusted Dealer key share generation
Feb 22, 2023
Hey team! Please add your planning poker estimate with Zenhub @conradoplg @dconnolly @natalieesk |
13 tasks
This was
linked to
pull requests
May 8, 2023
I didn't mean to close this issue. There's more to be done. |
mpguerra
changed the title
Demo for Trusted Dealer key share generation
Epic: Demo for Trusted Dealer key share generation
May 25, 2023
I think this is big enough for an epic by itself |
All done! 🎉 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Motivation
We want to simulate a simple execution of FROST to show potential FROST implementers how to use the FROST library.
Scope
Build a simple CLI that runs trusted dealer key generation and writes out the necessary data to the terminal. Demo can take in a number of participants and will generate a number of unique identifiers for the number of participants, it will then generate all of the various data required in each round
Specification
On startup, the Trusted Dealer demo will prompt for:
s
)MAX_PARTICIPANTS
)MIN_PARTICIPANTS
)The dealer CLI will then use that data to generate:
s_1
-s_MAX_PARTICIPANTS
- by runningtrusted_dealer_keygen
PK
(which is the same asvss_commitment[0]
) - by runningtrusted_dealer_keygen
vss_commitment
- by runningtrusted_dealer_keygen
PK_1
-PK_MAX_PARTICIPANTS
- by runningderive_group_info
This above data will be output by the Trusted Dealer demo to the terminal (or a file or wherever it makes sense) to be input into the Participant CLI (#239) during the Signature Generation demo.
The text was updated successfully, but these errors were encountered: