aboutsummaryrefslogtreecommitdiff
path: root/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md')
-rw-r--r--spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md4
1 files changed, 3 insertions, 1 deletions
diff --git a/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md b/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md
index 51f3624..dce072c 100644
--- a/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md
+++ b/spec/rend-spec-v3/publishing-shared-random-values-pub-sharedrandom.md
@@ -1,4 +1,5 @@
<a id="rend-spec-v3.txt-2.3"></a>
+
## Publishing shared random values [PUB-SHAREDRANDOM]
Our design for limiting the predictability of HSDir upload locations
@@ -17,6 +18,7 @@ According to proposal 250, we add two new lines in consensuses:
```
<a id="rend-spec-v3.txt-2.3.1"></a>
+
### Client behavior in the absence of shared random values
If the previous or current shared random value cannot be found in a
@@ -33,6 +35,7 @@ rounded down; period_num is calculated as specified in
found originally.
<a id="rend-spec-v3.txt-2.3.2"></a>
+
### Hidden services and changing shared random values
It's theoretically possible that the consensus shared random values will
@@ -44,4 +47,3 @@ should use the new shared random values to find the new responsible HSDirs
and upload their descriptors there.
XXX How long should they upload descriptors there for?
-