Delivery-date: Sun, 18 Aug 2024 22:18:37 -0700
Sender: bitcoindev@googlegroups.com
Date: Sun, 18 Aug 2024 22:08:36 -0700 (PDT)
From: /dev /fd0 <alicexbtong@gmail.com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Message-Id: <29d850d1-912a-4b15-ba41-cc36d05e7074n@googlegroups.com>
Subject: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
MIME-Version: 1.0
Content-Type: multipart/mixed; 
	boundary="----=_Part_449136_1417891241.1724044116948"
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com

------=_Part_449136_1417891241.1724044116948
Content-Type: multipart/alternative; 
	boundary="----=_Part_449137_1913765998.1724044116948"

------=_Part_449137_1913765998.1724044116948
Content-Type: text/plain; charset="UTF-8"

Hi Bitcoin Developers,

I am proposing an alternative way to activate soft forks. Please let me 
know if you see any issues with this method.

    BIP: XXX  
    Layer: Consensus (soft fork)  
    Title: nLockTime signaling and flag day activation
    Author: /dev/fd0 <alicexbt@protonmail.com>  
    Status: Draft  
    Type: Standards Track  
    Created: 2024-08-19  
    License: Public Domain

## Abstract

This document describes a process to activate soft forks using flag day 
after `nLockTime` signaling and discussion.

## Motivation

BIP 8 and BIP 9 are controversial. This BIP is an alternative which 
addresses the problems with other activation methods.

## Specification

- Assign numbers to different soft fork proposals or use their BIP numbers
- Users can broadcast their transactions with one of these numbers used as 
`nLockTime` to show support
- Miners inlcuding a transaction in block would signal readiness for a soft 
fork
- Community can analyze these transactions after 3 months and prepare for a 
flag day activation of soft fork

Example:
Use 119 to signal support for OP_CHECKTEMPLATEVERIFY in `nLockTime`

## Reference implementation

Activation: 
https://github.com/bitcoin/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514.diff

Exclusion in relay or mining: 
https://github.com/bitcoinknots/bitcoin/commit/18cd7b0ef6eaeacd06678c6d192b6cacc9d7eee5.diff

---

If a transaction does not get included in block for a long time, users can 
replace it with another transaction spending same inputs and use a 
different `nLockTime`.

/dev/fd0
floppy disk guy

-- 
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 email to bitcoindev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/bitcoindev/29d850d1-912a-4b15-ba41-cc36d05e7074n%40googlegroups.com.

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

Hi Bitcoin Developers,<div><br /></div><div>I am proposing an alternative w=
ay to activate soft forks. Please let me know if you see any issues with th=
is method.<br /><br />=C2=A0 =C2=A0 BIP: XXX =C2=A0<br />=C2=A0 =C2=A0 Laye=
r: Consensus (soft fork) =C2=A0<br />=C2=A0 =C2=A0 Title: nLockTime signali=
ng and flag day activation<br />=C2=A0 =C2=A0 Author: /dev/fd0 &lt;alicexbt=
@protonmail.com&gt; =C2=A0<br />=C2=A0 =C2=A0 Status: Draft =C2=A0<br />=C2=
=A0 =C2=A0 Type: Standards Track =C2=A0<br />=C2=A0 =C2=A0 Created: 2024-08=
-19 =C2=A0<br />=C2=A0 =C2=A0 License: Public Domain<br /><br />## Abstract=
<br /><br />This document describes a process to activate soft forks using =
flag day after `nLockTime` signaling and discussion.<br /><br />## Motivati=
on<br /><br />BIP 8 and BIP 9 are controversial. This BIP is an alternative=
 which addresses the problems with other activation methods.<br /><br />## =
Specification<br /><br />- Assign numbers to different soft fork proposals =
or use their BIP numbers<br />- Users can broadcast their transactions with=
 one of these numbers used as `nLockTime` to show support<br />- Miners inl=
cuding a transaction in block would signal readiness for a soft fork<br />-=
 Community can analyze these transactions after 3 months and prepare for a =
flag day activation of soft fork<br /><br />Example:<br />Use 119 to signal=
 support for OP_CHECKTEMPLATEVERIFY in `nLockTime`<br /><br />## Reference =
implementation<br /><br />Activation: <a href=3D"https://github.com/bitcoin=
/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514.diff">https://gith=
ub.com/bitcoin/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514.diff=
</a><br /><br />Exclusion in relay or mining: <a href=3D"https://github.com=
/bitcoinknots/bitcoin/commit/18cd7b0ef6eaeacd06678c6d192b6cacc9d7eee5.diff"=
>https://github.com/bitcoinknots/bitcoin/commit/18cd7b0ef6eaeacd06678c6d192=
b6cacc9d7eee5.diff</a><br /><br />---<br /><br />If a transaction does not =
get included in block for a long time, users can replace it with another tr=
ansaction spending same inputs and use a different `nLockTime`.<br /><br />=
/dev/fd0<br />floppy disk guy</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/29d850d1-912a-4b15-ba41-cc36d05e7074n%40googlegroups.=
com?utm_medium=3Demail&utm_source=3Dfooter">https://groups.google.com/d/msg=
id/bitcoindev/29d850d1-912a-4b15-ba41-cc36d05e7074n%40googlegroups.com</a>.=
<br />

------=_Part_449137_1913765998.1724044116948--

------=_Part_449136_1417891241.1724044116948--