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
113
114
115
116
|
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 <mh.in.england@gmail.com>) id 1YqPph-0004xg-5h
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 17:43:37 +0000
Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.212.171 as permitted sender)
client-ip=209.85.212.171; envelope-from=mh.in.england@gmail.com;
helo=mail-wi0-f171.google.com;
Received: from mail-wi0-f171.google.com ([209.85.212.171])
by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1YqPpg-0005c5-9c
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 17:43:37 +0000
Received: by wief7 with SMTP id f7so19337563wie.0
for <bitcoin-development@lists.sourceforge.net>;
Thu, 07 May 2015 10:43:30 -0700 (PDT)
MIME-Version: 1.0
X-Received: by 10.194.48.101 with SMTP id k5mr9545602wjn.79.1431020610310;
Thu, 07 May 2015 10:43:30 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.194.90.114 with HTTP; Thu, 7 May 2015 10:43:30 -0700 (PDT)
In-Reply-To: <554BA032.4040405@bluematt.me>
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>
Date: Thu, 7 May 2015 19:43:30 +0200
X-Google-Sender-Auth: Q6Vj4mtxQCev2DcV6uYgUZ0bfJo
Message-ID: <CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: Matt Corallo <bitcoin-list@bluematt.me>
Content-Type: multipart/alternative; boundary=047d7ba9791c24d7990515817337
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: 1YqPpg-0005c5-9c
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] 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:43:37 -0000
--047d7ba9791c24d7990515817337
Content-Type: text/plain; charset=UTF-8
> The only answer to this that anyone with a clue should give is "it
> will very, very likely be able to support at least 1MB blocks roughly
> every 10 minutes on average for the next eleven years, and it seems
> likely that a block size increase of some form will happen at some point in
> the next eleven years", anything else is dishonest.
Matt, you know better than that. Gavin neither lacks clue nor is he
dishonest.
He has been working on the assumption that other developers are reasonable,
and some kind of compromise solution can be found that everyone can live
with. Hence trying to find a middle ground, hence considering and writing
articles in response to every single objection raised. Hence asking for
suggestions on what to change about the plan, to make it more acceptable.
What more do you want, exactly?
And I'll ask again. Do you have a *specific, credible alternative*? Because
so far I'm not seeing one.
--047d7ba9791c24d7990515817337
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><div=
>=C2=A0=C2=A0</div><blockquote class=3D"gmail_quote" style=3D"margin:0 0 0 =
.8ex;border-left:1px #ccc solid;padding-left:1ex">The=C2=A0only answer to t=
his that anyone with a clue should give is "it will=C2=A0very, very li=
kely be able to support at least 1MB blocks roughly every=C2=A010 minutes o=
n average for the next eleven years, and it seems likely=C2=A0that a block =
size increase of some form will happen at some point in the=C2=A0next eleve=
n years", anything else is dishonest.</blockquote></div></div><div cla=
ss=3D"gmail_extra"><br></div><div class=3D"gmail_extra">Matt, you know bett=
er than that. Gavin neither lacks clue nor is he dishonest.=C2=A0</div><div=
class=3D"gmail_extra"><br></div><div class=3D"gmail_extra">He has been wor=
king on the assumption that other developers are reasonable, and some kind =
of compromise solution can be found that everyone can live with. Hence tryi=
ng to find a middle ground, hence considering and writing articles in respo=
nse to every single objection raised. Hence asking for suggestions on what =
to change about the plan, to make it more acceptable. What more do you want=
, exactly?</div><div class=3D"gmail_extra"><br></div><div class=3D"gmail_ex=
tra">And I'll ask again. Do you have a <b>specific, credible alternativ=
e</b>? Because so far I'm not seeing one.</div></div>
--047d7ba9791c24d7990515817337--
|
