From: /dev /fd0 <alicexbtong@gmail•com>
To: 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 10:50:13 -0700 (PDT) [thread overview]
Message-ID: <003b5d22-a3c6-403c-b56d-0b2f3aca1e2an@googlegroups.com> (raw)
In-Reply-To: <f3142cbfa94acd21e5fe9577b4e2fa9e@dtrt.org>
[-- Attachment #1.1: Type: text/plain, Size: 1938 bytes --]
Hi Dave,
Below are the differences between proposed BIP and earlier proposals:
>
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-April/014193.html
- It uses OP_RETURN
- It requires some percentage of tagged input addresses to reach a certain
level
>
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2017-May/014321.html
- It requires soft fork and a new opcode OP_CHECKBLOCKVERSION
>
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-April/020344.html
- It requires soft fork
>
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2013-June/002729.html
- It involves Proof-of-Stake voting based on UTXOs
/dev/fd0
floppy disk guy
On Monday, August 19, 2024 at 2:13:33 PM UTC David A. Harding wrote:
> 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/003b5d22-a3c6-403c-b56d-0b2f3aca1e2an%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 4417 bytes --]
next prev parent reply other threads:[~2024-08-19 18:19 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
2024-08-19 17:50 ` /dev /fd0 [this message]
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=003b5d22-a3c6-403c-b56d-0b2f3aca1e2an@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