summaryrefslogtreecommitdiff
path: root/c7/81a817f75181a325a780f6c807d4d4326d861b
blob: df6d6942909b2925e3233fde290093aef0aaba7f (plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
Delivery-date: Sun, 18 Aug 2024 22:18:37 -0700
Received: from mail-yw1-f185.google.com ([209.85.128.185])
	by mail.fairlystable.org with esmtps  (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
	(Exim 4.94.2)
	(envelope-from <bitcoindev+bncBCU2P6FJ3EBBBJFLRO3AMGQECJUZWSQ@googlegroups.com>)
	id 1sfumr-0003wD-Az
	for bitcoindev@gnusha.org; Sun, 18 Aug 2024 22:18:37 -0700
Received: by mail-yw1-f185.google.com with SMTP id 00721157ae682-690404fd230sf63105417b3.3
        for <bitcoindev@gnusha.org>; Sun, 18 Aug 2024 22:18:36 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlegroups.com; s=20230601; t=1724044711; x=1724649511; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:sender:from:to:cc:subject:date
         :message-id:reply-to;
        bh=ylAm8/RO78Hy/tQsG4PfLRjl8aewR0lvJz5oypqQJcI=;
        b=HfFXWI40QK+OR34c0L/M+kZwuZpdBYdc6CbNNhwrXtn+kLHtlD8Dl/g/PbsbL98bDA
         yr2n03vtuxZYgAxoob6jucEC1cc6gn552YBRi9MdTfmFocmEM3t5p/ClJvFcVkJGBKoK
         +7XAwOh5tBfH1TA61wfmqcqctYFkEWkYzAHjBoCEPAosFpqDKyFgx+0FlM4SWPc7WQXE
         LDNeqYup1RvRmZETfXrBSsJzUQp0YjFCisAL4plq77KskHDdYrxvZ/9Nr3f6Vhkxi5Co
         qt5iO5DJcHFJ4a+K9SK4yfd0MwGiL11VD274Mj/66mBatuafiqtE6b/lWd8bxwdF0X2c
         KlCg==
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20230601; t=1724044711; x=1724649511; darn=gnusha.org;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:from:to:cc:subject:date:message-id
         :reply-to;
        bh=ylAm8/RO78Hy/tQsG4PfLRjl8aewR0lvJz5oypqQJcI=;
        b=QsZnMGK0Eg/MNcT3qHoZ+la8Pbfwv1dPGp7VWs4j1CBJ0JYndZo6RFGd7QwE3qBioE
         rpuSGnlZJ20waHzX8OY87BF3reEIsK3G7erZ+XNgp5YokW86YD3skH92YZGeHMzB5iBe
         nao6fj/6P3HLAW89tq5acqIV3ETgq1TG0mAlHBN3GhuSYdCIYM0vFksl3oWdJwQr3xFg
         dAyoh35/nSe1O4UJo1CB1MlGeju9RkEjSC11kNnj/bOkuCKuvJ2J2Qq4O1U9pV6BAtbF
         T0zXH0c8HZFl3t4pgeud3iCl7KwmZQjCgBm55+zHkE8kgevHHhl6TIcNwIV3fYCcOxvL
         u5QQ==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20230601; t=1724044711; x=1724649511;
        h=list-unsubscribe:list-subscribe:list-archive:list-help:list-post
         :list-id:mailing-list:precedence:x-original-sender:mime-version
         :subject:message-id:to:from:date:x-beenthere:x-gm-message-state
         :sender:from:to:cc:subject:date:message-id:reply-to;
        bh=ylAm8/RO78Hy/tQsG4PfLRjl8aewR0lvJz5oypqQJcI=;
        b=BOEZ8fNngvitPkw0txUqGdRY5nQ0x8xPSy9QbeyYfwkrzl+HqsOoRqe0Xmlr7g0Bgm
         87toosWt2oiCxtJ9lhkIvWk7NbUoQ9baWQnf0KHJutW5884Dr4/E3PIQYk1OK4A9cfxe
         pnYMPzbu+KZDj4N34w6pSFmbDUkxqhITMn0u2U5bD9/1cbG0GZGA9jcfCIWNIIHig92d
         F4/UKqJJlo9O5QeoaoR2WxK8t1S8MrQ+GmQTU0pM3CvApVzVjxSR3ASuP676+ySa4SZ0
         EpGHIfp7U5YRZrKXeq2ZMU2iSGF1YNQeD9hUoQvqI4/0N+v/TtxRdhGh1NtseHaj+Eh7
         xkGg==
Sender: bitcoindev@googlegroups.com
X-Forwarded-Encrypted: i=1; AJvYcCVneXwAbo2V9lT15fCtDIHJoC34c16rc3Ny0ATP9xGRQ+HC3mliZ+ru9jIodGQhevUUS8pz+FHz3WVPhufNSYkUeT4Mlyg=
X-Gm-Message-State: AOJu0YzNJwtJuiEmSnWevYlBCa+4irGVr+JPFHg0eYujOXYde8NTG4Aq
	Ctk3TgdSuSXRxGn6DoLehSpQz6mInruToJzQcRVsLqIEdOj+n4X+
X-Google-Smtp-Source: AGHT+IH/WPMvxmCpZe2NAvR9cYU4BqaaK4i2qkIZPWdqiPENDLW9TDeVSDXU26UNXW7GkPLShqH1YQ==
X-Received: by 2002:a05:6902:2b13:b0:e0e:8319:c6e4 with SMTP id 3f1490d57ef6-e1180e9967fmr11038282276.8.1724044710244;
        Sun, 18 Aug 2024 22:18:30 -0700 (PDT)
X-BeenThere: bitcoindev@googlegroups.com
Received: by 2002:a05:6902:1247:b0:e13:d4bd:79fd with SMTP id
 3f1490d57ef6-e13d4bd7c1als413870276.1.-pod-prod-05-us; Sun, 18 Aug 2024
 22:18:28 -0700 (PDT)
X-Received: by 2002:a81:b049:0:b0:62c:67f4:4f5 with SMTP id 00721157ae682-6b1bc3f9536mr4367357b3.9.1724044708078;
        Sun, 18 Aug 2024 22:18:28 -0700 (PDT)
Received: by 2002:a05:690c:3244:b0:627:7f59:2eee with SMTP id 00721157ae682-6b46d7bdd14ms7b3;
        Sun, 18 Aug 2024 22:08:38 -0700 (PDT)
X-Received: by 2002:a05:690c:7281:b0:64a:e220:bfb5 with SMTP id 00721157ae682-6b1b749d255mr9952757b3.1.1724044117188;
        Sun, 18 Aug 2024 22:08:37 -0700 (PDT)
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"
X-Original-Sender: alicexbtong@gmail.com
Precedence: list
Mailing-list: list bitcoindev@googlegroups.com; contact bitcoindev+owners@googlegroups.com
List-ID: <bitcoindev.googlegroups.com>
X-Google-Group-Id: 786775582512
List-Post: <https://groups.google.com/group/bitcoindev/post>, <mailto:bitcoindev@googlegroups.com>
List-Help: <https://groups.google.com/support/>, <mailto:bitcoindev+help@googlegroups.com>
List-Archive: <https://groups.google.com/group/bitcoindev
List-Subscribe: <https://groups.google.com/group/bitcoindev/subscribe>, <mailto:bitcoindev+subscribe@googlegroups.com>
List-Unsubscribe: <mailto:googlegroups-manage+786775582512+unsubscribe@googlegroups.com>,
 <https://groups.google.com/group/bitcoindev/subscribe>
X-Spam-Score: -0.5 (/)

------=_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--