Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqNji-000097-GH for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 15:29:18 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.179 as permitted sender) client-ip=209.85.212.179; envelope-from=mh.in.england@gmail.com; helo=mail-wi0-f179.google.com; Received: from mail-wi0-f179.google.com ([209.85.212.179]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqNjg-0001Jh-MN for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 15:29:18 +0000 Received: by wief7 with SMTP id f7so16650971wie.0 for ; Thu, 07 May 2015 08:29:10 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.12.228 with SMTP id b4mr5994035wic.92.1431012550684; Thu, 07 May 2015 08:29:10 -0700 (PDT) Sender: mh.in.england@gmail.com Received: by 10.194.90.114 with HTTP; Thu, 7 May 2015 08:29:10 -0700 (PDT) In-Reply-To: References: <554A91BE.6060105@bluematt.me> Date: Thu, 7 May 2015 17:29:10 +0200 X-Google-Sender-Auth: UnkzP4ruiyg4kG0Ldy4RDitN7rQ Message-ID: From: Mike Hearn To: Jeff Garzik Content-Type: multipart/alternative; boundary=001a11c2a3a8c0b55505157f92de X-Spam-Score: -0.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 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (mh.in.england[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message 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: 1YqNjg-0001Jh-MN Cc: Bitcoin Dev Subject: Re: [Bitcoin-development] Block Size Increase 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: Thu, 07 May 2015 15:29:18 -0000 --001a11c2a3a8c0b55505157f92de Content-Type: text/plain; charset=UTF-8 > > It is a trivial *code* change. It is not a trivial change to the > economics of a $3.2B system. > Hmm - again I'd argue the opposite. Up until now Bitcoin has been unconstrained by the hard block size limit. If we raise it, Bitcoin will continue to be unconstrained by it. That's the default "continue as we are" position. If it's not raised, then ....... well, then we're in new territory entirely. Businesses built on the assumption that Bitcoin could become popular will suddenly have their basic assumptions invalidated. Users will leave. The technical code change would be zero, but the economic change would be significant. --001a11c2a3a8c0b55505157f92de Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
It is a trivial code change.=C2=A0 It is= not a trivial change to the economics of a $3.2B system.
=

Hmm - again I'd argue the opposi= te.

Up until now Bitcoin has been unconstrained by= the hard block size limit.

If we raise it, Bitcoi= n will continue to be unconstrained by it. That's the default "con= tinue as we are" position.

If it's not ra= ised, then ....... well, then we're in new territory entirely. Business= es built on the assumption that Bitcoin could become popular will suddenly = have their basic assumptions invalidated. Users will leave. The technical c= ode change would be zero, but the economic change would be significant.
--001a11c2a3a8c0b55505157f92de--