Delivery-date: Mon, 19 Aug 2024 11:19:34 -0700
Sender: bitcoindev@googlegroups.com
Date: Mon, 19 Aug 2024 10:50:13 -0700 (PDT)
From: /dev /fd0 <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <003b5d22-a3c6-403c-b56d-0b2f3aca1e2an@googlegroups.com>
In-Reply-To: <f3142cbfa94acd21e5fe9577b4e2fa9e@dtrt.org>
References: <29d850d1-912a-4b15-ba41-cc36d05e7074n@googlegroups.com>
 <f3142cbfa94acd21e5fe9577b4e2fa9e@dtrt.org>
Subject: Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_464206_1918729056.1724089813303"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_464206_1918729056.1724089813303
Content-Type: multipart/alternative; 
	boundary="----=_Part_464207_811860762.1724089813303"

------=_Part_464207_811860762.1724089813303
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable

Hi Dave,

Below are the differences between proposed BIP and earlier proposals:

>=20
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193.h=
tml

- It uses OP_RETURN
- It requires some percentage of tagged input addresses to reach a certain=
=20
level

>=20
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014321.htm=
l

- It requires soft fork and a new opcode OP_CHECKBLOCKVERSION

>=20
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020344.h=
tml

- It requires soft fork

>=20
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002729.ht=
ml

- It involves Proof-of-Stake voting based on UTXOs

/dev/fd0
floppy disk guy

On Monday, August 19, 2024 at 2:13:33=E2=80=AFPM UTC David A. Harding wrote=
:

> On 2024-08-18 19:08, /dev /fd0 wrote:
> > - Users can broadcast their transactions with one of these numbers
> > used as `nLockTime` to show support
>
> Variations on this idea have been proposed many times before; here's a=20
> few I quickly found:
>
> -=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193=
.html
>
> -=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014321.h=
tml
>
> -=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020344=
.html
>
> -=20
>
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002729.=
html
>
> I think it'd be useful if you could explain how your proposal=20
> meaningfully differs from previous proposals.
>
> -Dave
>

--=20
You received this message because you are subscribed to the Google Groups "=
Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/=
bitcoindev/003b5d22-a3c6-403c-b56d-0b2f3aca1e2an%40googlegroups.com.

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

Hi Dave,<div><br /></div><div>Below are the differences between proposed BI=
P and earlier proposals:<br /><div><br /></div><div>&gt;=C2=A0<a href=3D"ht=
tps://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193.htm=
l">https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/01419=
3.html</a></div><div><br />- It uses OP_RETURN</div><div>- It requires some=
 percentage of tagged input addresses to reach a certain level</div><div><b=
r /></div><div>&gt;=C2=A0<a href=3D"https://lists.linuxfoundation.org/piper=
mail/bitcoin-dev/2017-May/014321.html">https://lists.linuxfoundation.org/pi=
permail/bitcoin-dev/2017-May/014321.html</a></div><div><br /></div><div>- I=
t requires soft fork and a new opcode OP_CHECKBLOCKVERSION<br /><br />&gt;=
=C2=A0<a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/20=
22-April/020344.html">https://lists.linuxfoundation.org/pipermail/bitcoin-d=
ev/2022-April/020344.html</a></div><div><br /></div><div>- It requires soft=
 fork<br /><br />&gt;=C2=A0<a href=3D"https://lists.linuxfoundation.org/pip=
ermail/bitcoin-dev/2013-June/002729.html">https://lists.linuxfoundation.org=
/pipermail/bitcoin-dev/2013-June/002729.html</a></div><div><br /></div><div=
>- It involves=C2=A0Proof-of-Stake voting based on UTXOs<br /><br />/dev/fd=
0</div><div>floppy disk guy<br /><br /></div></div><div class=3D"gmail_quot=
e"><div dir=3D"auto" class=3D"gmail_attr">On Monday, August 19, 2024 at 2:1=
3:33=E2=80=AFPM UTC David A. Harding wrote:<br/></div><blockquote class=3D"=
gmail_quote" style=3D"margin: 0 0 0 0.8ex; border-left: 1px solid rgb(204, =
204, 204); padding-left: 1ex;">On 2024-08-18 19:08, /dev /fd0 wrote:
<br>&gt; - Users can broadcast their transactions with one of these numbers
<br>&gt; used as `nLockTime` to show support
<br>
<br>Variations on this idea have been proposed many times before; here&#39;=
s a=20
<br>few I quickly found:
<br>
<br>-=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017=
-April/014193.html" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundatio=
n.org/pipermail/bitcoin-dev/2017-April/014193.html&amp;source=3Dgmail&amp;u=
st=3D1724171505323000&amp;usg=3DAOvVaw3XHj3Wa0B4P_-qPqEaUHRC">https://lists=
.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193.html</a>
<br>
<br>-=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017=
-May/014321.html" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundatio=
n.org/pipermail/bitcoin-dev/2017-May/014321.html&amp;source=3Dgmail&amp;ust=
=3D1724171505323000&amp;usg=3DAOvVaw2_Ip3zt5ynYdzY9E2EBXR7">https://lists.l=
inuxfoundation.org/pipermail/bitcoin-dev/2017-May/014321.html</a>
<br>
<br>-=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022=
-April/020344.html" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundatio=
n.org/pipermail/bitcoin-dev/2022-April/020344.html&amp;source=3Dgmail&amp;u=
st=3D1724171505323000&amp;usg=3DAOvVaw0TsMoIDnG5Zmj1GMvIOXSV">https://lists=
.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020344.html</a>
<br>
<br>-=20
<br><a href=3D"https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013=
-June/002729.html" target=3D"_blank" rel=3D"nofollow" data-saferedirecturl=
=3D"https://www.google.com/url?hl=3Den&amp;q=3Dhttps://lists.linuxfoundatio=
n.org/pipermail/bitcoin-dev/2013-June/002729.html&amp;source=3Dgmail&amp;us=
t=3D1724171505323000&amp;usg=3DAOvVaw1AMoV2JSWVaYroCOKqTfbm">https://lists.=
linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002729.html</a>
<br>
<br>I think it&#39;d be useful if you could explain how your proposal=20
<br>meaningfully differs from previous proposals.
<br>
<br>-Dave
<br></blockquote></div>

<p></p>

-- <br />
You received this message because you are subscribed to the Google Groups &=
quot;Bitcoin Development Mailing List&quot; group.<br />
To unsubscribe from this group and stop receiving emails from it, send an e=
mail to <a href=3D"mailto:bitcoindev+unsubscribe@googlegroups.com">bitcoind=
ev+unsubscribe@googlegroups.com</a>.<br />
To view this discussion on the web visit <a href=3D"https://groups.google.c=
om/d/msgid/bitcoindev/003b5d22-a3c6-403c-b56d-0b2f3aca1e2an%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/003b5d22-a3c6-403c-b56d-0b2f3aca1e2an%40googlegroups.com</a>.=
<br />

------=_Part_464207_811860762.1724089813303--

------=_Part_464206_1918729056.1724089813303--