diff options
Diffstat (limited to 'spec/srv-spec/specification-spec.md')
-rw-r--r-- | spec/srv-spec/specification-spec.md | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/spec/srv-spec/specification-spec.md b/spec/srv-spec/specification-spec.md index 63ffaff..8118f6d 100644 --- a/spec/srv-spec/specification-spec.md +++ b/spec/srv-spec/specification-spec.md @@ -1,6 +1,6 @@ <a id="srv-spec.txt-4"></a> -# Specification \[SPEC\] +# Specification {#spec} <a id="srv-spec.txt-4.1"></a> @@ -20,7 +20,7 @@ in their votes to announce that they take part in the protocol. <a id="srv-spec.txt-4.1.1"></a> -### Computing commitments and reveals \[COMMITREVEAL\] +### Computing commitments and reveals {#COMMITREVEAL} A directory authority that wants to participate in this protocol needs to create a new pair of commitment/reveal values for every protocol @@ -48,7 +48,7 @@ REVEAL = base64-encode( TIMESTAMP || H(RN) ) <a id="srv-spec.txt-4.1.2"></a> -### Validating commitments and reveals \[VALIDATEVALUES\] +### Validating commitments and reveals {#VALIDATEVALUES} Given a COMMIT message and a REVEAL message it should be possible to verify that they indeed correspond. To do so, the client extracts the random value @@ -64,7 +64,7 @@ correspond to commit values published during the Commitment Phase. <a id="srv-spec.txt-4.1.4"></a> -### Encoding commit/reveal values in votes \[COMMITVOTE\] +### Encoding commit/reveal values in votes {#COMMITVOTE} An authority puts in its vote the commitments and reveals it has produced and seen from the other authorities. To do so, it includes the following in its @@ -82,7 +82,7 @@ REVEAL which is "sha3-256" for version 1. <a id="srv-spec.txt-4.1.5"></a> -### Shared Random Value \[SRVOTE\] +### Shared Random Value {#SRVOTE} Authorities include a shared random value (SRV) in their votes using the following encoding for the previous and current value respectively: @@ -101,14 +101,14 @@ period should be listed before the values of the current period. <a id="srv-spec.txt-4.2"></a> -## Encoding Shared Random Values in the consensus \[SRCONSENSUS\] +## Encoding Shared Random Values in the consensus {#SRCONSENSUS} Authorities insert the two active shared random values in the consensus following the same encoding format as in \[SRVOTE\]. <a id="srv-spec.txt-4.3"></a> -## Persistent state format \[STATEFORMAT\] +## Persistent state format {#STATEFORMAT} As a way to keep ground truth state in this protocol, an authority MUST keep a persistent state of the protocol. The next sub-section suggest a |