diff options
Diffstat (limited to 'spec/srv-spec/protocol.md')
| -rw-r--r-- | spec/srv-spec/protocol.md | 20 |
1 files changed, 10 insertions, 10 deletions
diff --git a/spec/srv-spec/protocol.md b/spec/srv-spec/protocol.md index 683b65e..67aa493 100644 --- a/spec/srv-spec/protocol.md +++ b/spec/srv-spec/protocol.md @@ -10,7 +10,7 @@ Now we go through the phases of the protocol: <a id="srv-spec.txt-3.1"></a> -## Commitment Phase \[COMMITMENTPHASE\] +## Commitment Phase {#COMMITMENTPHASE} The commit phase lasts from 00:00UTC to 12:00UTC. @@ -23,7 +23,7 @@ included in Alice's vote. <a id="srv-spec.txt-3.1.1"></a> -### Voting During Commitment Phase +### Voting During Commitment Phase {#commitment-voting} During the commit phase, each authority includes in its votes: @@ -43,7 +43,7 @@ authorities. Any subsequent commitments MUST be ignored. <a id="srv-spec.txt-3.1.2"></a> -### Persistent State During Commitment Phase \[STATECOMMIT\] +### Persistent State During Commitment Phase {#STATECOMMIT} During the commitment phase, authorities save in their persistent state the authoritative commits they have received from each authority. Only one commit @@ -51,7 +51,7 @@ per authority must be considered trusted and active at a given time. <a id="srv-spec.txt-3.2"></a> -## Reveal Phase +## Reveal Phase {#reveal-phase} The reveal phase lasts from 12:00UTC to 00:00UTC. @@ -60,7 +60,7 @@ reveal their random values. <a id="srv-spec.txt-3.2.1"></a> -### Voting During Reveal Phase +### Voting During Reveal Phase {#reveal-voting} During the reveal phase, each authority includes in its votes: @@ -77,7 +77,7 @@ the new commitment MUST be ignored. <a id="srv-spec.txt-3.2.2"></a> -### Persistent State During Reveal Phase \[STATEREVEAL\] +### Persistent State During Reveal Phase {#STATEREVEAL} During the reveal phase, authorities keep the authoritative commits from the commit phase in their persistent state. They also save any received reveals @@ -90,7 +90,7 @@ its votes. <a id="srv-spec.txt-3.3"></a> -## Shared Random Value Calculation At 00:00UTC +## Shared Random Value Calculation At 00:00UTC {#midnight-utc} Finally, at 00:00UTC every day, authorities compute a fresh shared random value and this value must be added to the consensus so clients can use it. @@ -107,7 +107,7 @@ would in the first round of the commitment phase (section \[COMMITMENTPHASE\]). <a id="srv-spec.txt-3.3.1"></a> -### Shared Randomness Calculation \[SRCALC\] +### Shared Randomness Calculation {#SRCALC} An authority that wants to derive the shared random value SRV, should use the appropriate reveal values for that time period and calculate SRV as @@ -133,7 +133,7 @@ are ordered based on the R_a value in ascending order. <a id="srv-spec.txt-3.4"></a> -## Bootstrapping Procedure +## Bootstrapping Procedure {#bootstrapping} As described in \[CONS\], two shared random values are required for the HSDir overlay periods to work properly as specified in proposal 224. Hence @@ -144,7 +144,7 @@ produced, which takes 48 hours. <a id="srv-spec.txt-3.5"></a> -## Rebooting Directory Authorities \[REBOOT\] +## Rebooting Directory Authorities {#REBOOT} The shared randomness protocol must be able to support directory authorities who leave or join in the middle of the protocol execution. |