md: Overview of session

README.md

@@ -511,9 +511,25 @@ If a participant deems a protocol session successful (see above), then this part
 
 ### Overview of a ChillDKG Session
 
-TODO Write
-
-![chilldkg diagram](images/chilldkg-sequence.png)
+The following figure shows an execution of the participants and the coordinator.
+Arrows indicate network messages between the participants.
+For simplicity, only one participant is depicted;
+all participants run the identical code and send messages at the same steps.
+
+![The diagram shows the message flow between participant and a coordinator.
+The first of two phases "Generation of host public keys" involves the participant invokes the function hostpubkey with parameter seed and sends the returned hostpubkey to the coordinator.
+The second phase "Session" is initiated by the coordinator sending hostpubkeys and t to the participant.
+The participant invokes participant_step1 and sends the returned pmsg1 to the coordinator.
+The coordinator invokes coordinator_step and sends the returned cmsg1 to the participant.
+The participant invokes participant_step2 and sends the returned pmsg2 to the coordinator.
+The coordinator invokes coordinator_finalize and sends the returned cmsg2 to the participant.
+The participant invokes participant_finalizes, which ends the second phase.
+](images/chilldkg-sequence.png "ChillDKG")
+
+A participant can more than one session with the same host public key,
+and multiple sessions may be run concurrently.
+
+Whenever a function call fails, the corresponding party will not continue the session.
 
 ### API Documentation
 

images/chilldkg-sequence.txt

@@ -1,5 +1,4 @@
 @startuml
-title ChillDKG
 participant Participant
 participant Coordinator
 
@@ -10,11 +9,11 @@ end
 
 group Session
 Coordinator->Participant: hostpubkeys, t
-rnote over Participant: partcipant_step1(...)
+rnote over Participant: participant_step1(...)
 Participant->Coordinator: pmsg1
 rnote over Coordinator: coordinator_step(...)
 Coordinator->Participant: cmsg1
-rnote over Participant: partcipant_step2(...)
+rnote over Participant: participant_step2(...)
 Participant->Coordinator: pmsg2
 rnote over Coordinator: coordinator_finalize(...)
 Coordinator->Participant: cmsg2