Skip to content

Commit 0e986db

Browse files
text: Improve blaming section
1 parent 865252a commit 0e986db

File tree

1 file changed

+7
-5
lines changed

1 file changed

+7
-5
lines changed

README.md

+7-5
Original file line numberDiff line numberDiff line change
@@ -581,15 +581,17 @@ e.g., stop sending additional funds to addresses derived from it.
581581
it will still be possible to spend the funds,
582582
and even recovered participants can participate in signing sessions.)
583583
584-
### Blame Functionality
584+
### Blaming Faulty Parties
585585
586586
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:
589589
- If an honest participant aborts the session, then this participant will blame at least one participant or the coordinator.
590590
- If an honest coordinator aborts the session, then the coordinator then will blame at least one participant.
591591
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.
593595
594596
The aborting party will be guaranteed that the suspected party is indeed faulty
595597
*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.
599601
For example, assume that the condition of a honest coordinator is violated.
600602
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.
601603
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
603605
before a suspected participant can be determined (see below).
604606
605607
[^incorrect-shares]: Namely, when having received incorrect secret shares.

0 commit comments

Comments
 (0)