diff options
Diffstat (limited to 'spec/srv-spec/overview.md')
| -rw-r--r-- | spec/srv-spec/overview.md | 8 |
1 files changed, 4 insertions, 4 deletions
diff --git a/spec/srv-spec/overview.md b/spec/srv-spec/overview.md index 6da4599..a9f4c99 100644 --- a/spec/srv-spec/overview.md +++ b/spec/srv-spec/overview.md @@ -22,7 +22,7 @@ cryptographically hashes the random value and calls the output its The idea is that given a reveal value you can cryptographically confirm that it corresponds to a given commitment value (by hashing it). However given a commitment value you should not be able to derive the underlying reveal -value. The construction of these values is specified in section [COMMITREVEAL]. +value. The construction of these values is specified in section \[COMMITREVEAL\]. <a id="srv-spec.txt-2.1"></a> @@ -62,7 +62,7 @@ Commit phase: <a id="srv-spec.txt-2.3"></a> -## How we use the consensus [CONS] +## How we use the consensus \[CONS\] The produced shared random values need to be readily available to clients. For this reason we include them in the consensus documents. @@ -70,7 +70,7 @@ clients. For this reason we include them in the consensus documents. Every hour the consensus documents need to include the shared random value of the day, as well as the shared random value of the previous day. That's because either of these values might be needed at a given time for a Tor -client to access a hidden service according to section [TIME-OVERLAP] of +client to access a hidden service according to section \[TIME-OVERLAP\] of proposal 224. This means that both of these two values need to be included in votes as well. @@ -124,7 +124,7 @@ reachability consequences for hidden service clients. <a id="srv-spec.txt-2.4"></a> -## Persistent State of the Protocol [STATE] +## Persistent State of the Protocol \[STATE\] A directory authority needs to keep a persistent state on disk of the on going protocol run. This allows an authority to join the protocol seamlessly |