From: Anthony Towns <aj@erisian•com.au>
To: Matt Corallo <lf-lists@mattcorallo•com>
Cc: Antoine Poinsot <darosior@protonmail•com>,
Bitcoin Development Mailing List <bitcoindev@googlegroups.com>
Subject: Re: [bitcoindev] What's a good stopping point? Making the case for the capabilities enabled by CTV+CSFS
Date: Thu, 3 Jul 2025 13:55:28 +1000 [thread overview]
Message-ID: <aGX_MNORQVQT_lp4@erisian.com.au> (raw)
In-Reply-To: <8a9a2299-ab4b-45a4-8b9d-95798e6bb62a@mattcorallo.com>
On Tue, Jun 24, 2025 at 11:54:02AM -0400, Matt Corallo wrote:
> > which
> > warrants a compelling demonstration that arbitrary transaction introspection
> > does enable important use cases not achievable with more minimal capabilities.
> I'm somewhat skeptical that showing this isn't rather simple,
I think the BitVM/CTV idea posted on delving [0] is one such simple demo?
I gave an example in that thread of how you'd implement the desired
construct using bllsh's introspection primitives, but the same could
equally well be done with Rusty's as-yet unpublished OP_TX, something
like:
DUP 0x1011 TX 0x00000002 EQUALVERIFY 0x1009 TX 0x0809 TX EQUALVERIFY
where:
* "0x1011 TX" pops an input index from the stack and gives the four-byte
vout index of that input's prevout
* "0x1009 TX" pops an input index from the stack and gives the txid of that input's
prevout
* "0x0809 TX" gives the txid of the current input's prevout
(this encodes "this utxo can only be spent (via this path) if its sibling
output at index 2 is also being spent in the same transaction")
Cheers,
aj
[0] https://delvingbitcoin.org/t/how-ctv-csfs-improves-bitvm-bridges/1591
--
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/aGX_MNORQVQT_lp4%40erisian.com.au.
prev parent reply other threads:[~2025-07-03 8:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-23 13:14 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-24 14:29 ` [bitcoindev] " Harsha Goli
2025-06-24 15:54 ` [bitcoindev] " Matt Corallo
2025-06-25 16:50 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-06-25 20:34 ` Ethan Heilman
2025-06-26 16:02 ` Josh Doman
2025-06-26 17:03 ` Greg Sanders
2025-06-29 22:50 ` Antoine Riard
2025-06-25 19:22 ` Chris Stewart
2025-07-03 3:55 ` Anthony Towns [this message]
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=aGX_MNORQVQT_lp4@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoindev@googlegroups.com \
--cc=darosior@protonmail$(echo .)com \
--cc=lf-lists@mattcorallo$(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