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 ) 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 ; 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 To: Bitcoin Development Mailing List 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: X-Google-Group-Id: 786775582512 List-Post: , List-Help: , List-Archive: , List-Unsubscribe: , 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 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,

I am proposing an alternative w= ay to activate soft forks. Please let me know if you see any issues with th= is method.

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

## Abstract=

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

## Motivati= on

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 inl= cuding 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://gith= ub.com/bitcoin/bitcoin/commit/ab91bf39b7c11e9c86bb2043c24f0f377f1cf514.diff=

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

---

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`.

= /dev/fd0
floppy disk guy

--
You received this message because you are subscribed to the Google Groups &= quot;Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an e= mail to bitcoind= ev+unsubscribe@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msg= id/bitcoindev/29d850d1-912a-4b15-ba41-cc36d05e7074n%40googlegroups.com.=
------=_Part_449137_1913765998.1724044116948-- ------=_Part_449136_1417891241.1724044116948--