Skip to content
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

handle different adversarial settings #9

Open
omershlo opened this issue Aug 14, 2021 · 0 comments
Open

handle different adversarial settings #9

omershlo opened this issue Aug 14, 2021 · 0 comments

Comments

@omershlo
Copy link
Contributor

The code currently assumes:

  1. all n refresh message arrive
  2. If 1 out of n messages fails the test the protocol fails.
    Therefore in the protocol we simply take the first t+1 refresh messages after we checked all n messages are valid. In practice we need to take the first t+1 messages of parties that passed all checks (doesn't have to be indices 1...t+1)

We need to add support for the case where some parties are malicious, meaning that we have some k honest parties ,t<k<n, and that the malicious parties can attack any party (adversary is not necessarily control indices k+1...n for example)

davidsemakula pushed a commit to davidsemakula/fs-dkr that referenced this issue Jul 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant