To that end, I setup a bitcoin node that listens on the v4/v6 internet as well as tor.
The hidden service address is dsyadrvivtt34s26.onion Could some folks please test this for me and make sure it works for others? I can see it is quite happily running on v4/v6 (and getting traffic) but its' less obvious that it is working over tor. On Mon, Oct 27, 2014 at 3:03 PM, Thomas White <thomaswh...@riseup.net> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > 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+to...@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. > > > > - -- > Fingerprint: 9DB0 082F 8FE2 E691 DA2A 6D03 4DAE 4226 9EB0 EB0B > Fingerprint: FAA4 2253 AA4B 38D0 1BC4 085E F688 CEF6 F9BF D57F > OTR IRC: DF63021D 27973EAA 02FA4DF6 9E52C9E0 8821E0EF > OTR XMPP: 77DB65BC C417C4DD 19F9664D 83D6D3FB 6C3D3A0E > > Twitter: https://twitter.com/CthulhuSec > > Not familiar with PGP? Get started today: > http://www.bitcoinnotbombs.com/beginners-guide-to-pgp/ > -----BEGIN PGP SIGNATURE----- > Version: GnuPG v2.0.22 (MingW32) > > iQIcBAEBAgAGBQJUTqUCAAoJEE2uQiaesOsL23QQAJG4XGhiMRCtAMhb6dbq9jHo > OZ5CPysEkXwMSK6dTwpCm9GuMHloK3Dq+CzKa6dDeBmEVslWxbXtsx0by0pDjJbS > I7tiIpjHrCJTrKgDbPQWJP3yZQ8W+fu3JYW+OxZxbrRXEvrX9vgD2pF3zVn2vb76 > n5LEtlmR8rMCC5JAq2tjFY7665xMkloYXay/VE7E2d9eZ5W1/4V1nHcm5cn7RTix > PxDvD6FAJCNAH7F5rGoGHzC9V9mPAatBfV5S/3Ya49PRtM70tWWBJD/L3KrB71k0 > F7P5eNrfL7gOgFgAIJ1FWuJH7Ri9kCyntsLSgEZBSwYeHEACfFL2qGO1IEw1qRCj > nxopXSMCNBQu8XP1568ha6KPyKLOTD0kVehE3tgVizabRMTwkuXqiUslbMCRthwy > y7WmPAaVgEYnGhIhnRHnf/G0tbfsBcInIyCrBuqfJfLnVfx7IPMDP52JLIg71tyM > RamPUNIv840HkpvTlYwTVIRwL5hFpeW327hxhcnkWFi0mUwb12Lr+N7BlB3aQGE9 > bVmqS4oq1qb6y0TTUlcEg42CDs9GpdVB3Amdcm9Y5scE6upDq+J9yO6322eh82Kq > qlJK1mnVHMyf3ZGS0ItqGuu54SjiB4kzVt4FV2einjYu4gXT+WiMRCmx1Hzk2hgO > t6iZ3nLBtWK19kpt4UVD > =jdgx > -----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 > -- 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
