Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VdaGt-0004tk-7d for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 06:37:51 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.217.177 as permitted sender) client-ip=209.85.217.177; envelope-from=gmaxwell@gmail.com; helo=mail-lb0-f177.google.com; Received: from mail-lb0-f177.google.com ([209.85.217.177]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VdaGs-0002MT-Da for bitcoin-development@lists.sourceforge.net; Tue, 05 Nov 2013 06:37:51 +0000 Received: by mail-lb0-f177.google.com with SMTP id u14so6186761lbd.36 for ; Mon, 04 Nov 2013 22:37:43 -0800 (PST) MIME-Version: 1.0 X-Received: by 10.112.52.33 with SMTP id q1mr4450190lbo.30.1383633463640; Mon, 04 Nov 2013 22:37:43 -0800 (PST) Received: by 10.112.63.164 with HTTP; Mon, 4 Nov 2013 22:37:43 -0800 (PST) In-Reply-To: <20131105043905.GA7552@petertodd.org> References: <1383624877.65922.YahooMailNeo@web120504.mail.ne1.yahoo.com> <20131105043905.GA7552@petertodd.org> Date: Mon, 4 Nov 2013 22:37:43 -0800 Message-ID: From: Gregory Maxwell To: Peter Todd Content-Type: text/plain; charset=UTF-8 X-Spam-Score: -1.6 (-) 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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -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] -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VdaGs-0002MT-Da 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 06:37:51 -0000 On Mon, Nov 4, 2013 at 8:39 PM, Peter Todd wrote: > 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. Likewise, I did too and am also not very tolerant with "trusted" or "centeralized" things in general. An authenticated miner announced set of nodes is _far_ from a cure all, as any attack they stop can be recovered by adding "and dos attacks the public miner announced nodes" to the attack's requirements... but we build security with layers. Bitcoin's security is only improved when we can weave the network tighter and make partitioning it more difficult.