You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Description
The key generation spec, and the associated verification, need a bit more clarity, particularly about what should happen when something goes wrong. At the moment, they generally assume reliable broadcast throughout, but the current implementation (and probably most future implementations) only have point-to-point communication.
Possible Solution
Perhaps we could assume a reliable broadcast step at the end, i.e. that the transcript of the key generation protocol is posted on the Bulletin Board (the precise definition/implementation of which can be deferred), and describe what attacker model can be defeated in that communication model.
This discussion was converted from issue #80 on September 16, 2021 16:16.
Heading
Bold
Italic
Quote
Code
Link
Numbered list
Unordered list
Task list
Attach files
Mention
Reference
Menu
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Generic Issue
Description
The key generation spec, and the associated verification, need a bit more clarity, particularly about what should happen when something goes wrong. At the moment, they generally assume reliable broadcast throughout, but the current implementation (and probably most future implementations) only have point-to-point communication.
Possible Solution
Perhaps we could assume a reliable broadcast step at the end, i.e. that the transcript of the key generation protocol is posted on the Bulletin Board (the precise definition/implementation of which can be deferred), and describe what attacker model can be defeated in that communication model.
Beta Was this translation helpful? Give feedback.
All reactions