From: Jeremy <jlrubin@mit.edu>
To: Bitcoin development mailing list <bitcoin-dev@lists.linuxfoundation.org>
Subject: [bitcoin-dev] Taproot Activation Meeting 4/20 Cancelled
Date: Sat, 17 Apr 2021 11:45:31 -0700 [thread overview]
Message-ID: <CAD5xwhi_ymtyu_A9Whm-8i8XPB=ZWZZZrm79PN+vfhsnUPPSkg@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Dear Bitcoin Developers,
There are no current agenda items or technical issues to weed out,
everything has been through the grinder, and Bitcoin Core seems to be on a
roll with getting Release Candidate 1 with Speedy Trial MTP in the pipe.
If anyone is hazy on the details -- it has been a little bit of a blaze --
I'd refer you to https://github.com/bitcoin/bips/pull/1104 (changes to BIP
341) which details what was hashed out by joint agreement of many community
members.
Not to be blunt, but given the high tensions, I recommend that everyone
take the opportunity to thoroughly enjoy the holiday :)
Best,
Jeremy
--
@JeremyRubin <https://twitter.com/JeremyRubin>
<https://twitter.com/JeremyRubin>
[-- Attachment #2: Type: text/html, Size: 2281 bytes --]
next reply other threads:[~2021-04-17 18:45 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-04-17 18:45 Jeremy [this message]
2021-04-17 20:10 ` [bitcoin-dev] Taproot Activation Meeting 4/20 Cancelled yancy
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='CAD5xwhi_ymtyu_A9Whm-8i8XPB=ZWZZZrm79PN+vfhsnUPPSkg@mail.gmail.com' \
--to=jlrubin@mit.edu \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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