From: Jeremy Rubin <jeremy.l.rubin@gmail•com>
To: Anthony Towns <aj@erisian•com.au>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] CTV Signet Parameters
Date: Thu, 28 Apr 2022 05:23:32 -0700 [thread overview]
Message-ID: <CAD5xwhg70tBHPL1yx0p6ePnhaWYMjSwzYZwihaJES3wUdnHY_Q@mail.gmail.com> (raw)
In-Reply-To: <20220420023107.GA6061@erisian.com.au>
[-- Attachment #1: Type: text/plain, Size: 924 bytes --]
Sorry I didn't see this snippet fully earlier, but I caught it in Optech
(cc harding)
> *(I didn't think DROP/1 is necessary here? Doesn't leaving the 32 byte*
> *hash on the stack evaluate as true? I guess that means everyone's using**sapio to
> construct the txs?)*
Not quite: it would mean that everyone is using *sapio-miniscript**, *which
may or may not be in Sapio, or they are using a different miniscript
implementation that is compatible with sapio-miniscript's CTV fragment
(which is sort of the most obvious way to implement it), or they are hand
writing the script and are still using that fragment.
E.g., you can see
https://min.sc/nextc/#gist=001cf1fcb0e24ca9f3614c4db9bfe57d:2 or
https://min.sc/nextc/#gist=001cf1fcb0e24ca9f3614c4db9bfe57d:0 both of these
might "look" like sapio, but are built using minsc.
The underlying point might still stand, but using miniscript seems
different than using Sapio.
[-- Attachment #2: Type: text/html, Size: 2632 bytes --]
next prev parent reply other threads:[~2022-04-28 12:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-17 21:58 Jeremy Rubin
2022-02-18 11:13 ` 0x0ff
2022-02-22 3:19 ` Jeremy Rubin
2022-04-20 2:31 ` Anthony Towns
2022-04-20 17:05 ` Nadav Ivgi
2022-04-21 2:36 ` Anthony Towns
2022-04-28 12:23 ` Jeremy Rubin [this message]
2022-04-20 17:13 Buck O Perley
2022-04-21 5:03 ` Anthony Towns
2022-04-21 6:16 ` Jeremy Rubin
2022-04-21 6:25 ` Jeremy Rubin
2022-04-21 13:22 ` Russell O'Connor
2022-04-21 15:05 ` Jeremy Rubin
2022-04-22 0:58 ` Anthony Towns
2022-04-22 1:10 ` Nadav Ivgi
2022-04-22 5:30 ` 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=CAD5xwhg70tBHPL1yx0p6ePnhaWYMjSwzYZwihaJES3wUdnHY_Q@mail.gmail.com \
--to=jeremy.l.rubin@gmail$(echo .)com \
--cc=aj@erisian$(echo .)com.au \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
/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