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
Copy file name to clipboardexpand all lines: README.md
+7-5
Original file line number
Diff line number
Diff line change
@@ -581,15 +581,17 @@ e.g., stop sending additional funds to addresses derived from it.
581
581
it will still be possible to spend the funds,
582
582
and even recovered participants can participate in signing sessions.)
583
583
584
-
### Blame Functionality
584
+
### Blaming Faulty Parties
585
585
586
586
Any faulty party can make a ChillDKG session abort by sending a message that deviates from the protocol specification.
587
-
To help investigating and resolving these protocol failures, ChillDKG provides *blame functionality*
588
-
that enables honest protocol parties to identify and blame at least one participant suspected to be faulty:[^missing-messages]
587
+
To help investigating and resolving these protocol failures, ChillDKG provides a *blame functionality*
588
+
that enables honest protocol parties to identify and blame at least one participant suspected to be faulty:
589
589
- If an honest participant aborts the session, then this participant will blame at least one participant or the coordinator.
590
590
- If an honest coordinator aborts the session, then the coordinator then will blame at least one participant.
591
591
592
-
[^missing-messages]: If a session is stuck due to missing messages, the receiving party will (trivially) know who has not sent their protocol messages (yet).
592
+
Moreover, a party which, instead of aborting after having received an invalid protocol message,
593
+
aborts due to a timeout while waiting for a protocol message
594
+
will trivially blame the party who is supposed to send the outstanding message.
593
595
594
596
The aborting party will be guaranteed that the suspected party is indeed faulty
595
597
*only if* all messages in the ChillDKG session have been transmitted correctly over the communication links,
@@ -599,7 +601,7 @@ It is important to understand that this is a conditional statement.
599
601
For example, assume that the condition of a honest coordinator is violated.
600
602
In that case, even if all participants are honest, the malicious coordinator can deviate from the protocol in a way that makes one participant blame another participant, when, in fact, it is the coordinator who is faulty and not the suspected participant.
601
603
602
-
In some cases,[^incorrect-shares], an aborting participant needs to obtain an auxiliary *investigation message* from the coordinator
604
+
In some cases,[^incorrect-shares] an aborting participant needs to obtain an auxiliary *investigation message* from the coordinator
603
605
before a suspected participant can be determined (see below).
604
606
605
607
[^incorrect-shares]: Namely, when having received incorrect secret shares.
0 commit comments