From: Jonas Nick <jonasdnick@gmail.com>
To: Lloyd Fournier <lloyd.fourn@gmail.com>,
dlc-dev@mailmanlists.org,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] [dlc-dev] CTV dramatically improves DLCs
Date: Tue, 25 Jan 2022 16:24:21 +0000 [thread overview]
Message-ID: <2b316504-f785-b1b3-9ff9-8d781d6c0d9b@gmail.com> (raw)
In-Reply-To: <CAH5Bsr2vxL3FWXnJTszMQj83jTVdRvvuVpimEfY7JpFCyP1AZA@mail.gmail.com>
Thank you, that's an interesting application of OP_CTV.
Perhaps worth pointing out that this does not require OP_CTV but could also be
enabled by other covenant constructions. For example, it seems like
ANYPREVOUT-based covenants provide similar benefits. The script of the Taproot
leaves could be set to
<sig> <G> CHECKSIGVERIFY <CET_i> CHECKSIGVERIFY
where <sig> is an ANYPREVOUTANYSCRIPT signature of the CET for public key P = G.
When using nonce R = G, signature creation has negligible computational cost (s
= 1 + H(R, P, m)). A downside compared to CTV is the additional overhead of 64
witness bytes (<sig>).
next prev parent reply other threads:[~2022-01-25 16:23 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-24 8:01 [bitcoin-dev] CTV dramatically improves DLCs Lloyd Fournier
2022-01-25 16:24 ` Jonas Nick [this message]
2022-01-27 0:45 ` [bitcoin-dev] [dlc-dev] " Thibaut Le Guilly
2022-01-28 16:53 ` Jeremy
2022-01-28 17:21 ` [bitcoin-dev] " Jeremy
2022-01-28 19:38 ` Jeremy Rubin
2022-01-28 21:14 ` Alex Schoof
2022-02-06 7:18 ` Lloyd Fournier
2022-02-06 17:56 ` Jeremy Rubin
2022-02-07 2:30 ` Thibaut Le Guilly
2022-03-15 17:28 ` Jeremy Rubin
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=2b316504-f785-b1b3-9ff9-8d781d6c0d9b@gmail.com \
--to=jonasdnick@gmail.com \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=dlc-dev@mailmanlists.org \
--cc=lloyd.fourn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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