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

Investigate the scenario of merging two protocols #3

Closed
fjarri opened this issue Oct 12, 2024 · 2 comments
Closed

Investigate the scenario of merging two protocols #3

fjarri opened this issue Oct 12, 2024 · 2 comments
Assignees
Labels
enhancement New feature or request
Milestone

Comments

@fjarri
Copy link
Member

fjarri commented Oct 12, 2024

Two variants here:

  • executing two protocols simultaneously,
  • chaining two protocols one after the other.

How much boilerplate is required to do that? What tools can we provide for the users to make it easier?

@fjarri fjarri added the enhancement New feature or request label Oct 12, 2024
@fjarri fjarri added this to the v0.1.0 milestone Oct 14, 2024
@fjarri
Copy link
Member Author

fjarri commented Oct 25, 2024

I just realized that due to the more dynamic nature of our protocols we may be able to get away with defining just one struct and make it handle multiple rounds. Same goes for malicious behavior tests by the way - no need to override each round separately.

@fjarri fjarri self-assigned this Nov 1, 2024
@fjarri
Copy link
Member Author

fjarri commented Nov 3, 2024

Chaining will be implemented in #60, merging specifically is more defined now and is tracked by #61. This can be closed.

@fjarri fjarri closed this as completed Nov 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant