From: Luke Dashjr <luke@dashjr•org>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] Taproot activation meeting on IRC - Tuesday 16th March 19:00 UTC
Date: Mon, 15 Mar 2021 17:20:04 +0000 [thread overview]
Message-ID: <202103151720.04687.luke@dashjr.org> (raw)
At the previous meeting, there was consensus for BIP8 activation parameters
except for LOT, assuming a release around this time. Since then, a release
has not occurred, and the new idea of Speedy Trial has been proposed to
preempt the original/main activation plan.
It's probably a good idea to meet up again to discuss these things and adjust
accordingly.
Agenda:
- Speedy Trial: Can we get a comparable consensus on the proposal?
(Note: current draft conflicts with original plan timeline)
- Main activation, post ST: Moving startheight (and timeoutheight?) later
is probably a good idea at this point, both because too little progress has
been made on it, and to avoid the conflict with the current ST draft.
- Making progress: To date, too few people have been involved in materialising
the main activation plan. If it's going to move forward, more people need to
get actively involved. This should not wait for ST to complete, unless we
want another 4-5 month slip of the timeline.
This meeting is tentatively scheduled for *tomorrow*, March 16th at the usual
time of 19:00 UTC, in freenode's ##Taproot-activation IRC channel. If turnout
is too low, we can postpone it a week, but it'd be nice to get things
resolved and moving sooner.
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
Luke
next reply other threads:[~2021-03-15 17:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-15 17:20 Luke Dashjr [this message]
2021-03-15 19:14 ` Jeremy
2021-03-15 19:37 ` Luke Dashjr
2021-03-15 20:59 ` Jeremy
2021-03-15 21:46 ` Luke Dashjr
2021-03-16 17:42 ` Emil Pfeffer
2021-03-17 8:21 Prayank
2021-03-19 10:45 ` Emil Pfeffer
2021-03-19 16:55 ` Prayank
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=202103151720.04687.luke@dashjr.org \
--to=luke@dashjr$(echo .)org \
--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