From: Salvatore Ingala <salvatore.ingala@gmail•com>
To: "David A. Harding" <dave@dtrt•org>
Cc: Bitcoin Protocol Discussion <bitcoin-dev@lists•linuxfoundation.org>
Subject: Re: [bitcoin-dev] Concrete MATT opcodes
Date: Mon, 7 Aug 2023 10:31:40 +0200 [thread overview]
Message-ID: <CAMhCMoEcxJc4Ov3iQyahaBtEcpGmFqN4k2Kg78_2vPXn8B8JQA@mail.gmail.com> (raw)
In-Reply-To: <99A6BB96-50B4-4894-9EFD-E36047D890E3@dtrt.org>
[-- Attachment #1: Type: text/plain, Size: 1056 bytes --]
Hi Dave,
I apologize for the confusion and the inconsistent use of plurals.
The reason I called it a "complete proposal" is that the opcode is
now functionally complete, unlike the previous attempt where the
approach for the output amount introspection was not yet specified.
The semantics are informally defined in the previous e-mail, and
implemented in the code [1], which is the only formal specification
at this time. I believe the code is now fairly stable and ready to
experiment with.
My own and (hopefully) others' experimentation will help in writing
a more informed BIP proposal in the next few months.
About the plurals: OP_CHECKCONTRACTVERIFY is indeed now a single
opcode that is useful on its own, but I will also be maintaining a
separate branch [2] that contains both OP_CHECKCONTRACTVERIFY and
OP_CAT, which enables the full generality of the MATT proposal.
Best,
Salvatore
[1] -
https://github.com/bitcoin-inquisition/bitcoin/compare/24.0...Merkleize:bitcoin:checkcontractverify
[2] - https://github.com/Merkleize/bitcoin/tree/matt
[-- Attachment #2: Type: text/html, Size: 1406 bytes --]
next prev parent reply other threads:[~2023-08-07 8:32 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 21:37 Salvatore Ingala
2023-08-06 20:13 ` David A. Harding
2023-08-07 8:31 ` Salvatore Ingala [this message]
2023-08-07 11:37 ` Johan Torås Halseth
2023-08-09 8:38 ` Salvatore Ingala
2023-08-14 3:00 ` Antoine Riard
2023-08-14 14:07 ` symphonicbtc
2023-08-18 20:12 ` Antoine Riard
2023-08-19 23:11 ` symphonicbtc
2023-09-13 20:25 ` Antoine Riard
2023-08-18 15:08 ` Salvatore Ingala
2023-09-15 0:23 ` Antoine Riard
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=CAMhCMoEcxJc4Ov3iQyahaBtEcpGmFqN4k2Kg78_2vPXn8B8JQA@mail.gmail.com \
--to=salvatore.ingala@gmail$(echo .)com \
--cc=bitcoin-dev@lists$(echo .)linuxfoundation.org \
--cc=dave@dtrt$(echo .)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