From: "'moonsettler' via Bitcoin Development Mailing List" <bitcoindev@googlegroups.com>
To: Anthony Towns <aj@erisian•com.au>
Cc: Nadav Ivgi <nadav@shesek•info>, bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] "Recursive covenant" with CTV and CSFS
Date: Tue, 18 Mar 2025 20:29:57 +0000 [thread overview]
Message-ID: <NYpEviMeuCzkq09xeaXnKDBNDLjREe-7gJEKCHw5RiOo-fFntC4Ts6ainINIYpEh8CZdcVn9nNLApxbBTIl3jxkXs2zwtwPpPuOJHlbfKpQ=@protonmail.com> (raw)
In-Reply-To: <Z9ED_dez7_UHxjK0@erisian.com.au>
Hi All,
> You could have CTV commit to two inputs, with the second input's entire
> value being burnt to fees, but that's fairly annoying
Sometimes it's annoying, other times it enables new applications, because
it can force the submitter of the transaction to contribute to the output(s).
This could serve different uses like griefing deterrent (immortal statechains)
or collect yield from blind merged mining (surfchains).
BR,
moonsettler
On Wednesday, March 12th, 2025 at 4:48 AM, Anthony Towns <aj@erisian•com.au> wrote:
> On Mon, Mar 10, 2025 at 07:14:30AM +0200, Nadav Ivgi wrote:
>
> > For some historical context, it's interesting to note that CTV originally
> > had the constexpr requirement which prevented your CSFS+CTV construct by
> > requiring the CTV hash to come from a literal push preceding the opcode
> > (i.e. not dynamically computed/pre-verified and not from the witness). This
> > was eventually removed because it was deemed an unnecessary safeguard and
> > to simplify the implementation.
>
>
> I think the original COSHV implementation had the hash appear a push after
> the CTV opcode.
> https://github.com/JeremyRubin/bips/blob/op-checkoutputshashverify/bip-coshv.mediawiki
>
> > Also, it seems that APO alone also enables the same kind of construct as
> > what you're describing. For example, a 'recursive' APO signature spending
> > back to the same address could similarly be used as the basis for a BMM
> > Spacechain.
>
>
> With either APO or CTV alone you can do an arbitrarily long chain of commitments
> (with APO|SINGLE allowing you to add an input/output for fees and change when
> using those commitments), adding CSFS and discarding the CSFS private key allows
> you to have a single commitment that can be reused indefinitely.
>
> > Here's my go at it using Minsc:
> > https://min.sc/v0.3/#gist=3aa538b384d3aaf4282d1acaf943f608
>
>
> Nice!
>
> > Note however that what you described is creating 0-fee transactions, with
> > no way to attach additional fees.
>
>
> Yes; I don't think you can do a good job of that on mutinynet with just
> CTV/CSFS, since I don't think 0-value anchor outputs are supported. (You
> could have CTV commit to two inputs, with the second input's entire
> value being burnt to fees, but that's fairly annoying)
>
> Cheers,
> aj
>
> --
> 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/Z9ED_dez7_UHxjK0%40erisian.com.au.
--
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/NYpEviMeuCzkq09xeaXnKDBNDLjREe-7gJEKCHw5RiOo-fFntC4Ts6ainINIYpEh8CZdcVn9nNLApxbBTIl3jxkXs2zwtwPpPuOJHlbfKpQ%3D%40protonmail.com.
prev parent reply other threads:[~2025-03-18 21:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-05 0:01 Anthony Towns
2025-03-05 6:14 ` Olaoluwa Osuntokun
2025-03-05 16:14 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
2025-03-06 17:17 ` Greg Sanders
2025-03-06 18:36 ` 'moonsettler' via Bitcoin Development Mailing List
2025-03-06 21:26 ` Antoine Riard
2025-03-07 21:36 ` Anthony Towns
2025-03-07 21:01 ` Anthony Towns
2025-03-08 15:55 ` James O'Beirne
2025-03-11 1:06 ` Antoine Riard
2025-03-05 17:53 ` 'moonsettler' via Bitcoin Development Mailing List
2025-03-05 22:46 ` Antoine Riard
2025-03-07 21:16 ` Anthony Towns
2025-03-10 22:36 ` Antoine Riard
2025-03-10 5:14 ` Nadav Ivgi
2025-03-12 3:48 ` Anthony Towns
2025-03-12 10:02 ` Nadav Ivgi
2025-03-12 16:15 ` Nadav Ivgi
2025-03-14 3:20 ` Anthony Towns
2025-03-18 20:29 ` 'moonsettler' via Bitcoin Development Mailing List [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='NYpEviMeuCzkq09xeaXnKDBNDLjREe-7gJEKCHw5RiOo-fFntC4Ts6ainINIYpEh8CZdcVn9nNLApxbBTIl3jxkXs2zwtwPpPuOJHlbfKpQ=@protonmail.com' \
--to=bitcoindev@googlegroups.com \
--cc=aj@erisian$(echo .)com.au \
--cc=moonsettler@protonmail$(echo .)com \
--cc=nadav@shesek$(echo .)info \
/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