1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
|
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 <gavinandresen@gmail.com>) 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 <bitcoin-development@lists.sourceforge.net>;
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: <CABsx9T2vAQyZODRE9apu0R1n=LybssQcuTYD7P3mAQH_Fv6QCQ@mail.gmail.com>
References: <554A91BE.6060105@bluematt.me>
<CANEZrP3wGWHdz+ut6pvke5TJJsc1rTFt8sn2KziX35oL5LAsyg@mail.gmail.com>
<CABm2gDpDvk2VsQ+mJ-BoeBKmvu9jBXNujZEFKuCStRNjFL6VOA@mail.gmail.com>
<CANEZrP2zAGCCBhNa4=9yw+A_Dn5o4SQXoPTE_qcJzZ1dFuF2tw@mail.gmail.com>
<CABm2gDqd6iHRUDKZWWTudcC1QkYa+rCuHjz7pMC2K1Db8wpgfA@mail.gmail.com>
<CANEZrP1CU0kB0vXeXUX1L8byaT-Zf2xg+3N+GeNthi_i6bn1qw@mail.gmail.com>
<CABsx9T2Nxvr4fqREMw3_LXftzsxrUAR1+9sVMa8_EpTnH1nN1Q@mail.gmail.com>
<554BA032.4040405@bluematt.me>
<CABsx9T2vAQyZODRE9apu0R1n=LybssQcuTYD7P3mAQH_Fv6QCQ@mail.gmail.com>
Date: Thu, 7 May 2015 13:40:59 -0400
Message-ID: <CABsx9T1mnVjtpC4pnHPBwQQYLktiSABKrTzco7TbnAtZ4Bmj0w@mail.gmail.com>
From: Gavin Andresen <gavinandresen@gmail.com>
To: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
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: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
<mailto:bitcoin-development-request@lists.sourceforge.net?subject=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 <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."
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
<div dir=3D"ltr"><div class=3D"gmail_quote"><div dir=3D"ltr"><div class=3D"=
gmail_extra"><div class=3D"gmail_quote">On Thu, May 7, 2015 at 1:26 PM, Mat=
t Corallo <span dir=3D"ltr"><<a href=3D"mailto:bitcoin-list@bluematt.me"=
target=3D"_blank">bitcoin-list@bluematt.me</a>></span> wrote:<br></div>=
<div class=3D"gmail_quote"><span class=3D""><blockquote class=3D"gmail_quot=
e" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">=
I think this is a huge issue. You've been wandering around telling<br>
people that the blocksize will increase soon for months</blockquote><div><b=
r></div></span><div>I think the strongest thing I've ever said is:</div=
><div><br></div><div>"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."</div><div><br></div><div>Th=
is is what "I will be pushing to change it this year" looks like.=
</div></div></div></div></div><div><br></div>-- <br><div class=3D"gmail_sig=
nature">--<br>Gavin Andresen<br></div>
</div>
--089e0149424824c7290515816ae9--
|
