From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-1.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1YqPnG-0004ly-Fc for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 17:41:06 +0000 Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.50 as permitted sender) client-ip=209.85.215.50; envelope-from=gavinandresen@gmail.com; helo=mail-la0-f50.google.com; Received: from mail-la0-f50.google.com ([209.85.215.50]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1YqPnF-0005Wa-LF for bitcoin-development@lists.sourceforge.net; Thu, 07 May 2015 17:41:06 +0000 Received: by lagv1 with SMTP id v1so36036399lag.3 for ; Thu, 07 May 2015 10:40:59 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.152.4.72 with SMTP id i8mr4101759lai.32.1431020459311; Thu, 07 May 2015 10:40:59 -0700 (PDT) Received: by 10.25.90.75 with HTTP; Thu, 7 May 2015 10:40:59 -0700 (PDT) In-Reply-To: References: <554A91BE.6060105@bluematt.me> <554BA032.4040405@bluematt.me> Date: Thu, 7 May 2015 13:40:59 -0400 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=089e0149424824c7290515816ae9 X-Spam-Score: -0.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 (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 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 X-Headers-End: 1YqPnF-0005Wa-LF Subject: [Bitcoin-development] Fwd: 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 17:41:06 -0000 --089e0149424824c7290515816ae9 Content-Type: text/plain; charset=UTF-8 On Thu, May 7, 2015 at 1:26 PM, Matt Corallo wrote: > I think this is a huge issue. You've been wandering around telling > people that the blocksize will increase soon for months I think the strongest thing I've ever said is: "There is consensus that the max block size much change sooner or later. There is not yet consensus on exactly how or when. I will be pushing to change it this year." This is what "I will be pushing to change it this year" looks like. -- -- Gavin Andresen --089e0149424824c7290515816ae9 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
On Thu, May 7, 2015 at 1:26 PM, Mat= t Corallo <bitcoin-list@bluematt.me> wrote:
=
= I think this is a huge issue. You've been wandering around telling
people that the blocksize will increase soon for months
I think the strongest thing I've ever said is:

"There is consensus that the max block size much = change sooner or later. There is not yet consensus on exactly how or when. = I will be pushing to change it this year."

Th= is is what "I will be pushing to change it this year" looks like.=

--
--
Gavin Andresen
--089e0149424824c7290515816ae9--