From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] CTV Meeting #5 Agenda (Tuesday, March 7th, 12:00 PT)
Date: Mon, 7 Mar 2022 19:32:13 -0800 [thread overview]
Message-ID: <CAD5xwhhYjBp8hVeUC=hpefnX9gKUwbSzg0cCnTH10phMZeTEuw@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhgwUm1aco50pUh9v0DJurz1GH49MNbmgOd_HoFsZXaeTw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1134 bytes --]
* Tuesday, March 8th.
I think Noon PT == 8pm UTC?
but dont trust me i cant even tell what day is what.
--
@JeremyRubin <https://twitter.com/JeremyRubin>
On Mon, Mar 7, 2022 at 6:50 PM Jeremy Rubin <jeremy.l.rubin@gmail•com>
wrote:
> Hi all,
>
> There will be a CTV meeting tomorrow at noon PT. Agenda below:
>
> 1) Sapio Taproot Support Update / Request for Review (20 Minutes)
> - Experimental support for Taproot merged on master
> https://github.com/sapio-lang/sapio
> 2) Transaction Sponsoring v.s CPFP/RBF (20 Minutes)
> -
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-February/019879.html
> -
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2020-September/018168.html
> 3) Jamesob's Non-Recursive Vaults Post (20 minutes)
> -
> https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-March/020067.html
> 4) What the heck is everyone talking about on the mailing list all of the
> sudden (30 minutes)
> - EVICT, TLUV, FOLD, Lisp, OP_ANNEX, Drivechain Covenants, Jets, Etc
> 5) Q&A (30 mins)
>
> Best,
>
> Jeremy
>
>
> --
> @JeremyRubin <https://twitter.com/JeremyRubin>
>
[-- Attachment #2: Type: text/html, Size: 4763 bytes --]
next prev parent reply other threads:[~2022-03-08 3:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-08 2:50 Jeremy Rubin
2022-03-08 3:32 ` Jeremy Rubin [this message]
2022-03-09 11:02 ` Jorge Timón
2022-03-09 14:14 ` Michael Folkson
2022-03-10 11:41 ` Jorge Timón
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='CAD5xwhhYjBp8hVeUC=hpefnX9gKUwbSzg0cCnTH10phMZeTEuw@mail.gmail.com' \
--to=jeremy.l.rubin@gmail$(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