Delivery-Date: Mon, 27 Oct 2014 18:40:35 -0400
Return-Path: <tor-talk-bounces@lists.torproject.org>
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on moria.seul.org
X-Spam-Level: 
X-Spam-Status: No, score=-3.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
	RCVD_IN_DNSWL_MED,RP_MATCHES_RCVD,T_DKIM_INVALID,URIBL_BLACK autolearn=ham
	version=3.3.1
X-Original-To: archiver@seul.org
Delivered-To: archiver@seul.org
Received: from eugeni.torproject.org (eugeni.torproject.org [38.229.72.13])
	(using TLSv1.2 with cipher ADH-AES256-GCM-SHA384 (256/256 bits))
	(No client certificate requested)
	by khazad-dum.seul.org (Postfix) with ESMTPS id DB2BF1E0BE6;
	Mon, 27 Oct 2014 18:40:33 -0400 (EDT)
Received: from eugeni.torproject.org (localhost [127.0.0.1])
	by eugeni.torproject.org (Postfix) with ESMTP id 25EAC3100C;
	Mon, 27 Oct 2014 22:40:29 +0000 (UTC)
Received: from localhost (localhost [127.0.0.1])
 by eugeni.torproject.org (Postfix) with ESMTP id C618131001
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 22:40:24 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at eugeni.torproject.org
Received: from eugeni.torproject.org ([127.0.0.1])
 by localhost (eugeni.torproject.org [127.0.0.1]) (amavisd-new, port 10024)
 with ESMTP id ZyJdupm-jBVj for <tor-talk@lists.torproject.org>;
 Mon, 27 Oct 2014 22:40:24 +0000 (UTC)
X-Greylist: delayed 579 seconds by postgrey-1.34 at eugeni;
 Mon, 27 Oct 2014 22:40:24 UTC
