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
|
Return-Path: <ahmedzsales18@gmail.com>
Received: from smtp1.linuxfoundation.org (smtp1.linux-foundation.org
[172.17.192.35])
by mail.linuxfoundation.org (Postfix) with ESMTPS id 3258F8D8
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Aug 2015 22:51:10 +0000 (UTC)
X-Greylist: whitelisted by SQLgrey-1.7.6
Received: from mail-vk0-f54.google.com (mail-vk0-f54.google.com
[209.85.213.54])
by smtp1.linuxfoundation.org (Postfix) with ESMTPS id AE64D11E
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Aug 2015 22:51:09 +0000 (UTC)
Received: by vkao123 with SMTP id o123so15595932vka.3
for <bitcoin-dev@lists.linuxfoundation.org>;
Tue, 18 Aug 2015 15:51:08 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113;
h=mime-version:in-reply-to:references:date:message-id:subject:from:to
:content-type; bh=mWJIuahU2tl2YWPWaDrq+5C23Td0e6gUMuThcl460/U=;
b=h1pZLd6LVH+a4a0noh5HeYlvnDssgJWjN4poFlZaUb/b8VE+zt67az/fhj36KYpsc3
+HuWKPUxZZFm5d6CIal7nK1I3IUEjXHpjESN79P6xrtD3JJsayHulN1/oxbdGIIJlt1r
vsg5IWbit7zHruPlSj+3CdviQZ9TvZvGYx7HWmBVxD+79k04A7rkZfY74Ny98Nc9xZQ4
RvxlAFJGqk3kUVrXWJiAy5zACI5Qe0Ed6JBGZ1Dsi18XJ6ggzoSUzkRHgmjWrpypOmw3
iNMK7vV1/PX/azDWC6uXoER6gHR43+yyLLvCtX3s2iWlK4vNszldQeuu0QZn6xcAXdDX
mW1A==
MIME-Version: 1.0
X-Received: by 10.52.72.84 with SMTP id b20mr11975547vdv.6.1439938268788; Tue,
18 Aug 2015 15:51:08 -0700 (PDT)
Received: by 10.31.109.134 with HTTP; Tue, 18 Aug 2015 15:51:08 -0700 (PDT)
In-Reply-To: <d17549688c0c747b2077c1f6f96b6445@xbt.hk>
References: <d17549688c0c747b2077c1f6f96b6445@xbt.hk>
Date: Tue, 18 Aug 2015 23:51:08 +0100
Message-ID: <CADr=VrROXW0cvCYKsidxSLgtYvBxPAGvcv_FFbeTAFJ3tF6AiQ@mail.gmail.com>
From: Ahmed Zsales <ahmedzsales18@gmail.com>
To: bitcoin-dev@lists.linuxfoundation.org
Content-Type: multipart/alternative; boundary=0023544478f3027bbe051d9dc1ac
X-Spam-Status: No, score=-2.4 required=5.0 tests=BAYES_00,DKIM_SIGNED,
DKIM_VALID,DKIM_VALID_AU,FREEMAIL_ENVFROM_END_DIGIT,FREEMAIL_FROM,
HTML_MESSAGE,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
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an
experimental hardfork?
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: Tue, 18 Aug 2015 22:51:10 -0000
--0023544478f3027bbe051d9dc1ac
Content-Type: text/plain; charset=UTF-8
-> You need to take into account the reward halving, likely to be in
3Q2016. Forks and reward halving at the same time would possibly be a bad
combination.
-> The original proposed date for the fork was December 2015. It was pushed
back to January as December is a busy period for a lot of people and
businesses. Likewise, June is a busy period for people. July / August is a
good period as it is quiet because people go on holiday. A window of 2
months during holiday periods is better than starting in June. January 2016
is better, mainly because of the excessive reward halving chatter likely to
be going on..
..
> Proposal (parameters in ** are my recommendations but negotiable):
>
> 1. Today, we all agree that some kind of block size hardfork will happen
> on t1=*1 June 2016*
>
> 2. If no other consensus could be reached before t2=*1 Feb 2016*, we will
> adopt the backup plan
>
> 3. The backup plan is: t3=*30 days* after m=*80%* of miner approval, but
> not before t1=*1 June 2016*, the block size is increased to s=*1.5MB*
>
> 4. If the backup plan is adopted, we all agree that a better solution
> should be found before t4=*31 Dec 2017*.
> ..
--0023544478f3027bbe051d9dc1ac
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
<div dir=3D"ltr">-> You need to take into account the reward halving, li=
kely to be in 3Q2016. Forks and reward halving at the same time would possi=
bly be a bad combination.=C2=A0<div><br></div><div>-> The original propo=
sed date for the fork was December 2015. It was pushed back to January as D=
ecember is a busy period for a lot of people and businesses. Likewise, June=
is a busy period for people. July / August is a good period as it is quiet=
because people go on holiday. A window of 2 months during holiday periods =
is better than starting in June. January 2016 is better, mainly because of =
the excessive reward halving chatter likely to be going on..<div><div class=
=3D"gmail_extra"><br><div class=3D"gmail_quote"><blockquote class=3D"gmail_=
quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1=
ex">..<br>
Proposal (parameters in ** are my recommendations but negotiable):<br>
<br>
1. Today, we all agree that some kind of block size hardfork will happen on=
t1=3D*1 June 2016*<br>
<br>
2. If no other consensus could be reached before t2=3D*1 Feb 2016*, we will=
adopt the backup plan<br>
<br>
3. The backup plan is: t3=3D*30 days* after m=3D*80%* of miner approval, bu=
t not before t1=3D*1 June 2016*, the block size is increased to s=3D*1.5MB*=
<br>
<br>
4. If the backup plan is adopted, we all agree that a better solution shoul=
d be found before t4=3D*31 Dec 2017*.<br>
..</blockquote></div></div></div></div></div>
--0023544478f3027bbe051d9dc1ac--
|
