Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YyKyU-0005hv-JE for bitcoin-development@lists.sourceforge.net; Fri, 29 May 2015 14:09:26 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.178 as permitted sender) client-ip=209.85.216.178; envelope-from=tier.nolan@gmail.com; helo=mail-qc0-f178.google.com; Received: from mail-qc0-f178.google.com ([209.85.216.178]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YyKyT-00070t-Pb for bitcoin-development@lists.sourceforge.net; Fri, 29 May 2015 14:09:26 +0000 Received: by qcxw10 with SMTP id w10so26389677qcx.3 for ; Fri, 29 May 2015 07:09:20 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.140.132.17 with SMTP id 17mr10444358qhe.36.1432908560347; Fri, 29 May 2015 07:09:20 -0700 (PDT) Received: by 10.140.85.241 with HTTP; Fri, 29 May 2015 07:09:20 -0700 (PDT) In-Reply-To: References: <16096345.A1MpJQQkRW@crushinator> Date: Fri, 29 May 2015 15:09:20 +0100 Message-ID: From: Tier Nolan Cc: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c07c72bc38ab0517390518 X-Spam-Score: 3.3 (+++) 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 (tier.nolan[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.2 MISSING_HEADERS Missing To: header 1.0 HTML_MESSAGE BODY: HTML included in message -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 2.7 MALFORMED_FREEMAIL Bad headers on message from free email service -0.0 AWL AWL: Adjusted score from AWL reputation of From: address X-Headers-End: 1YyKyT-00070t-Pb Subject: Re: [Bitcoin-development] Proposed alternatives to the 20MB step function 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: Fri, 29 May 2015 14:09:26 -0000 --001a11c07c72bc38ab0517390518 Content-Type: text/plain; charset=UTF-8 On Fri, May 29, 2015 at 1:39 PM, Gavin Andresen wrote: > But if there is still no consensus among developers but the "bigger blocks > now" movement is successful, I'll ask for help getting big miners to do the > same, and use the soft-fork block version voting mechanism to (hopefully) > get a majority and then a super-majority willing to produce bigger blocks. > The purpose of that process is to prove to any doubters that they'd better > start supporting bigger blocks or they'll be left behind, and to give them > a chance to upgrade before that happens. > How do you define that the movement is successful? For > Because if we can't come to consensus here, the ultimate authority for > determining consensus is what code the majority of merchants and exchanges > and miners are running. > The measure is miner consensus. How do you intend to measure exchange/merchant acceptance? --001a11c07c72bc38ab0517390518 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable


On Fri, May 29, 2015 at 1:39 PM, Gavin Andresen <<= a href=3D"mailto:gavinandresen@gmail.com" target=3D"_blank">gavinandresen@g= mail.com> wrote:
But if there is still no consensus among developer= s but the "bigger blocks now" movement is successful, I'll as= k for help getting big miners to do the same, and use the soft-fork block v= ersion voting mechanism to (hopefully) get a majority and then a super-majo= rity willing to produce bigger blocks. The purpose of that process is to pr= ove to any doubters that they'd better start supporting bigger blocks o= r they'll be left behind, and to give them a chance to upgrade before t= hat happens.

How do you define = that the movement is successful?

For
=C2=A0
Because if we can't come to consensus here, the ultimate authori= ty for determining consensus is what code the majority of merchants and exc= hanges and miners are running.

= The measure is miner consensus.=C2=A0 How do you intend to measure exchange= /merchant acceptance?
--001a11c07c72bc38ab0517390518--