From: BitcoinMechanic <bitcoinmechanicca@protonmail•com>
To: "bitcoin-dev@lists•linuxfoundation.org"
<bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 13th April 19:00 UTC
Date: Sat, 10 Apr 2021 02:40:29 +0000 [thread overview]
Message-ID: <LXABjC3kHmtKvzKD0zz1rh0QxEEbCUr5bUv5A1uzu8OzJ0U3CMYG8e6i9OaXHmvIpeYTja0vN493GoC9rKV3W_MOMOuLbNWzCEdqEhGM-fs=@protonmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1025 bytes --]
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.
[-- Attachment #2.1: Type: text/html, Size: 1852 bytes --]
[-- Attachment #2.2: image1618022427865 --]
[-- Type: image/png, Size: 6217 bytes --]
next reply other threads:[~2021-04-10 2:40 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-10 2:40 BitcoinMechanic [this message]
2021-04-12 19:39 ` Billy Tetrud
2021-04-10 16:06 Michael Folkson
2021-04-10 16:59 ` Jeremy
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='LXABjC3kHmtKvzKD0zz1rh0QxEEbCUr5bUv5A1uzu8OzJ0U3CMYG8e6i9OaXHmvIpeYTja0vN493GoC9rKV3W_MOMOuLbNWzCEdqEhGM-fs=@protonmail.com' \
--to=bitcoinmechanicca@protonmail$(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