From: Michael Folkson <michaelfolkson@gmail•com>
To: jlrubin@mit•edu,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] (Recurring) Taproot activation meeting on IRC - Tuesday 23rd March 19:00 UTC + every fortnight
Date: Mon, 22 Mar 2021 12:10:03 +0000 [thread overview]
Message-ID: <CAFvNmHQthx=j=wu-LZT85Cm_25Tqua20wQBxz2Jg2jFtd_pmvg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1114 bytes --]
Thanks for organizing this Jeremy, agenda looks great. I do think we are
now at the time where Taproot activation becomes a priority for all those
with a stake in Taproot activation.
Although these parameters haven't yet been finalized the proposed
(approximate) startheight is May 1st which is less than 6 weeks away.
https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2021-March/018594.html
Therefore I encourage everyone with a stake in Taproot activation to attend
this meeting tomorrow (Tuesday 19:00 UTC) and raise any specific concerns
with block height vs MTP and proposed timetables as Jeremy suggests before
the meeting.
Personally I think we should avoid the min activation height dragging into
December. November (current proposed is November 13th) seems ideal as to
avoid (admittedly Western) holidays in December and January. Other than
that I think we have some (limited) wiggle room with regards to the exact
timetable to ensure the optimal code is merged.
--
Michael Folkson
Email: michaelfolkson@gmail•com
Keybase: michaelfolkson
PGP: 43ED C999 9F85 1D40 EAF4 9835 92D6 0159 214C FEE3
[-- Attachment #2: Type: text/html, Size: 1340 bytes --]
next reply other threads:[~2021-03-22 12:10 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-22 12:10 Michael Folkson [this message]
-- strict thread matches above, loose matches on Subject: below --
2021-03-19 21:41 Jeremy
2021-03-21 18:10 ` 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='CAFvNmHQthx=j=wu-LZT85Cm_25Tqua20wQBxz2Jg2jFtd_pmvg@mail.gmail.com' \
--to=michaelfolkson@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=jlrubin@mit$(echo .)edu \
/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