From 1c57e5de3b0de3eee2ee44b1ae2a0c800c2d5a76 Mon Sep 17 00:00:00 2001 From: Nick Mathewson Date: Mon, 14 Apr 2014 16:52:29 -0400 Subject: Reflow proposals 233, 234. --- proposals/234-remittance-addresses.txt | 41 ++++++++++++++++++---------------- 1 file changed, 22 insertions(+), 19 deletions(-) (limited to 'proposals/234-remittance-addresses.txt') 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 :
1,: + Allow an optional "RemittanceAddresses" line to the torrc file + containing comma-delimited cryptocurrency URIs. The format is: + + RemittanceAddressses :
1,: -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. -- cgit v1.2.3-54-g00ecf