From: "David A. Harding" <dave@dtrt.org>
To: Salvatore Ingala <salvatore.ingala@gmail.com>,
Bitcoin Protocol Discussion
<bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] Concrete MATT opcodes
Date: Sun, 06 Aug 2023 10:13:25 -1000 [thread overview]
Message-ID: <99A6BB96-50B4-4894-9EFD-E36047D890E3@dtrt.org> (raw)
In-Reply-To: <CAMhCMoFYF+9NL1sqKfn=ma3C_mfQv7mj2fqbqO5WXVwd6vyhLw@mail.gmail.com>
On July 30, 2023 11:37:49 AM HST, Salvatore Ingala via bitcoin-dev
>I have put together a first complete proposal for the core opcodes of
>MATT [1][2].
>The changes make the opcode functionally complete, and the
>implementation is revised and improved.
> [...]
>[1] - https://merkle.fun/
>[2] -
>https://lists.linuxfoundation.org/pipermail/bitcoin-dev/2022-November/021182.html
Hi Salvatore,
Where exactly is the proposal? Merkle.fun links to a "WIP" comment that seems to specify OP_CHECKCONTRACTVERIFY but your text above says "core opcodes" (plural) so I feel like I'm missing something. Also, it being "WIP" makes me wonder if that actually is the "complete proposal" I should be looking for.
When I read "complete proposal", I was expecting a draft BIP.
-Dave
next prev parent reply other threads:[~2023-08-06 20:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 21:37 [bitcoin-dev] Concrete MATT opcodes Salvatore Ingala
2023-08-06 20:13 ` David A. Harding [this message]
2023-08-07 8:31 ` Salvatore Ingala
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=99A6BB96-50B4-4894-9EFD-E36047D890E3@dtrt.org \
--to=dave@dtrt.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
--cc=salvatore.ingala@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