Received: from outbound.mailhostbox.com (outbound.mailhostbox.com
 [162.222.225.22])
 by eugeni.torproject.org (Postfix) with ESMTP id 9FB0F30F9B
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 22:40:24 +0000 (UTC)
Received: from [0.0.0.0] (rainbowwarrior.torservers.net [77.247.181.164])
 (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
 (No client certificate requested)
 (Authenticated sender: s7r@sky-ip.org)
 by outbound.mailhostbox.com (Postfix) with ESMTPSA id 6969263976A
 for <tor-talk@lists.torproject.org>; Mon, 27 Oct 2014 22:30:40 +0000 (GMT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sky-ip.org;
 s=20110108; t=1414449042;
 bh=pD/5TImPaNR/dRXTRodgmu8jtbumWVbrDD6wLaIpHqQ=;
 h=Message-ID:Date:From:Reply-To:MIME-Version:To:Subject:References:
 In-Reply-To:Content-Type:Content-Transfer-Encoding;
 b=M8GyawFLFtiaFURL21q0FSVQZkVCDv897So0rmXpo2ubEA0OJxAzTb6yie3eYjgcF
 O/dtR9WkWr0cdcSAqd97jahr1JyohXMrT7TTb2iuoLLQvZ9Bsi5u6IaImOe68+oo83
 tSB33ZvuorbLm1sbk3FrRcEJPL6aLHPXm3bnzakA=
Message-ID: <544EC788.1010701@sky-ip.org>
Date: Tue, 28 Oct 2014 00:30:32 +0200
From: s7r <s7r@sky-ip.org>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
 rv:31.0) Gecko/20100101 Thunderbird/31.2.0
MIME-Version: 1.0
To: tor-talk@lists.torproject.org
References: <20141023191048.17a50660@meilong>
 <20141023232921.GF21428@torproject.org>
 <20141024103527.fd3ac8eff8862bf101b45d95@mega-nerd.com>
 <CAD2Ti2_QWc1Xq+uTvmurFLqjLVsSACMYYDzTAs7zk5SWyQE7Cw@mail.gmail.com>
 <544EA504.6070201@riseup.net>
In-Reply-To: <544EA504.6070201@riseup.net>
X-CTCH-RefID: str=0001.0A02020A.544EC792.00A6, ss=1, re=0.000, recu=0.000,
 reip=0.000, cl=1, cld=1, fgs=0
X-CTCH-VOD: Unknown
X-CTCH-Spam: Unknown
X-CTCH-Score: 0.000
X-CTCH-Rules: C_4847,
X-CTCH-Flags: 0
X-CTCH-ScoreCust: 0.000
X-CTCH-SenderID: s7r@sky-ip.org
X-CTCH-SenderID-TotalMessages: 1
X-CTCH-SenderID-TotalSpam: 0
X-CTCH-SenderID-TotalSuspected: 0
X-CTCH-SenderID-TotalBulk: 0
X-CTCH-SenderID-TotalConfirmed: 0
X-CTCH-SenderID-TotalRecipients: 0
X-CTCH-SenderID-TotalVirus: 0
X-CTCH-SenderID-BlueWhiteFlag: 0
Subject: Re: [tor-talk]
 =?windows-1252?q?Bitcoin_over_Tor_isn=92t_a_good_idea_?=
 =?windows-1252?q?=28Alex_Biryukov_/_Ivan_Pustogarov_story=29?=
X-BeenThere: tor-talk@lists.torproject.org
X-Mailman-Version: 2.1.15
Precedence: list
Reply-To: tor-talk@lists.torproject.org
List-Id: "all discussion about theory, design,
 and development of Onion Routing" <tor-talk.lists.torproject.org>
List-Unsubscribe: <https://lists.torproject.org/cgi-bin/mailman/options/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=unsubscribe>
List-Archive: <http://lists.torproject.org/pipermail/tor-talk/>
List-Post: <mailto:tor-talk@lists.torproject.org>
List-Help: <mailto:tor-talk-request@lists.torproject.org?subject=help>
List-Subscribe: <https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk>, 
 <mailto:tor-talk-request@lists.torproject.org?subject=subscribe>
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Errors-To: tor-talk-bounces@lists.torproject.org
Sender: "tor-talk" <tor-talk-bounces@lists.torproject.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Here are some Bitcoin reliable nodes sponsored by Thomas (TheCthulhu)
accessible via Tor hidden services:

h2vlpudzphzqxutd.onion

sbow7bnje2f4gcvt.onion

dioq2yg3l5ptgpge.onion

All use Bitcoin default port 8333. These servers are up all the time
and very fast.

Hidden services are end-to-end encrypted so the risk of MITM between
nodes does not exist. Also, if you run bitcoin in such a way with
onlynet=tor enabled in config, nobody listening your wire can have a
slight clue that you use bitcoin.

We think tor-hidden-services only Bitcoin nodes are a very important
part of the Bitcoin ecosystem.

Getting them running is quite simple. You just need disk space, at
least 50GB free for now. Here are some guides:

https://www.sky-ip.org/configure-bitcoin-node-debian-ubuntu.html

https://www.sky-ip.org/configure-bitcoin-node-freebsd.html

On 10/27/2014 10:03 PM, Thomas White wrote:
> I didn't realise my nodes didn't allow the bitcoin port. I'll get 
> right on it.
> 
> Also, if anyone in the Tor community has spare capacity, you can
> also setup a full bitcoin node on the same server you use as an 
> exit/relay/bridge and it doesn't take up a great deal of resources 
> other than disk space (16Gb I think right now and growing slowly).
> On my series of exits there is also full bitcoin nodes accessible 
> exclusively over hidden services and others which are accessible
> over regular clearnet.
> 
> -T
> 
> On 27/10/2014 19:58, grarpamp wrote:
>> On Thu, Oct 23, 2014 at 7:35 PM, Erik de Castro Lopo 
>> <mle+tools@mega-nerd.com> wrote:
> 
>> http://arxiv.org/pdf/1410.6079v1.pdf
> 
>>> Could this situation be improved if people ran limited exit
>>> nodes that only alloed the bitcoin p2p protocol to exit? I for
>>> one don't have enough
> 
>> There are about ten exit nodes that do only this today. [One of 
>> which is run by Mike Hearn who has advocated building in
>> censorship capabilities to Tor, and blocking (historically)
>> tainted coins (such as you have now or might receive through
>> otherwise completely innocent transactions with you, or from your
>> own trans/mixing with others).]
> 
>> Then there is question if your client will select such 'only
>> *coin' nodes versus those with high bandwidth and open exit
>> policies.
> 
>> There are also a fair number of hidden services in Tor/I2P/CJDNS
>>  that act as bitcoin nodes.
> 
>> As related tangent, yes, the bitcoin protocol needs to be 
>> encrypted on the wire, at least bitcoin node to bitcoin node
>> with TLS, obviously and urgently so, particularly if you wish to
>> guard your trans from wire listeners.
> 
>> You might be best to in fact run bitcoin always and entirely
>> over Tor, especially while transacting. But then also routinely
>> compare that received blockchain to one you receive via
>> alternate/trusted sources, such as clearnet or signed bittorrent
>> checkpoints.
> 
> 
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (MingW32)

iQEcBAEBAgAGBQJUTseIAAoJEIN/pSyBJlsRvDsH/1JTXOExUnLAtec2uGhloCAu
xuacUvwPAY9iJ102/PMQhFS6O2kc9tABiKPPWa2GSAx2pBlXuBSq74Rij8Q+bpv/
8VYAxT0uyVEGvXs2k579exuWrNkQ3uRQZcBnh/+EGBC+8UybaT9HGN1qnZ0vcI0r
+zW54ma8P+FY8JfxQVauDEJZtsrAXnr+2Riwzqd47l6aScM7PVKoVq/eLBuTwf5x
TqoxmxVuFdLxDxiReq73/8g2x9ecFjvrGb1/qkLo7mdV5f01/24gYP1EpXbbN8Rf
2C2fuYXihvJfGVtRkug1X9Wf+hwTIGgiGnIc+rhwg24NP62qPm3+Kxngs/zfysE=
=law6
-----END PGP SIGNATURE-----
-- 
tor-talk mailing list - tor-talk@lists.torproject.org
To unsubscribe or change other settings go to
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-talk

