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
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
|
Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193]
helo=mx.sourceforge.net)
by sfs-ml-2.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
(envelope-from <jrn@jrn.me.uk>) id 1YqR1T-0008Dr-3u
for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 18:59:51 +0000
X-ACL-Warn:
Received: from homie.mail.dreamhost.com ([208.97.132.208]
helo=homiemail-a9.g.dreamhost.com)
by sog-mx-3.v43.ch3.sourceforge.com with esmtp (Exim 4.76)
id 1YqR1R-0003pD-Op for bitcoin-development@lists.sourceforge.net;
Thu, 07 May 2015 18:59:51 +0000
Received: from homiemail-a9.g.dreamhost.com (localhost [127.0.0.1])
by homiemail-a9.g.dreamhost.com (Postfix) with ESMTP id 47030626070
for <bitcoin-development@lists.sourceforge.net>;
Thu, 7 May 2015 11:59:44 -0700 (PDT)
Received: from [192.168.0.6] (cpc12-cmbg17-2-0-cust830.5-4.cable.virginm.net
[86.30.131.63])
(using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits))
(No client certificate requested)
(Authenticated sender: jrn@jrn.me.uk)
by homiemail-a9.g.dreamhost.com (Postfix) with ESMTPSA id C84CE62606E
for <bitcoin-development@lists.sourceforge.net>;
Thu, 7 May 2015 11:59:43 -0700 (PDT)
Message-ID: <554BB61D.1040602@jrn.me.uk>
Date: Thu, 07 May 2015 19:59:41 +0100
From: Ross Nicoll <jrn@jrn.me.uk>
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64;
rv:31.0) Gecko/20100101 Thunderbird/31.6.0
MIME-Version: 1.0
To: bitcoin-development@lists.sourceforge.net
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> <CANEZrP3yM9wsSPNgpOsXDk-DjUy5PW2XuRTvK2AyCNbVJ5hZHw@mail.gmail.com> <CADJgMzti7ROH90APiwg4NOAT5+Av=4i295b8VN0sbSLr4+WWRw@mail.gmail.com>
<CAEieSeTafYjBCVUotLKBXX=Z3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gmail.com>
In-Reply-To: <CAEieSeTafYjBCVUotLKBXX=Z3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------030002080602000609090701"
X-Spam-Score: 0.9 (/)
X-Spam-Report: Spam Filtering performed by mx.sourceforge.net.
See http://spamassassin.org/tag/ for more details.
-0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at http://www.dnswl.org/,
no trust [208.97.132.208 listed in list.dnswl.org]
1.0 HTML_MESSAGE BODY: HTML included in message
-0.1 AWL AWL: Adjusted score from AWL reputation of From: address
X-Headers-End: 1YqR1R-0003pD-Op
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 18:59:51 -0000
This is a multi-part message in MIME format.
--------------030002080602000609090701
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
I'm presuming that schedule is just an example, as you'd end up with
insanely large block sizes in a few years.
Absolutely, yes, an increase schedule is an option if people agree on
it, and I think the better option, as the current limit too low, but
jumping straight to a value big enough for "indefinitely" is a huge jump.
Gave some thought to scaling block size based on transaction fees, but
suspect it would end up with miners sending huge fees to themselves with
transactions that aren't relayed (so they only are actioned if they make
it into a block that miner mines) to make the network allow bigger blocks.
Ross
On 07/05/2015 19:38, Chris Wardell wrote:
> Instead of raising the block size to another static number like 20MB,
> can we raise it dynamically?
>
> Make the max block size something like:
> pow(2, nHeight/100000) * 1MB; //double every ~2 years
>
>
>
> ------------------------------------------------------------------------------
> One dashboard for servers and applications across Physical-Virtual-Cloud
> Widest out-of-the-box monitoring support with 50+ applications
> Performance metrics, stats and reports that give you Actionable Insights
> Deep dive visibility with transaction tracing using APM Insight.
> http://ad.doubleclick.net/ddm/clk/290420510;117567292;y
>
>
> _______________________________________________
> Bitcoin-development mailing list
> Bitcoin-development@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/bitcoin-development
--------------030002080602000609090701
Content-Type: text/html; charset=windows-1252
Content-Transfer-Encoding: quoted-printable
<html>
<head>
<meta content=3D"text/html; charset=3Dwindows-1252"
http-equiv=3D"Content-Type">
</head>
<body bgcolor=3D"#FFFFFF" text=3D"#000000">
I'm presuming that schedule is just an example, as you'd end up with
insanely large block sizes in a few years.<br>
<br>
Absolutely, yes, an increase schedule is an option if people agree
on it, and I think the better option, as the current limit too low,
but jumping straight to a value big enough for "indefinitely" is a
huge jump.<br>
<br>
Gave some thought to scaling block size based on transaction fees,
but suspect it would end up with miners sending huge fees to
themselves with transactions that aren't relayed (so they only are
actioned if they make it into a block that miner mines) to make the
network allow bigger blocks.<br>
<br>
Ross<br>
<br>
<div class=3D"moz-cite-prefix">On 07/05/2015 19:38, Chris Wardell
wrote:<br>
</div>
<blockquote
cite=3D"mid:CAEieSeTafYjBCVUotLKBXX=3DZ3UHBKdi5kU5CFSxXJEmzCudQMg@mail.gm=
ail.com"
type=3D"cite">
<div dir=3D"ltr">
<div>
<div>
<div>Instead of raising the block size to another static
number like 20MB, can we raise it dynamically?<br>
<br>
</div>
Make the max block size something like:<br>
</div>
</div>
pow(2, nHeight/100000) * 1MB;=A0 //double every ~2 years<br>
<br>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">----------------------------------------------------=
--------------------------
One dashboard for servers and applications across Physical-Virtual-Cloud=20
Widest out-of-the-box monitoring support with 50+ applications
Performance metrics, stats and reports that give you Actionable Insights
Deep dive visibility with transaction tracing using APM Insight.
<a class=3D"moz-txt-link-freetext" href=3D"http://ad.doubleclick.net/ddm/=
clk/290420510;117567292;y">http://ad.doubleclick.net/ddm/clk/290420510;11=
7567292;y</a></pre>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">_______________________________________________
Bitcoin-development mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:Bitcoin-development@=
lists.sourceforge.net">Bitcoin-development@lists.sourceforge.net</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.sourceforge.net/=
lists/listinfo/bitcoin-development">https://lists.sourceforge.net/lists/l=
istinfo/bitcoin-development</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------030002080602000609090701--
|
