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
|
Return-Path: <jl2012@xbt.hk>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id D6F8F89C
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 29 Mar 2017 04:21:41 +0000 (UTC)
X-Greylist: from auto-whitelisted by SQLgrey-1.7.6
Received: from sender-of-o52.zoho.com (sender-of-o52.zoho.com [135.84.80.217])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id DF675161
for <bitcoin-dev@lists.linuxfoundation.org>;
Wed, 29 Mar 2017 04:21:40 +0000 (UTC)
Received: from [192.168.1.111] (137.189.135.19 [137.189.135.19]) by
mx.zohomail.com with SMTPS id 1490761297585964.0486404973495;
Tue, 28 Mar 2017 21:21:37 -0700 (PDT)
From: Johnson Lau <jl2012@xbt.hk>
Message-Id: <A6898D1C-B221-4363-8F34-76744F4E9722@xbt.hk>
Content-Type: multipart/alternative;
boundary="Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3"
Mime-Version: 1.0 (Mac OS X Mail 10.2 \(3259\))
Date: Wed, 29 Mar 2017 12:21:33 +0800
In-Reply-To: <1526531.K1h7bgEXcQ@cherry>
To: Tom Zander <tomz@freedommail.ch>
References: <CAFzgq-xizPMNqfvW11nUhd6HmfZu8aGjcR9fshEsf6o5HOt_dA@mail.gmail.com>
<B93DE8AA-AA01-4E0E-88B6-B788B03282E0@xbt.hk>
<1526531.K1h7bgEXcQ@cherry>
X-Mailer: Apple Mail (2.3259)
X-ZohoMailClient: External
X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,HTML_MESSAGE
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 <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hard fork proposal from last week's meeting
X-BeenThere: bitcoin-dev@lists.linuxfoundation.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: Bitcoin Protocol 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: Wed, 29 Mar 2017 04:21:42 -0000
--Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/plain;
charset=us-ascii
> On 29 Mar 2017, at 04:50, Tom Zander <tomz@freedommail.ch =
<mailto:tomz@freedommail.ch>> wrote:
>=20
> On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via bitcoin-dev =
wrote:
>> So if we really want to get prepared for a potential HF with unknown
>> parameters,
>=20
> That was not suggested.
>=20
> Maybe you can comment on the very specific suggestion instead?
>=20
> --=20
> Tom Zander
> Blog: https://zander.github.io <https://zander.github.io/>
> Vlog: https://vimeo.com/channels/tomscryptochannel =
<https://vimeo.com/channels/tomscryptochannel>
Just take something like FlexTran as example. How you could get prepared =
for that without first finalising the spec?
Or changing the block interval from 10 minutes to some other value?
Also, fixing the sighash bug for legacy scripts?
There are many other ideas that require a HF:
https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas =
<https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas>=
--Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html;
charset=us-ascii
<html><head><meta http-equiv=3D"Content-Type" content=3D"text/html =
charset=3Dus-ascii"><meta http-equiv=3D"Content-Type" content=3D"text/html=
charset=3Dus-ascii"></head><body style=3D"word-wrap: break-word; =
-webkit-nbsp-mode: space; -webkit-line-break: after-white-space;" =
class=3D""><br class=3D""><div><blockquote type=3D"cite" class=3D""><div =
class=3D"">On 29 Mar 2017, at 04:50, Tom Zander <<a =
href=3D"mailto:tomz@freedommail.ch" class=3D"">tomz@freedommail.ch</a>>=
wrote:</div><br class=3D"Apple-interchange-newline"><div class=3D""><div =
class=3D"">On Tuesday, 28 March 2017 19:34:23 CEST Johnson Lau via =
bitcoin-dev wrote:<br class=3D""><blockquote type=3D"cite" class=3D"">So =
if we really want to get prepared for a potential HF with unknown<br =
class=3D"">parameters,<br class=3D""></blockquote><br class=3D"">That =
was not suggested.<br class=3D""><br class=3D"">Maybe you can comment on =
the very specific suggestion instead?<br class=3D""><br class=3D"">-- =
<br class=3D"">Tom Zander<br class=3D"">Blog: <a =
href=3D"https://zander.github.io" =
class=3D"">https://zander.github.io</a><br class=3D"">Vlog: <a =
href=3D"https://vimeo.com/channels/tomscryptochannel" =
class=3D"">https://vimeo.com/channels/tomscryptochannel</a><br =
class=3D""></div></div></blockquote></div><br class=3D""><div =
class=3D"">Just take something like FlexTran as example. How you could =
get prepared for that without first finalising the spec?</div><div =
class=3D""><br class=3D""></div><div class=3D"">Or changing the block =
interval from 10 minutes to some other value?</div><div class=3D""><br =
class=3D""></div><div class=3D"">Also, fixing the sighash bug for legacy =
scripts?</div><div class=3D""><br class=3D""></div><div class=3D"">There =
are many other ideas that require a HF:</div><div class=3D""><a =
href=3D"https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas" =
class=3D"">https://en.bitcoin.it/wiki/User:Gmaxwell/alt_ideas</a></div></b=
ody></html>=
--Apple-Mail=_4F399D86-46D4-4C0F-B373-0B6ED9B1DAB3--
|
