From: <eric@voskuil•org>
To: "'Claus Ehrenberg'" <aubergemediale@gmail•com>,
"'Bitcoin Protocol Discussion'"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] March 23rd 2021 Taproot Activation Meeting Notes
Date: Wed, 7 Apr 2021 08:25:22 -0700 [thread overview]
Message-ID: <0a4c01d72bc2$39ff9560$adfec020$@voskuil.org> (raw)
In-Reply-To: <CANPykMr_pyz7XxrXo2FfkNPmBwzMkmnL2SPw8-TmVhOtxkz=-A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 918 bytes --]
You may activate any time you want.
e
From: bitcoin-dev <bitcoin-dev-bounces@lists•linuxfoundation.org> On Behalf Of Claus Ehrenberg via bitcoin-dev
Sent: Wednesday, April 7, 2021 6:42 AM
To: Rusty Russell <rusty@rustcorp•com.au>; Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] March 23rd 2021 Taproot Activation Meeting Notes
As a user, I think it's very important for me to know if Taproot is eventually coming or not. So why not make it so that if _either_ miners _or_ users decide for Taproot, it will activate no matter what. Accepting a chain split is imo the fairest way to 'resolve the conflict' (it can't be resolved anyway).
That would probably mean running ST and and UASF concurrently.
The upside would be that we've got a safe date for Taproot, except neither users nor miners want it.
Cheers,
Claus
[-- Attachment #2: Type: text/html, Size: 2987 bytes --]
next prev parent reply other threads:[~2021-04-07 15:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-24 3:46 Jeremy
2021-03-25 7:02 ` Anthony Towns
2021-03-25 14:30 ` Jeremy
2021-04-06 4:25 ` Rusty Russell
2021-04-07 1:20 ` Ryan Grant
2021-04-07 5:01 ` Rusty Russell
2021-04-07 13:42 ` Claus Ehrenberg
2021-04-07 15:25 ` eric [this message]
2021-04-07 17:13 ` Matt Corallo
2021-04-08 11:11 ` Anthony Towns
2021-03-24 11:23 Michael Folkson
2021-03-24 18:10 ` Jeremy
2021-03-24 19:14 ` Michael Folkson
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='0a4c01d72bc2$39ff9560$adfec020$@voskuil.org' \
--to=eric@voskuil$(echo .)org \
--cc=aubergemediale@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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