Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of bitpay.com
	designates 209.85.212.177 as permitted sender)
	client-ip=209.85.212.177; envelope-from=jgarzik@bitpay.com;
	helo=mail-wi0-f177.google.com; 
MIME-Version: 1.0
In-Reply-To: <CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com>
References: <FB36762E8B574F7AAB7D25618841CF01@grabhive.com>
	<CANEZrP3rqTW_DEZ75B9tg6kNPtfX4ENBJupaJD1axSLsxMdCwQ@mail.gmail.com>
Date: Tue, 30 Jul 2013 10:01:56 -0400
Message-ID: <CAJHLa0PcxdCwHRN8ZrpOyD_NWPfBod4SJNooxpMXQUqHg102uQ@mail.gmail.com>
From: Jeff Garzik <jgarzik@bitpay.com>
To: Mike Hearn <mike@plan99.net>
Content-Type: text/plain; charset=ISO-8859-1
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Tor and Bitcoin
Precedence: list

On Tue, Jul 30, 2013 at 8:41 AM, Mike Hearn <mike@plan99.net> wrote:
> * Talk the Tor protocol directly and have the app explicitly pick its own
> diverse set of exit nodes, one per p2p connection. This is likely to be
> complicated. Last time I looked Tor doesn't provide any kind of library or
> API.

This has been discussed on IRC, and would be interesting to explore.
For several applications, linking directly with a Tor library is far
superior to the fragility of requiring a properly configured external
process.  Lacking such a Tor library right now, one must be written
<hint hint>

-- 
Jeff Garzik
Senior Software Engineer and open source evangelist
BitPay, Inc.      https://bitpay.com/