MIME-Version: 1.0
In-Reply-To: <a4a8c42d8e6528dd7c0ae100958dd988@xbt.hk>
References: <f225318eddd0aadc71861f988f2f4674@xbt.hk>
	<CABsx9T2VoWm04i_vQv7u0vXM6hdMBM29bnMSuv8RmMFMGxOdpg@mail.gmail.com>
	<a4a8c42d8e6528dd7c0ae100958dd988@xbt.hk>
Date: Thu, 4 Feb 2016 12:00:49 -0600
Message-ID: <CABaSBawLVciovTLrdd_yVwOgAE-i5cem6+pC7-mnuL3TsQVn=Q@mail.gmail.com>
From: Bryan Bishop <kanzure@gmail.com>
To: jl2012 <jl2012@xbt.hk>, Bryan Bishop <kanzure@gmail.com>
Content-Type: multipart/alternative; boundary=089e0160b7c6c4977f052af5833f
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Hardfork bit BIP
Precedence: list

--089e0160b7c6c4977f052af5833f
Content-Type: text/plain; charset=UTF-8

On Thu, Feb 4, 2016 at 11:56 AM, jl2012 via bitcoin-dev <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> past the triggering block. A block-chain re-org of two thousand or
>> more blocks on the main Bitcoin chain is unthinkable-- the economic
>> chaos would be massive, and the reaction to such a drastic (and
>> extremely unlikely) event would certainly be a hastily imposed
>> checkpoint to get everybody back onto the chain that everybody was
>> using for economic transactions.
>>
>
> No, the "triggering block" you mentioned is NOT where the hardfork starts.
> Using BIP101 as an example, the hardfork starts when the first >1MB is
> mined. For people who failed to upgrade, the "grace period" is always zero,
> which is the moment they realize a hardfork.
>

Are there any plans written down anywhere about the "hastily imposed
checkpoint" scenario? As far as I know, we would have to check-point on
both blockchains because of the way that hard-forks work (creating two
separate chains and/or networks). Nothing about this should be an
"emergency", we have all the time in the world to prepare a safe and
responsible way to upgrade the network without unilaterally
declaring obsolescence.

- Bryan
http://heybryan.org/
1 512 203 0507

--089e0160b7c6c4977f052af5833f
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div dir=3D"ltr"><div class=3D"gmail_extra"><div class=3D"gmail_quote">On T=
hu, Feb 4, 2016 at 11:56 AM, jl2012 via bitcoin-dev <span dir=3D"ltr">&lt;<=
a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org" target=3D"_blank">b=
itcoin-dev@lists.linuxfoundation.org</a>&gt;</span> wrote:<br><blockquote c=
lass=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left-width:1p=
x;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1=
ex"><span class=3D""><blockquote class=3D"gmail_quote" style=3D"margin:0px =
0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);bord=
er-left-style:solid;padding-left:1ex">past the triggering block. A block-ch=
ain re-org of two thousand or<br>
more blocks on the main Bitcoin chain is unthinkable-- the economic<br>
chaos would be massive, and the reaction to such a drastic (and<br>
extremely unlikely) event would certainly be a hastily imposed<br>
checkpoint to get everybody back onto the chain that everybody was<br>
using for economic transactions.<br>
</blockquote>
<br></span>
No, the &quot;triggering block&quot; you mentioned is NOT where the hardfor=
k starts. Using BIP101 as an example, the hardfork starts when the first &g=
t;1MB is mined. For people who failed to upgrade, the &quot;grace period&qu=
ot; is always zero, which is the moment they realize a hardfork.<span class=
=3D""><br></span></blockquote></div><br>Are there any plans written down an=
ywhere about the &quot;hastily imposed checkpoint&quot; scenario? As far as=
 I know, we would have to check-point on both blockchains because of the wa=
y that hard-forks work (creating two separate chains and/or networks). Noth=
ing about this should be an &quot;emergency&quot;, we have all the time in =
the world to prepare a safe and responsible way to upgrade the network with=
out unilaterally declaring=C2=A0obsolescence.<br><div><br></div><div class=
=3D"gmail_signature">- Bryan<br><a href=3D"http://heybryan.org/" target=3D"=
_blank">http://heybryan.org/</a><br>1 512 203 0507</div>
</div></div>

--089e0160b7c6c4977f052af5833f--