[tor-commits] [torspec/master] Be more specific about consensus method 26 changes.

[nickm@xxxxxxxxxxxxxx]

commit df2b04bf5b011cb46c603366e9e3cce34b2fbcaa
Author: Matt Traudt <sirmatt@xxxxxxx>
Date:   Wed Oct 26 21:05:18 2016 -0400

    Be more specific about consensus method 26 changes.
---
 dir-spec.txt | 7 +++++--
 1 file changed, 5 insertions(+), 2 deletions(-)

diff --git a/dir-spec.txt b/dir-spec.txt
index 5ea0242..73eca11 100644
--- a/dir-spec.txt
+++ b/dir-spec.txt
@@ -2614,8 +2614,11 @@ The following methods have incorrect implementations; authorities SHOULD
 
   Let weight_scale = 10000
 
-  Starting with consensus method 26, G, M, E, and D are initialized to 1.
-  Prior consensus methods initialize them to 0.
+  Starting with consensus method 26, G, M, E, and D are initialized to 1 and
+  T to 4. Prior consensus methods initialize them all to 0. With this change,
+  test tor networks that are small or new are much more likely to produce
+  bandwidth-weights in their consensus. The extra bandwidth has a negligible
+  impact on the bandwidth weights in the public tor network.
 
   Let G be the total bandwidth for Guard-flagged nodes.
   Let M be the total bandwidth for non-flagged nodes.



_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits