summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorRoger Dingledine <arma@torproject.org>2006-03-25 23:23:19 +0000
committerRoger Dingledine <arma@torproject.org>2006-03-25 23:23:19 +0000
commit6652d821b277f78098855b130b4b2475efb25567 (patch)
treea8253a6d16b7d2ca682dead9dc92fbe3dd974b63
parent8f75d5d0a22ccb2002153e1eca4aecfce873b0ab (diff)
downloadtor-6652d821b277f78098855b130b4b2475efb25567.tar.gz
tor-6652d821b277f78098855b130b4b2475efb25567.zip
If you run a fast server, can you run your client elsewhere?
svn:r6238
-rw-r--r--doc/incentives.txt14
1 files changed, 14 insertions, 0 deletions
diff --git a/doc/incentives.txt b/doc/incentives.txt
index 088832aaca..5b805549d1 100644
--- a/doc/incentives.txt
+++ b/doc/incentives.txt
@@ -324,6 +324,20 @@
Alice to have a low reputation, and the only high bandwidth circuit
Alice could use would be via the evil node.
+3.14. If you run a fast server, can you run your client elsewhere?
+
+ A lot of people want to run a fast server at a colocation facility,
+ and then reap the rewards using their cablemodem or DSL Tor client.
+
+ If we use anonymous micropayments, where reputation can literally
+ be transferred, this is trivial.
+
+ If we pick a design where servers accrue reputation and can only
+ use it themselves, though, the clients can configure the servers as
+ their entry nodes and "inherit" their reputation. In this approach
+ we would let servers configure a set of IP addresses or keys that get
+ "like local" service.
+
4. Sample designs.
4.1. Two classes of service for circuits.