MIME-Version: 1.0
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
Subject: Re: [bitcoin-dev] Bitcoin is an experiment. Why don't we have an
 experimental hardfork?
Precedence: list

--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">-&gt; 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>-&gt; 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--