public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Luke Kenneth Casson Leighton <lkcl@lkcl.net>
To: Bitcoin Protocol Discussion <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Making the case for flag day activation of taproot
Date: Wed, 3 Mar 2021 22:12:21 +0000	[thread overview]
Message-ID: <CAPweEDzavOzQpkiep4-yu6wMFmg2FiVe2LWt75e0LEnRSdQM9g@mail.gmail.com> (raw)
In-Reply-To: <mailman.66954.1614808879.32591.bitcoin-dev@lists.linuxfoundation.org>

would it help by first setting a regular period of e.g. 6 months when
only at that time would consensus rules ever be changed?  not, "6
months from now taproot will be introduced', a rule, "*any* consensus
change regardless of what they are (including NO change) will *ONLY*
be made at regular interval period X months".

this stops dead efforts by bots to announce "consensus! rules! are
changing!" because if it's not at the exact time-period it's clearly
bullshit.

l.


       reply	other threads:[~2021-03-03 22:13 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.66954.1614808879.32591.bitcoin-dev@lists.linuxfoundation.org>
2021-03-03 22:12 ` Luke Kenneth Casson Leighton [this message]
2021-03-03 14:39 [bitcoin-dev] Making the case for flag day activation of taproot Chris Belcher
2021-03-03 16:19 ` Vincent Truong
2021-03-04 23:45   ` Eric Voskuil
2021-03-03 17:30 ` yanmaani
2021-03-03 20:48   ` Chris Belcher
2021-03-03 21:39     ` yanmaani
2021-03-03 19:08 ` Russell O'Connor
2021-03-03 22:14   ` Matt Corallo
2021-03-04 13:47     ` Russell O'Connor
2021-03-04 18:23       ` Keagan McClelland
2021-03-05 14:51         ` Ryan Grant
2021-03-05 18:17           ` Luke Dashjr
2021-03-06 17:57       ` Matt Corallo
2021-03-29  9:17   ` Anthony Towns

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=CAPweEDzavOzQpkiep4-yu6wMFmg2FiVe2LWt75e0LEnRSdQM9g@mail.gmail.com \
    --to=lkcl@lkcl.net \
    --cc=bitcoin-dev@lists.linuxfoundation.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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