aboutsummaryrefslogtreecommitdiff
path: root/spec/path-spec/guard-nodes.md
diff options
context:
space:
mode:
Diffstat (limited to 'spec/path-spec/guard-nodes.md')
-rw-r--r--spec/path-spec/guard-nodes.md5
1 files changed, 3 insertions, 2 deletions
diff --git a/spec/path-spec/guard-nodes.md b/spec/path-spec/guard-nodes.md
index 6b7bc8b..77f7fdf 100644
--- a/spec/path-spec/guard-nodes.md
+++ b/spec/path-spec/guard-nodes.md
@@ -1,4 +1,5 @@
<a id="path-spec.txt-5"></a>
+
# Guard nodes
We use Guard nodes (also called "helper nodes" in the research
@@ -7,6 +8,7 @@ our Guard selection algorithm -- which has grown rather complex -- see
guard-spec.txt.
<a id="path-spec.txt-5.1"></a>
+
## How consensus bandwidth weights factor into entry guard selection
When weighting a list of routers for choosing an entry guard, the following
@@ -29,7 +31,7 @@ If a router has been marked as both an entry guard and an exit, then we
prefer to use it more, with our preference for doing so (roughly) linearly
increasing w.r.t. the router's non-guard bandwidth and bandwidth weight
(calculated without taking the guard flag into account). From proposal
-#236:
+# 236:
|
| Let Wpf denote the weight from the 'bandwidth-weights' line a
@@ -40,4 +42,3 @@ increasing w.r.t. the router's non-guard bandwidth and bandwidth weight
| choose N proportionally to F*Wpf*B + (1-F)*Wpn*B.
where F is the weight as calculated using the above parameters.
-