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
|
Return-Path: <jrn@jrn.me.uk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id B289583D
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 21:32:13 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from hapkido.dreamhost.com (hapkido.dreamhost.com [66.33.216.122])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id 2B11B153
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 21:32:13 +0000 (UTC)
Received: from homiemail-a4.g.dreamhost.com (homie.mail.dreamhost.com
[208.97.132.208])
by hapkido.dreamhost.com (Postfix) with ESMTP id 8E6BF9E7C4
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 14:32:12 -0700 (PDT)
Received: from homiemail-a4.g.dreamhost.com (localhost [127.0.0.1])
by homiemail-a4.g.dreamhost.com (Postfix) with ESMTP id B4F2C51C080
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 14:32:11 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=jrn.me.uk; h=subject:to
:references:from:message-id:date:mime-version:in-reply-to:
content-type; s=jrn.me.uk; bh=bBmJ+nJ56Bw5visETpTUhgbb/UM=; b=fn
nid7ofgyvMWKutuP0tr6RGOaktVq4giOs+nqJy7tRpsWzZPwsqTynWeH9jxV2wr4
pzBu+RnB8vO7+TqyWlDZswga7D14ZeRtDQXdD5RcCScSMOijigOMRZfnPHwABITE
It2D1vJy5jccnt0O0N9vk/zdJpG1HitoVDSX+s+n8=
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-a4.g.dreamhost.com (Postfix) with ESMTPSA id 54A1051C074
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 14:32:11 -0700 (PDT)
To: bitcoin-dev@lists.linuxfoundation.org
References: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
<20150622205420.GA8892@savin.petertodd.org>
<CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmail.com>
From: Ross Nicoll <jrn@jrn.me.uk>
Message-ID: <55887EDF.3070505@jrn.me.uk>
Date: Mon, 22 Jun 2015 22:32:15 +0100
User-Agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.0.1
MIME-Version: 1.0
In-Reply-To: <CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmail.com>
Content-Type: multipart/alternative;
boundary="------------070401020302090605090002"
X-Spam-Status: No, score=-2.0 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID, DKIM_VALID_AU, HTML_MESSAGE,
RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Subject: Re: [bitcoin-dev] Draft BIP : fixed-schedule block size increase
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Development Discussion <bitcoin-dev.lists.linuxfoundation.org>
List-Unsubscribe: <https://lists.linuxfoundation.org/mailman/options/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=unsubscribe>
List-Archive: <http://lists.linuxfoundation.org/pipermail/bitcoin-dev/>
List-Post: <mailto:bitcoin-dev@lists.linuxfoundation.org>
List-Help: <mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=help>
List-Subscribe: <https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev>,
<mailto:bitcoin-dev-request@lists.linuxfoundation.org?subject=subscribe>
X-List-Received-Date: Mon, 22 Jun 2015 21:32:13 -0000
This is a multi-part message in MIME format.
--------------070401020302090605090002
Content-Type: text/plain; charset=windows-1252; format=flowed
Content-Transfer-Encoding: 7bit
Potentially daft question, why not use a minimum height? Yes, it's
imprecise, but over an extended period of time they're good enough IMHO.
I'd have to do more careful calculations to confirm, but block 388,000
should be about right as a minimum.
Ross
On 22/06/2015 22:04, Stephen Morse wrote:
>
> In the nVersion bits proposal that I co-authored we solved that
> issue by
> comparing the timestamp against the median time, which is
> guaranteed by
> the protocol rules to monotonically advance.
>
>
> I'm also a fan of using the median time to ensure that there is a
> clear point where the protocol change starts. Something like "blocks
> only allow the larger block size if the associate pindex has
> pindex->GetMedianTimePast() after midnight 11 Jan 2016 and where a
> supermajority showing support for the fork has previously been reached".
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
--------------070401020302090605090002
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">
Potentially daft question, why not use a minimum height? Yes, it's
imprecise, but over an extended period of time they're good enough
IMHO.<br>
<br>
I'd have to do more careful calculations to confirm, but block
388,000 should be about right as a minimum.<br>
<br>
Ross<br>
<br>
<div class=3D"moz-cite-prefix">On 22/06/2015 22:04, Stephen Morse
wrote:<br>
</div>
<blockquote
cite=3D"mid:CABHVRKQoHERWSLwF-885jis9PqV07qYEJrScxwxfePwv0C9EoQ@mail.gmai=
l.com"
type=3D"cite">
<div dir=3D"ltr">
<div class=3D"gmail_extra">
<div class=3D"gmail_quote"><br>
<blockquote class=3D"gmail_quote" style=3D"margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-lef=
t-style:solid;padding-left:1ex">
<div class=3D"">
<div class=3D"h5"><span style=3D"color:rgb(34,34,34)">In =
the
nVersion bits proposal that I co-authored we solved
that issue by</span><br>
</div>
</div>
comparing the timestamp against the median time, which is
guaranteed by<br>
the protocol rules to monotonically advance.<br>
</blockquote>
<div><br>
</div>
<div>I'm also a fan of using the median time to ensure that
there is a clear point where the protocol change starts.
Something like "blocks only allow the larger block size if
the associate=A0<font face=3D"monospace, monospace">pindex<=
/font>=A0has=A0<font
face=3D"monospace, monospace">pindex->GetMedianTimePas=
t(</font>)
after=A0midnight 11 Jan 2016 and where a supermajority
showing support for the fork has previously been
reached".=A0</div>
</div>
</div>
</div>
<br>
<fieldset class=3D"mimeAttachmentHeader"></fieldset>
<br>
<pre wrap=3D"">_______________________________________________
bitcoin-dev mailing list
<a class=3D"moz-txt-link-abbreviated" href=3D"mailto:bitcoin-dev@lists.li=
nuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</a>
<a class=3D"moz-txt-link-freetext" href=3D"https://lists.linuxfoundation.=
org/mailman/listinfo/bitcoin-dev">https://lists.linuxfoundation.org/mailm=
an/listinfo/bitcoin-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>
--------------070401020302090605090002--
|
