From: "David A. Harding" <dave@dtrt•org>
To: /dev /fd0 <alicexbtong@gmail•com>
Cc: Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] BIP 8.5: Flag day activation based on nlocktime signaling
Date: Mon, 19 Aug 2024 03:22:03 -1000 [thread overview]
Message-ID: <f3142cbfa94acd21e5fe9577b4e2fa9e@dtrt.org> (raw)
In-Reply-To: <29d850d1-912a-4b15-ba41-cc36d05e7074n@googlegroups.com>
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
few I quickly found:
-
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193.html
-
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014321.html
-
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020344.html
-
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002729.html
I think it'd be useful if you could explain how your proposal
meaningfully differs from previous proposals.
-Dave
--
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/f3142cbfa94acd21e5fe9577b4e2fa9e%40dtrt.org.
next prev parent reply other threads:[~2024-08-19 14:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 5:08 /dev /fd0
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 [this message]
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=f3142cbfa94acd21e5fe9577b4e2fa9e@dtrt.org \
--to=dave@dtrt$(echo .)org \
--cc=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