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

A special error variant for improbable cases #80

Open
fjarri opened this issue Jan 1, 2025 · 0 comments
Open

A special error variant for improbable cases #80

fjarri opened this issue Jan 1, 2025 · 0 comments
Labels
API Involves backwards-incompatible changes of the public API question Further information is requested security Counteracting malicious behavior
Milestone

Comments

@fjarri
Copy link
Member

fjarri commented Jan 1, 2025

For some protocols, it is possible to have a situation in finalize() which is a fault, not attributable (because it's not a result of someone's malicious action), but whose probability is statistically negligible. For example, if in a KeyGen the secret shares generated by the nodes add up to zero.

What should we do for such situations? Just return LocalError? Have a special error variant which will mean for the user "just restart the protocol" as opposed to them getting a LocalError and halting the node because they think it's a bug?

@fjarri fjarri added question Further information is requested API Involves backwards-incompatible changes of the public API labels Jan 1, 2025
@fjarri fjarri added this to the v1.0.0 milestone Jan 1, 2025
@fjarri fjarri added the security Counteracting malicious behavior label Jan 1, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
API Involves backwards-incompatible changes of the public API question Further information is requested security Counteracting malicious behavior
Projects
None yet
Development

No branches or pull requests

1 participant