commit 4f15ab616e2870d574c7522c0740ad89972d143e
Author: David Goulet <[email protected]>
Date:   Mon Feb 15 15:39:03 2016 -0500

    prop250: Mention the hard limit of 255 dirauth
    
    Signed-off-by: David Goulet <[email protected]>
---
 proposals/250-commit-reveal-consensus.txt | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/proposals/250-commit-reveal-consensus.txt 
b/proposals/250-commit-reveal-consensus.txt
index 262630f..cd19b4c 100644
--- a/proposals/250-commit-reveal-consensus.txt
+++ b/proposals/250-commit-reveal-consensus.txt
@@ -331,6 +331,9 @@ Supersedes: 225
    To maintain consistent ordering in HASHED_REVEALS, all the ID_a | R_a pairs
    are ordered based on the R_a value in ascending order.
 
+   Because the number of reveals (REVEAL_NUM) is using a 1 byte value, it
+   imposes a hard limit of 255 authorities participating in the protocol.
+
 3.4. Bootstrapping Procedure
 
    As described in [CONS], two shared random values are required for the HSDir

_______________________________________________
tor-commits mailing list
[email protected]
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits

Reply via email to