From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Bitcoin development mailing list <bitcoin-dev@lists•linuxfoundation.org>
Subject: [bitcoin-dev] 7 Theses on a next step for BIP-119
Date: Tue, 19 Apr 2022 10:31:54 -0700 [thread overview]
Message-ID: <CAD5xwhjVS4Y4e3qDWzJfva+0hiKpe8-WqmX_kUHrpfXmG5sMXw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 450 bytes --]
Devs,
In advance of the CTV meeting today, I wanted to share what my next step is
in advocating for CTV, as well as 7 theses for why I believe it to be the
right course of action to take at this time.
Please see the post at
https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/.
As always, open to hear any and all feedback,
Jeremy
archived at:
https://web.archive.org/web/20220419172825/https://rubin.io/bitcoin/2022/04/17/next-steps-bip119/
[-- Attachment #2: Type: text/html, Size: 1833 bytes --]
next reply other threads:[~2022-04-19 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-19 17:31 Jeremy Rubin [this message]
2022-04-20 13:24 ` Michael Folkson
2022-04-20 17:13 ` Robin Linus
2022-04-20 18:19 ` Michael Folkson
2022-04-20 19:46 ` Robin Linus
2022-04-20 22:04 ` Michael Folkson
2022-04-21 9:05 ` Robin Linus
2022-04-21 4:03 ` Billy Tetrud
2022-04-21 12:49 ` Zac Greenwood
2022-04-21 13:40 ` alicexbt
2022-04-21 14:16 ` Greg Sanders
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=CAD5xwhjVS4Y4e3qDWzJfva+0hiKpe8-WqmX_kUHrpfXmG5sMXw@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