From: Michael Folkson <michaelfolkson@gmail•com>
To: bitcoinmechanicca@protonmail•com,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
Date: Sat, 10 Apr 2021 17:06:43 +0100 [thread overview]
Message-ID: <CAFvNmHRW_pDarfatpUtebd9K0=LohBtRqpYSnNVc58rC5_c10w@mail.gmail.com> (raw)
Hi Bitcoin Mechanic
I will attend but I will be looking at Core PR #21377 over the next
couple of days and I would encourage other reviewers to review that PR
too. If that PR is merged into Core I would strongly recommend any
alternative release be fully compatible with the activation parameters
in Core.
We can discuss in the meeting what we think the cut off date should be
for when Core should no longer be a consideration. Personally I think
(and hope) we will see progress on #21377 in the coming days.
For the sake of the mailing list Bitcoin Mechanic has set up a meeting
to discuss an alternative release to Core with Taproot activation
code.
Thanks
Michael
> Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
> The focus of the meeting will be ratifying the Taproot activation plan previously discussed at the March 16th meeting (aka 2021-03 Plan Y as summarized here):
https://docs.google.com/spreadsheets/d/1K3pmH09yXLTHGV3wqFZGR3ei7QVwtdEwo0PjI2NHD3w/edit#gid=0
> While there was never any consensus reached on the LOT parameter, there appears to be consensus on BIP8 and the remaining parameters, and more than sufficient support for LOT=True to proceed safely.
> Miners will have 18 months in which to signal and accelerate activation. If not, taproot will activate regardless.
> With a majority of the economy running this it will guarantee eventual lock-in of taproot with the smallest chance of a chain split.
> As a reminder, the channel is also open for ongoing discussion 24/7, and there is a web chat client here:
> https://webchat.freenode.net/?channel=##taproot-activation
> Best,
> Bitcoin Mechanic
> Sent with [ProtonMail](https://protonmail.com/) Secure Email.
--
Michael Folkson
Email: michaelfolkson@gmail•com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
next reply other threads:[~2021-04-10 16:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 16:06 Michael Folkson [this message]
2021-04-10 16:59 ` Jeremy
-- strict thread matches above, loose matches on Subject: below --
2021-04-10 2:40 BitcoinMechanic
2021-04-12 19:39 ` Billy Tetrud
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='CAFvNmHRW_pDarfatpUtebd9K0=LohBtRqpYSnNVc58rC5_c10w@mail.gmail.com' \
--to=michaelfolkson@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=bitcoinmechanicca@protonmail$(echo .)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