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
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <brianchoffman@gmail.com>) id 1Yypzo-0000hi-RN
for bitcoin-development@lists.sourceforge.net;
Sat, 30 May 2015 23:16:52 +0000
Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
designates 209.85.192.44 as permitted sender)
client-ip=209.85.192.44; envelope-from=brianchoffman@gmail.com;
helo=mail-qg0-f44.google.com;
Received: from mail-qg0-f44.google.com ([209.85.192.44])
by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
(Exim 4.76) id 1Yypzn-00014H-SU
for bitcoin-development@lists.sourceforge.net;
Sat, 30 May 2015 23:16:52 +0000
Received: by qgfa63 with SMTP id a63so39482102qgf.0
for <bitcoin-development@lists.sourceforge.net>;
Sat, 30 May 2015 16:16:46 -0700 (PDT)
X-Received: by 10.229.48.200 with SMTP id s8mr17841830qcf.0.1433027806409;
Sat, 30 May 2015 16:16:46 -0700 (PDT)
Received: from [10.126.96.179] (mobile-166-171-057-242.mycingular.net.
[166.171.57.242])
by mx.google.com with ESMTPSA id 92sm1520728qgi.13.2015.05.30.16.16.44
(version=TLSv1 cipher=ECDHE-RSA-RC4-SHA bits=128/128);
Sat, 30 May 2015 16:16:44 -0700 (PDT)
Content-Type: multipart/alternative;
boundary=Apple-Mail-14DE21AB-D8E2-4396-8074-155E9FB89393
Mime-Version: 1.0 (1.0)
From: Brian Hoffman <brianchoffman@gmail.com>
X-Mailer: iPhone Mail (12F70)
In-Reply-To: <CAE28kUTSgrU0kY6zLHrZXAAP+XD2H=NqT8rE3jt6Cp+1qGkHRg@mail.gmail.com>
Date: Sat, 30 May 2015 19:16:42 -0400
Content-Transfer-Encoding: 7bit
Message-Id: <44570322-FBAE-4BAF-A0DA-2E478EF436B4@gmail.com>
References: <554BE0E1.5030001@bluematt.me>
<CAFzgq-xByQ1E_33_m3UpXQFUkGc78HKnA=7XXMshANDuTkNsvA@mail.gmail.com>
<CABsx9T0kbRe31LMwk499MQUw225f5GGd67GfhXBezHmDqxkioA@mail.gmail.com>
<CAE28kUTSgrU0kY6zLHrZXAAP+XD2H=NqT8rE3jt6Cp+1qGkHRg@mail.gmail.com>
To: Alex Mizrahi <alex.mizrahi@gmail.com>
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
(brianchoffman[at]gmail.com)
-0.0 SPF_PASS SPF: sender matches SPF record
1.0 HTML_MESSAGE BODY: HTML included in message
0.0 MIME_QP_LONG_LINE RAW: Quoted-printable line longer than 76 chars
-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: 1Yypzn-00014H-SU
Cc: Bitcoin Dev <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Block Size Increase Requirements
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: Sat, 30 May 2015 23:16:52 -0000
--Apple-Mail-14DE21AB-D8E2-4396-8074-155E9FB89393
Content-Type: text/plain;
charset=us-ascii
Content-Transfer-Encoding: quoted-printable
> Why 20 MB? Do you anticipate 20x transaction count growth in 2016?
Do you anticipate linear growth?
> On May 30, 2015, at 6:05 PM, Alex Mizrahi <alex.mizrahi@gmail.com> wrote:
>=20
> =20
>> Why 2 MB ?
>=20
> Why 20 MB? Do you anticipate 20x transaction count growth in 2016?
>=20
> Why not grow it by 1 MB per year?
> This is a safer option, I don't think that anybody claims that 2 MB blocks=
will be a problem.
> And in 10 years when we get to 10 MB we'll get more evidence as to whether=
network can handle 10 MB blocks.
>=20
> So this might be a solution which would satisfy both sides:
> * people who are concerned about block size growth will have an opportu=
nity to stop it before it grows too much (e.g. with a soft fork),
> * while people who want bigger blocks will get an equivalent of 25% per=
year growth within the first 10 years, which isn't bad, is it?
>=20
> So far I haven't heard any valid arguments against linear growth.
> --------------------------------------------------------------------------=
----
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--Apple-Mail-14DE21AB-D8E2-4396-8074-155E9FB89393
Content-Type: text/html;
charset=utf-8
Content-Transfer-Encoding: quoted-printable
<html><head><meta http-equiv=3D"content-type" content=3D"text/html; charset=3D=
utf-8"></head><body dir=3D"auto"><div><blockquote type=3D"cite"><div dir=3D"=
ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><font color=3D"#0=
00000"><span style=3D"background-color: rgba(255, 255, 255, 0);">Why 20 MB? D=
o you anticipate 20x transaction count growth in 2016?</span></font></div></=
div></div></blockquote></div><div><br></div><div>Do you anticipate linear gr=
owth?</div><div><br>On May 30, 2015, at 6:05 PM, Alex Mizrahi <<a href=3D=
"mailto:alex.mizrahi@gmail.com">alex.mizrahi@gmail.com</a>> wrote:<br><br=
></div><blockquote type=3D"cite"><div><div dir=3D"ltr"><div class=3D"gmail_e=
xtra"><div class=3D"gmail_quote"><div> </div><blockquote class=3D"gmail=
_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex"><div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote"><=
span class=3D""><div></div></span><div>Why 2 MB ?</div></div></div></div></b=
lockquote><div><br></div><div>Why 20 MB? Do you anticipate 20x transaction c=
ount growth in 2016?</div><div><br></div><div>Why not grow it by 1 MB per ye=
ar?</div><div>This is a safer option, I don't think that anybody claims that=
2 MB blocks will be a problem.</div><div>And in 10 years when we get to 10 M=
B we'll get more evidence as to whether network can handle 10 MB blocks.</di=
v><div><br></div><div>So this might be a solution which would satisfy both s=
ides:</div><div> * people who are concerned about block size gro=
wth will have an opportunity to stop it before it grows too much (e.g. with a=
soft fork),</div><div> * while people who want bigger blocks wi=
ll get an equivalent of 25% per year growth within the first 10 years, which=
isn't bad, is it?</div><div><br></div><div>So far I haven't heard any valid=
arguments against linear growth.</div></div></div></div>
</div></blockquote><blockquote type=3D"cite"><div><span>--------------------=
----------------------------------------------------------</span><br></div><=
/blockquote><blockquote type=3D"cite"><div><span>___________________________=
____________________</span><br><span>Bitcoin-development mailing list</span>=
<br><span><a href=3D"mailto:Bitcoin-development@lists.sourceforge.net">Bitco=
in-development@lists.sourceforge.net</a></span><br><span><a href=3D"https://=
lists.sourceforge.net/lists/listinfo/bitcoin-development">https://lists.sour=
ceforge.net/lists/listinfo/bitcoin-development</a></span><br></div></blockqu=
ote></body></html>=
--Apple-Mail-14DE21AB-D8E2-4396-8074-155E9FB89393--
|
