From: Matt Corallo <lf-lists@mattcorallo•com>
To: Jameson Lopp <jameson.lopp@gmail•com>
Cc: Andrew Poelstra <apoelstra@wpsoftware•net>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] CTV + CSFS: a letter
Date: Fri, 13 Jun 2025 08:36:47 -0400 [thread overview]
Message-ID: <4f99a0b9-a8d6-49dd-adc5-b7d8d587b820@mattcorallo.com> (raw)
In-Reply-To: <CADL_X_fxwKLdst9tYQqabUsJgu47xhCbwpmyq97ZB-SLWQC9Xw@mail.gmail.com>
Thanks Jameson.
I think this is a much more valuable contribution to encouraging developers to work on covenants
than some other parts of this thread.
Is there a specific protocol utilizing covenants that you wish to implement at Casa (I assume Vaults
maybe, but can you sketch the high-level setup and considerations)?
Thanks,
Matt
On 6/13/25 7:08 AM, Jameson Lopp wrote:
> > Unlike a generic "We Want Things" sign-on letter, individual messages indicating desire to
> utilize features is way more compelling.
>
> Then I submit my essay from 2 years ago (https://blog.casa.io/why-bitcoin-needs-covenants/ <https://
> blog.casa.io/why-bitcoin-needs-covenants/>) and will quote myself:
>
> "There are clearly a LOT of use cases that could potentially be unlocked with the right kind of
> covenant implementation. Personally, having spent 8 years working on high security multi-signature
> wallets, I'm most interested in vaults. I believe the value they offer is quite straightforward and
> is applicable to every single self-custody bitcoin user, regardless of what type of wallet they are
> running."
>
> - Jameson
>
> On Thu, Jun 12, 2025 at 6:54 PM Matt Corallo <lf-lists@mattcorallo•com <mailto:lf-
> lists@mattcorallo•com>> wrote:
>
> To be fair to James, in my (luckily rather brief) experience with Bitcoin-consensus-letter-writing,
> its nearly impossible to forge a statement that everyone agrees to that is consistently interpreted.
>
> Matt
>
> On 6/12/25 3:51 PM, Andrew Poelstra wrote:
> > Le Thu, Jun 12, 2025 at 02:38:13PM -0400, James O'Beirne a écrit :
> >>
> >> As the person who coordinated the letter, I can say that this is not an
> >> accurate characterization of the signers' intent. Everyone who signed
> >> explicitly wants to see the imminent review, integration, and activation
> >> planning for CTV+CSFS specifically. The letter is intentionally concise to
> >> make sure there are no misunderstandings about that.
> >>
> >> I spoke to each person on the original list of signatories who either did
> >> (or didn't) sign and this was made very clear. Some people didn't sign as a
> >> result of what the letter says.
> >>
> >
> > The letter asks Core to "prioritize the review and integration" on an
> > accelerated timeline, and that this will "allow" for "activation planning".
> >
> > Early drafts of the letter did ask for actual integration and even
> > activation, but I did not sign any of those early drafts. It was not
> > until the language was weakened to be about priorities and planning (and
> > to be a "respectful ask" rather some sort of demand) that I signed on.
> >
> >
> > The letter is concise but unfortunately I think Matt is correct that it
> > offers a broad range of interpretations, even among the signers.
> >
> >
>
> --
> You received this message because you are subscribed to the Google Groups "Bitcoin Development
> Mailing List" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to
> bitcoindev+unsubscribe@googlegroups•com <mailto:bitcoindev%2Bunsubscribe@googlegroups•com>.
> To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/f8b37a59-0897-40df-
> a08e-7812c806a716%40mattcorallo.com <https://groups.google.com/d/msgid/bitcoindev/
> f8b37a59-0897-40df-a08e-7812c806a716%40mattcorallo.com>.
>
--
You received this message because you are subscribed to the Google Groups "Bitcoin Development Mailing List" group.
To unsubscribe from this group and stop receiving emails from it, send an email to bitcoindev+unsubscribe@googlegroups•com.
To view this discussion visit https://groups.google.com/d/msgid/bitcoindev/4f99a0b9-a8d6-49dd-adc5-b7d8d587b820%40mattcorallo.com.
next prev parent reply other threads:[~2025-06-13 12:39 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-09 11:40 James O'Beirne
2025-06-09 12:51 ` Michael Folkson
2025-06-09 14:41 ` James O'Beirne
2025-06-09 15:56 ` Michael Folkson
2025-06-09 13:51 ` Matt Corallo
2025-06-09 14:43 ` James O'Beirne
2025-06-09 17:51 ` Matt Corallo
2025-06-09 19:27 ` /dev /fd0
2025-06-09 21:12 ` Matt Corallo
2025-06-09 18:55 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 2:02 ` Paul Sztorc
2025-06-09 23:02 ` Andrew Poelstra
2025-06-10 2:08 ` David A. Harding
2025-06-10 13:23 ` Andrew Poelstra
2025-06-10 17:17 ` Matt Corallo
2025-06-10 23:42 ` Antoine Riard
2025-06-12 3:34 ` James O'Beirne
2025-06-13 1:18 ` Antoine Riard
2025-06-10 23:42 ` Antoine Riard
2025-06-11 13:52 ` Peter Todd
2025-06-13 6:19 ` Anthony Towns
2025-06-13 14:50 ` Harsha Goli
2025-06-10 14:03 ` James O'Beirne
2025-06-10 16:56 ` Sjors Provoost
2025-06-10 17:15 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-10 19:04 ` Paul Sztorc
2025-06-11 18:09 ` Brandon Black
2025-06-10 2:28 ` Melvin Carvalho
2025-06-10 13:19 ` Greg Sanders
2025-06-11 14:12 ` James O'Beirne
[not found] ` <CAB3F3Dsf8=rbOyPf1yTQDzyQQX6FAoJWTg16VC8PVs4_uBkeTw@mail.gmail.com>
2025-06-11 16:50 ` James O'Beirne
2025-06-11 18:34 ` James O'Beirne
2025-06-11 20:30 ` Matt Corallo
2025-06-12 0:59 ` Harsha Goli
2025-06-12 18:04 ` Matt Corallo
2025-06-12 18:38 ` James O'Beirne
2025-06-12 18:43 ` Matt Corallo
2025-06-12 19:51 ` Andrew Poelstra
2025-06-12 22:44 ` Matt Corallo
2025-06-13 11:08 ` Jameson Lopp
2025-06-13 12:36 ` Matt Corallo [this message]
2025-06-13 13:07 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-13 15:41 ` Jameson Lopp
2025-06-13 5:50 ` Anthony Towns
2025-06-12 2:06 ` Greg Maxwell
2025-06-12 3:23 ` James O'Beirne
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=4f99a0b9-a8d6-49dd-adc5-b7d8d587b820@mattcorallo.com \
--to=lf-lists@mattcorallo$(echo .)com \
--cc=apoelstra@wpsoftware$(echo .)net \
--cc=bitcoindev@googlegroups.com \
--cc=jameson.lopp@gmail$(echo .)com \
/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