Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VdYQA-00009q-Ls for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 04:39:18 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of petertodd.org designates 62.13.149.115 as permitted sender) client-ip=62.13.149.115; envelope-from=pete@petertodd.org; helo=outmail149115.authsmtp.co.uk; Received: from outmail149115.authsmtp.co.uk ([62.13.149.115]) by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76) id 1VdYQ9-0006HO-De for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 04:39:18 +0000 Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235]) by punt12.authsmtp.com (8.14.2/8.14.2) with ESMTP id rA54dBsC038516; Tue, 5 Nov 2013 04:39:11 GMT Received: from petertodd.org (petertodd.org [174.129.28.249]) (authenticated bits=128) by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id rA54d5fB064725 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO); Tue, 5 Nov 2013 04:39:08 GMT Date: Mon, 4 Nov 2013 23:39:05 -0500 From: Peter Todd To: Gustaw Wieczorek Message-ID: <20131105043905.GA7552@petertodd.org> References: <1383624877.65922.YahooMailNeo@web120504.mail.ne1.yahoo.com> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="EVF5PPMfhYS0aIcm" Content-Disposition: inline In-Reply-To: <1383624877.65922.YahooMailNeo@web120504.mail.ne1.yahoo.com> User-Agent: Mutt/1.5.21 (2010-09-15) X-Server-Quench: 35c8bfd0-45d4-11e3-b802-002590a15da7 X-AuthReport-Spam: If SPAM / abuse - report it at: http://www.authsmtp.com/abuse X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR aAdMdgcUFloCAgsB AmUbW1BeU1R7WWs7 ag1VcwRfa1RMVxto VEFWR1pVCwQmQ20E AkobBGtycQFBens+ Yk9qWD5YWRdyJxAp QlNQEDkCeGZhPWMC AkhYdR5UcAFPdx8U a1UrBXRDAzANdhES HhM4ODE3eDlSNilR RRkIIFQOdA4iAyI7 Ah8PGzg1FFEIS202 LhorMBYWFU0SOEI0 PDMA X-Authentic-SMTP: 61633532353630.1023:706 X-AuthFastPath: 0 (Was 255) X-AuthSMTP-Origin: 174.129.28.249/587 X-AuthVirus-Status: No virus detected - but ensure you scan with your own anti-virus system. X-Spam-Score: -1.5 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain -0.0 SPF_PASS SPF: sender matches SPF record 0.0 URIBL_BLOCKED ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [URIs: petertodd.org] X-Headers-End: 1VdYQ9-0006HO-De Cc: "bitcoin-development@lists.sourceforge.net" Subject: Re: [Bitcoin-development] Auto-generated miner backbone X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Tue, 05 Nov 2013 04:39:18 -0000 --EVF5PPMfhYS0aIcm Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Mon, Nov 04, 2013 at 08:14:37PM -0800, Gustaw Wieczorek wrote: > Mike Hearn wrote: >=20 > > how about if we wrote code to automatically build a miner backbone >=20 > Yeah, let's build a backbone, or a cloud, and then we could have Google r= un it! >=20 > Come on, Mike, your conflict-of-interest as an employee is hanging out in= the open, flapping in the breeze here...=A0 Don't you think it's a bit obv= ious for somebody in your position to advocate centralization of infrastruc= ture, especially when it comes to bitcoin? >=20 >=20 > On the other hand, I guess your blind trust in IP addresses as a solid fo= undation for security is why you were so shocked when the NSA hacked your "= backbone". Go away. Mike specifically mentioned the idea of using Tor addresses, which are authenticated. In addition this mechanism to create a backbone *automatically* is exactly as decentralized as Bitcoin mining itself is. It has nothing to do with Google. I suggested the mechanism myself for slightly different reasons, and if you know me, you'd know I'm the first to jump on anyone pushing centralization. --=20 'peter'[:-1]@petertodd.org 000000000000000517064a43348fa39325bdc244ffb1d0da11ab85676d494a85 --EVF5PPMfhYS0aIcm Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) iQEcBAEBCAAGBQJSeHZpAAoJEBmcgzuo5/CFaqwIAIjwMFDO1UmIr/wds7IdMVcv bnYv/IvbrQsdGgZPEUotOgPCVyAEM1DU25S6j8V3XuBW0qpoTaFwxURQoGFJnOXf fejvzpR9FArJOtn1MWmffRRXOAvfYi01rnYhV3oJxCK9NpssyEm2FkAWZ1sBqgLP tV+LllvnC1bL1/oKO4u3bJ8L8Zis4yPEL+RMhYnEd/58SsUs0b6dusscDu4RSQtX jhdChw+tWwFhAjDzWyY4k9CbT5rZhoPDFv4WZRoEkkrR4RzizUOMs5ldl0vtF2kQ NaCdFMD07VOnlKnxpZcPkABjsIjdOAybBfUlGIKdwQveuZUPrWLR6+cj2jfqptk= =fNhT -----END PGP SIGNATURE----- --EVF5PPMfhYS0aIcm--