diff options
author | Roger Dingledine <arma@torproject.org> | 2006-03-25 22:37:44 +0000 |
---|---|---|
committer | Roger Dingledine <arma@torproject.org> | 2006-03-25 22:37:44 +0000 |
commit | 8f75d5d0a22ccb2002153e1eca4aecfce873b0ab (patch) | |
tree | 1ccfc26452c7fe2cc1af994cb4c310b3f6e41210 /doc/incentives.txt | |
parent | e90bebf27b11badaf6649107bda5dcf117d903da (diff) | |
download | tor-8f75d5d0a22ccb2002153e1eca4aecfce873b0ab.tar.gz tor-8f75d5d0a22ccb2002153e1eca4aecfce873b0ab.zip |
try to make it clearer that eigentrust is one way to do the
"deputy tester" design, but there are simpler ways too.
svn:r6237
Diffstat (limited to 'doc/incentives.txt')
-rw-r--r-- | doc/incentives.txt | 5 |
1 files changed, 3 insertions, 2 deletions
diff --git a/doc/incentives.txt b/doc/incentives.txt index 8c1ee7738c..088832aaca 100644 --- a/doc/incentives.txt +++ b/doc/incentives.txt @@ -51,10 +51,11 @@ The option above has the directory servers doing all of the measurements. This doesn't scale. We can set it up so we have "deputy testers" -- trusted other nodes that do performance testing and report - their results. If we want to be really adventurous, we could even + their results. + + If we want to be really adventurous, we could even accept claims from every Tor user and build a complex weighting / reputation system to decide which claims are "probably" right. - One possible way to implement the latter is something similar to EigenTrust [http://www.stanford.edu/~sdkamvar/papers/eigentrust.pdf], where the opinion of nodes with high reputation more is weighted |