From: /dev /fd0 <alicexbtong@gmail•com>
To: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
Date: Sun, 18 Aug 2024 22:08:36 -0700 (PDT) [thread overview]
Message-ID: <29d850d1-912a-4b15-ba41-cc36d05e7074n@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1980 bytes --]
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.
[-- Attachment #1.2: Type: text/html, Size: 2696 bytes --]
next reply other threads:[~2024-08-19 5:18 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 5:08 /dev /fd0 [this message]
2024-08-19 13:16 ` 'Fabian' via Bitcoin Development Mailing List
2024-08-19 17:50 ` /dev /fd0
2024-08-19 13:22 ` David A. Harding
2024-08-19 17:50 ` /dev /fd0
2024-08-20 18:05 ` Murch
2024-08-22 11:43 ` /dev /fd0
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=29d850d1-912a-4b15-ba41-cc36d05e7074n@googlegroups.com \
--to=alicexbtong@gmail$(echo .)com \
--cc=bitcoindev@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox