aboutsummaryrefslogtreecommitdiff
path: root/proposals/234-remittance-addresses.txt
diff options
context:
space:
mode:
authorNick Mathewson <nickm@torproject.org>2014-04-14 16:52:29 -0400
committerNick Mathewson <nickm@torproject.org>2014-04-14 16:52:29 -0400
commit1c57e5de3b0de3eee2ee44b1ae2a0c800c2d5a76 (patch)
treec4e75249b94ecd9128163b848cfe244b9a581946 /proposals/234-remittance-addresses.txt
parentf1ea369418afc2bbbce3288ab2b5f1c1d88a8e5d (diff)
downloadtorspec-1c57e5de3b0de3eee2ee44b1ae2a0c800c2d5a76.tar.gz
torspec-1c57e5de3b0de3eee2ee44b1ae2a0c800c2d5a76.zip
Reflow proposals 233, 234.
Diffstat (limited to 'proposals/234-remittance-addresses.txt')
-rw-r--r--proposals/234-remittance-addresses.txt41
1 files changed, 22 insertions, 19 deletions
diff --git a/proposals/234-remittance-addresses.txt b/proposals/234-remittance-addresses.txt
index 55cd8bd..303df85 100644
--- a/proposals/234-remittance-addresses.txt
+++ b/proposals/234-remittance-addresses.txt
@@ -6,31 +6,34 @@ Status: Open
1. Motivation
-We wish to add the ability for individual users to donate to the owners of
-relay operators using a cryptocurrency. We propose adding an optional line to
-the torrc file which will be published in the directory consensus and listed
-on https://compass.torproject.org.
+
+ We wish to add the ability for individual users to donate to the
+ owners of relay operators using a cryptocurrency. We propose adding
+ an optional line to the torrc file which will be published in the
+ directory consensus and listed on https://compass.torproject.org.
2. Proposal
-Allow an optional "RemittanceAddresses" line to the torrc file containing
-comma-delimited cryptocurrency URIs. The format is:
-RemittanceAddressses <currency1>:<address>1,<currency2>:<address2>
+ Allow an optional "RemittanceAddresses" line to the torrc file
+ containing comma-delimited cryptocurrency URIs. The format is:
+
+ RemittanceAddressses <currency1>:<address>1,<currency2>:<address2>
-For an example using an actual bitcoin and namecoin address, this is:
+ For an example using an actual bitcoin and namecoin address, this is:
-RemittanceAddressses bitcoin:19mP9FKrXqL46Si58pHdhGKow88SUPy1V8,namecoin:NAMEuWT2icj3ef8HWJwetZyZbXaZUJ5hFT
+ RemittanceAddressses bitcoin:19mP9FKrXqL46Si58pHdhGKow88SUPy1V8,namecoin:NAMEuWT2icj3ef8HWJwetZyZbXaZUJ5hFT
-The contents of a relay's RemittanceAddresses line will be mirrored in
-the relay's router descriptor (which is then published in the directory
-consensus). This line will be treated akin to the ContactInfo field. A
-cryptocurrency address may not contain a colon, comma, whitespace, or other
-nonprintable ASCII.
+ The contents of a relay's RemittanceAddresses line will be mirrored in
+ the relay's router descriptor (which is then published in the
+ directory consensus). This line will be treated akin to the
+ ContactInfo field. A cryptocurrency address may not contain a colon,
+ comma, whitespace, or other nonprintable ASCII.
-Like the ContactInfo line, there is no explicit length limit for
-RemittanceAddressses---the only limit is the length of the entire descriptor.
-If the relay lists multiple addresses of the same currency type (e.g., two
-bitcoin addresses), only the first (left-most) one of each currency is
-published in the directory consensus.
+ Like the ContactInfo line, there is no explicit length limit for
+ RemittanceAddressses---the only limit is the length of the entire
+ descriptor. If the relay lists multiple addresses of the same
+ currency type (e.g., two bitcoin addresses), only the first
+ (left-most) one of each currency is published in the directory
+ consensus.