diff options
Diffstat (limited to 'spec/srv-spec/discussion.md')
| -rw-r--r-- | spec/srv-spec/discussion.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/spec/srv-spec/discussion.md b/spec/srv-spec/discussion.md index ea38318..59d26df 100644 --- a/spec/srv-spec/discussion.md +++ b/spec/srv-spec/discussion.md @@ -4,7 +4,7 @@ <a id="srv-spec.txt-6.1"></a> -## Why the added complexity from proposal 225? +## Why the added complexity from proposal 225? {#why-complexity} The complexity difference between this proposal and prop225 is in part because prop225 doesn't specify how the shared random value gets to the @@ -13,7 +13,7 @@ random values can always be readily accessible to clients. <a id="srv-spec.txt-6.2"></a> -## Why do you do a commit-and-reveal protocol in 24 rounds? +## Why do you do a commit-and-reveal protocol in 24 rounds? {#why-rounds} The reader might be wondering why we span the protocol over the course of a whole day (24 hours), when only 3 rounds would be sufficient to generate a @@ -32,7 +32,7 @@ recover and rejoin the protocol. <a id="srv-spec.txt-6.3"></a> -## Why can't we recover if the 00:00UTC consensus fails? +## Why can't we recover if the 00:00UTC consensus fails? {#why-no-recovery} If the 00:00UTC consensus fails, there will be no shared random value for the whole day. In theory, we could recover by calculating the shared |