MIME-Version: 1.0
In-Reply-To: <q2ezd-tOTBF_3zLOedB36jYCuszrKYS-9BHS_Unle1NipWFTWX-aDwsfy5XrAB2D02SwojA4C_vDIyZa-VEh9IlQalF27HYG5C5KAP9096o=@protonmail.ch>
References: <KXL-Ie0q1dKTlbQ2XCyTRCzoQLND-Q7M9CFvYTfhjgeiZ4K3knpetQSwwLviO6whuHXQnFPg-rg8q1xW8w5mNnYFxalvx5_9Vci63lC9ju4=@protonmail.ch>
	<q2ezd-tOTBF_3zLOedB36jYCuszrKYS-9BHS_Unle1NipWFTWX-aDwsfy5XrAB2D02SwojA4C_vDIyZa-VEh9IlQalF27HYG5C5KAP9096o=@protonmail.ch>
From: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <jtimon@jtimon.cc>
Date: Fri, 7 Jul 2017 11:51:16 +0200
Message-ID: <CABm2gDqBE-sxB3j6WK9kW8Zp9GkEG1b3q=_iqJS+XkGzv7EXDQ@mail.gmail.com>
To: shaolinfry <shaolinfry@protonmail.ch>
Content-Type: multipart/alternative; boundary="f403043c51c0b541b00553b72ca5"
Cc: Bitcoin Dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Height based vs block time based thresholds
Precedence: list

--f403043c51c0b541b00553b72ca5
Content-Type: text/plain; charset="UTF-8"

What if you want height based but lockinontimeout = false ?

On 7 Jul 2017 8:09 am, "shaolinfry via bitcoin-dev" <
bitcoin-dev@lists.linuxfoundation.org> wrote:

> I have written a height based reference implementation as well as updated
> the BIP text in the following proposals
>
> "lockinontimeout" was just an implementation detail to allow BIP8 the BIP9
> implementation code. With the change to height based, we can dispense with
> it entirely.
>
> So the two changes BIP8 brings is BIP9 modified to use height not time,
> and remove the veto failed state.
>
> Code: https://github.com/bitcoin/bitcoin/compare/master...shaolinfry:bip8-
> height
> BIP: https://github.com/bitcoin/bips/compare/master...
> shaolinfry:bip8-height
>
>
> -------- Original Message --------
> Subject: [bitcoin-dev] Height based vs block time based thresholds
>
> Some people have criticized BIP9's blocktime based thresholds arguing they
> are confusing (the first retarget after threshold). It is also vulnerable
> to miners fiddling with timestamps in a way that could prevent or delay
> activation - for example by only advancing the block timestamp by 1 second
> you would never meet the threshold (although this would come a the penalty
> of hiking the difficulty dramatically).
>
> On the other hand, the exact date of a height based thresholds is hard to
> predict a long time in advance due to difficulty fluctuations. However,
> there is certainty at a given block height and it's easy to monitor.
>
> If there is sufficient interest, I would be happy to amend BIP8 to be
> height based. I originally omitted height based thresholds in the interests
> of simplicity of review - but now that the proposal has been widely
> reviewed it would be a trivial amendment.
>
>
>
>
> _______________________________________________
> bitcoin-dev mailing list
> bitcoin-dev@lists.linuxfoundation.org
> https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
>
>

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

<div dir=3D"auto">What if you want height based but=C2=A0<span style=3D"fon=
t-family:sans-serif;font-size:13.696px">lockinontimeout =3D false ?</span><=
/div><div class=3D"gmail_extra"><br><div class=3D"gmail_quote">On 7 Jul 201=
7 8:09 am, &quot;shaolinfry via bitcoin-dev&quot; &lt;<a href=3D"mailto:bit=
coin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.linuxfoundation.org</=
a>&gt; wrote:<br type=3D"attribution"><blockquote class=3D"gmail_quote" sty=
le=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>I=
 have written a height based reference implementation as well as updated th=
e BIP text in the following proposals<br></div><div><br></div><div><div>&qu=
ot;lockinontimeout&quot; was just an implementation detail to allow BIP8 th=
e BIP9 implementation code. With the change to height based, we can dispens=
e with it entirely.<br></div><div><br></div><div>So the two changes BIP8 br=
ings is BIP9 modified to use height not time, and remove the veto failed st=
ate.<br></div><div><div><br></div></div><div>Code:=C2=A0<a href=3D"https://=
github.com/bitcoin/bitcoin/compare/master...shaolinfry:bip8-height" target=
=3D"_blank">https://github.com/<wbr>bitcoin/bitcoin/compare/<wbr>master...s=
haolinfry:bip8-<wbr>height</a><br></div></div><div>BIP:=C2=A0<a href=3D"htt=
ps://github.com/bitcoin/bips/compare/master...shaolinfry:bip8-height" targe=
t=3D"_blank">https://github.com/<wbr>bitcoin/bips/compare/master...<wbr>sha=
olinfry:bip8-height</a><br></div><div><br></div><div><br></div><blockquote =
class=3D"m_4220148740660768475protonmail_quote" type=3D"cite"><div>--------=
 Original Message --------<br></div><div>Subject: [bitcoin-dev] Height base=
d vs block time based thresholds<br></div><div><br></div><div>Some people h=
ave criticized BIP9&#39;s blocktime based thresholds arguing they are confu=
sing (the first retarget after threshold). It is also vulnerable to miners =
fiddling with timestamps in a way that could prevent or delay activation - =
for example by only advancing the block timestamp by 1 second you would nev=
er meet the threshold (although this would come a the penalty of hiking the=
 difficulty dramatically).<br></div><div><br></div><div>On the other hand, =
the exact date of a height based thresholds is hard to predict a long time =
in advance due to difficulty fluctuations. However, there is certainty at a=
 given block height and it&#39;s easy to monitor.<br></div><div><br></div><=
div>If there is sufficient interest, I would be happy to amend BIP8 to be h=
eight based. I originally omitted height based thresholds in the interests =
of simplicity of review - but now that the proposal has been widely reviewe=
d it would be a trivial amendment.<br></div><div class=3D"m_422014874066076=
8475protonmail_signature_block"><div class=3D"m_4220148740660768475protonma=
il_signature_block-proton m_4220148740660768475protonmail_signature_block-e=
mpty"><br></div></div><div><br></div></blockquote><div><br></div><br>______=
________________________<wbr>_________________<br>
bitcoin-dev mailing list<br>
<a href=3D"mailto:bitcoin-dev@lists.linuxfoundation.org">bitcoin-dev@lists.=
<wbr>linuxfoundation.org</a><br>
<a href=3D"https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev" =
rel=3D"noreferrer" target=3D"_blank">https://lists.linuxfoundation.<wbr>org=
/mailman/listinfo/bitcoin-<wbr>dev</a><br>
<br></blockquote></div></div>

--f403043c51c0b541b00553b72ca5--