From: Ryan Breen <ryan@breen•xyz>
To: Michael Folkson <michaelfolkson@protonmail•com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Swift Activation - CTV
Date: Tue, 2 Jan 2024 11:24:06 -0500 [thread overview]
Message-ID: <5E185ABF-9F36-427D-B30D-D1E26D198469@breen.xyz> (raw)
In-Reply-To: <Zzpp9sp69_QmkUre4YUawBxOLECIfHHUf_OoD8UXXZ8Xwtmr5R62_rlGV2iwLivkST-vWusc0X9horY9qHEHKP2g4GR2ppCAuIE57VANUP0=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 1109 bytes --]
> On Jan 2, 2024, at 10:50 AM, Michael Folkson via bitcoin-dev <bitcoin-dev@lists•linuxfoundation.org> wrote:
>
> Your knowledge is incorrect. As far as I know in the getting on for 2 years since the first CTV activation talk/attempt literally no one has built out a CTV use case and demonstrated it on signet with the possible exception of James O'Beirne's OP_VAULT which requires other new opcodes in addition to CTV. I wish this wasn't the case. It is pitiful that we have these individuals (such as yourself) that are so convinced CTV should be activated but refuse to address any concerns raised by others and refuse to work on any of the speculated use cases, instead choosing to just beat the activation drum over and over again.
James O’Beirne built a CTV-only vault prototype[1], actually. Jeremy Rubin also built vaults and many other prototypes with his Sapio smart contracting language.[2]
So this assertion that CTV has had no use cases or prototypes built out for it is just not true.
[1]: https://github.com/jamesob/simple-ctv-vault
[2]: https://github.com/sapio-lang/sapio
[-- Attachment #2: Type: text/html, Size: 1778 bytes --]
next prev parent reply other threads:[~2024-01-02 16:30 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-12-20 1:44 alicexbt
2023-12-22 1:05 ` Luke Dashjr
2023-12-22 1:56 ` alicexbt
2023-12-22 22:34 ` alicexbt
2023-12-30 8:05 ` Anthony Towns
2023-12-30 8:59 ` Erik Aronesty
2024-01-01 16:37 ` Michael Folkson
2024-01-01 17:11 ` Erik Aronesty
2024-01-02 13:52 ` Michael Folkson
2024-01-02 14:32 ` Erik Aronesty
2024-01-02 16:24 ` Ryan Breen [this message]
2024-01-02 16:43 ` alicexbt
2023-12-30 13:54 ` Michael Folkson
2024-01-03 8:36 ` Anthony Towns
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=5E185ABF-9F36-427D-B30D-D1E26D198469@breen.xyz \
--to=ryan@breen$(echo .)xyz \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=michaelfolkson@protonmail$(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