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
|
Return-Path: <pete@petertodd.org>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 52518273
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 20:54:29 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from outmail148098.authsmtp.com (outmail148098.authsmtp.com
[62.13.148.98])
by smtp1.linuxfoundation.org (Postfix) with ESMTP id BB174E7
for <bitcoin-dev@lists.linuxfoundation.org>;
Mon, 22 Jun 2015 20:54:28 +0000 (UTC)
Received: from mail-c235.authsmtp.com (mail-c235.authsmtp.com [62.13.128.235])
by punt17.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5MKsOoR004731;
Mon, 22 Jun 2015 21:54:24 +0100 (BST)
Received: from savin.petertodd.org (75-119-251-161.dsl.teksavvy.com
[75.119.251.161]) (authenticated bits=128)
by mail.authsmtp.com (8.14.2/8.14.2/) with ESMTP id t5MKsLcJ002948
(version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NO);
Mon, 22 Jun 2015 21:54:23 +0100 (BST)
Date: Mon, 22 Jun 2015 16:54:21 -0400
From: Peter Todd <pete@petertodd.org>
To: Jean-Paul Kogelman <jeanpaulkogelman@me.com>
Message-ID: <20150622205420.GA8892@savin.petertodd.org>
References: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha256;
protocol="application/pgp-signature"; boundary="tThc/1wpZn/ma/RB"
Content-Disposition: inline
In-Reply-To: <dd09d1e5-57fb-46ef-8bc0-0fdccf9e7abb@me.com>
User-Agent: Mutt/1.5.21 (2010-09-15)
X-Server-Quench: dd151da0-1920-11e5-b396-002590a15da7
X-AuthReport-Spam: If SPAM / abuse - report it at:
http://www.authsmtp.com/abuse
X-AuthRoute: OCd2Yg0TA1ZNQRgX IjsJECJaVQIpKltL GxAVKBZePFsRUQkR
aQdMdAAUEkAaAgsB AmMbWVVeVVl7W2c7 bA9PbARUfEhLXhtr
VklWR1pVCwQmRRl8 fV1iAWNydwdPfHY+ ZEdgXHAVCBB7cEcp
E05JFGQEZXphaTUa TRJbfgVJcANIexZF O1F6ACIKLwdSbGoL
FQ4vNDcwO3BTJTpg Ci0XJFwOCWwqJnZu Dx4DDTgjWFYORyg/
MhgrYlQYG00Sel4z I1ZpWFQTKRIbEQA2
X-Authentic-SMTP: 61633532353630.1023:706
X-AuthFastPath: 0 (Was 255)
X-AuthSMTP-Origin: 75.119.251.161/587
X-AuthVirus-Status: No virus detected - but ensure you scan with your own
anti-virus system.
X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_LOW
autolearn=ham version=3.3.1
X-Spam-Checker-Version: SpamAssassin 3.3.1 (2010-03-16) on
smtp1.linux-foundation.org
Cc: bitcoin-dev@lists.linuxfoundation.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 20:54:29 -0000
--tThc/1wpZn/ma/RB
Content-Type: text/plain; charset=iso-8859-1
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable
On Mon, Jun 22, 2015 at 07:32:22PM +0000, Jean-Paul Kogelman wrote:
>=20
>=20
> On Jun 22, 2015, at 11:18 AM, Gavin Andresen <gavinandresen@gmail.com> wr=
ote:
>=20
> The maximum size shall be 8,000,000 bytes at a timestamp of 2016-01-11 00=
:00:00 UTC (timestamp 1452470400), and shall double every 63,072,000 second=
s (two years, ignoring leap years), until 2036-01-06 00:00:00 UTC (timestam=
p 2083190400). The maximum size of blocks in between doublings will increas=
e linearly based on the block's timestamp. The maximum size of blocks after=
2036-01-06 00:00:00 UTC shall be 8,192,000,000 bytes.
> =A0
> Since it's possible that block timestamps aren't chronological in order, =
what would happen if a block following a size increase trigger is back in t=
he past before the size increase? Would that block have a lower size restri=
ction again? Would using block height not be a more stable number to work w=
ith?
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.
--=20
'peter'[:-1]@petertodd.org
0000000000000000138b2613c026e0ed1dbf6f8f193f1c3115bdf540dc22fbf6
--tThc/1wpZn/ma/RB
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
-----BEGIN PGP SIGNATURE-----
iQGrBAEBCACVBQJViHX4XhSAAAAAABUAQGJsb2NraGFzaEBiaXRjb2luLm9yZzAw
MDAwMDAwMDAwMDAwMDAxMzhiMjYxM2MwMjZlMGVkMWRiZjZmOGYxOTNmMWMzMTE1
YmRmNTQwZGMyMmZiZjYvFIAAAAAAFQARcGthLWFkZHJlc3NAZ251cGcub3JncGV0
ZUBwZXRlcnRvZC5vcmcACgkQJIFAPaXwkfvbHggAksxGsQfw/1AfNS+6pXBnbN1F
shxxH7cZ44H9eozwmcUxrZp4n2MEZcCXpxewVvF19Hl/w+zzp6Vps0x0g93L4QUF
OdNhJLG9lueX2OoH1QHEE0BaRd52E7IxQ2x06c6mHwpNiFdPWZDipgy9Z1THHuDr
04Uey+Zwl7p7kyCl6DG5QpMxUJIWzwcpOmi7S0erz3jvpow7Ig2mqehKlOz0Dwk/
JLPjxnSzb7lnm1R54j48hF8s507TWFWLXKCmPfKZTNXa92ps63+apcAl7ocq0pBH
1TUKV+Ns1fv81yKr1y0RjrbwnjfdP4iu1dzGKVYwDLmjTAdC55big4Q9WEuKDg==
=pX9a
-----END PGP SIGNATURE-----
--tThc/1wpZn/ma/RB--
|
