From: Anthony Towns <aj@erisian•com.au>
To: Brandon Black <freedom@reardencode•com>
Cc: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] Covenants Support - Bitcoin Wiki
Date: Wed, 11 Dec 2024 23:28:42 +1000 [thread overview]
Message-ID: <Z1mTiguyy5waz4Vg@erisian.com.au> (raw)
In-Reply-To: <Z1dW77h3rhr5oivP@console>
On Mon, Dec 09, 2024 at 12:45:35PM -0800, Brandon Black wrote:
> First, my example scripts for Lightning Symmetry all use opcodes that do
> not exist in the script testing environments so I cannot run my scripts
> through those environments.
You've implemented your code against bitcoin inquisition 27.x [0],
which already includes an "evalscript" subcommand [1] that allows you
to do precisely that, even without updating the functional test suite
so that CI passes. So, yes, you can run your scripts through testing
environments.
You can also easily tweak your scripts to run them through unmodified
testing environments to at least ensure you aren't making trivial errors
and to check the stack is working the way you think it should -- replace
the new commands with OP_NOP (for things like CTV) or OP_2DROP OP_VERIFY
(for things like CHECKSIGVERIFY, where an empty signature would fail,
and there are two other arguments to ignore).
> The fact that I misglanced the opcode list
> during drafting is completely irrelevant to the exercise.
That you made a mistake is perhaps excusable, though as someone proposing
to modify the script language, being more than glancingly familiar with
script as it is today seems like a pretty basic expectation. That you
didn't put your work through even the most basic testing cycle before
publicising it isn't so excusable. [2]
It's utterly astounding to me that you're publicising your project
as "lnhance" [3] and yet are willing to be that careless in your
demonstrations of how it might enhance the lightning network.
Cheers,
aj
[0] https://github.com/bitcoin-inquisition/bitcoin/pull/45
[1] https://github.com/bitcoin-inquisition/bitcoin/pull/58
[2] For instance, I made a claim above that you can use evalscript
with your inquisition pr. That's something that I should test,
and when I do, it turns out there's a line that needs fixing to
make that work. Here's what it looks like after that's done,
checking the first entry in the bip340 test vectors:
```
$ ./bitcoin-util -sigversion=tapscript -script_flags=CHECKSIGFROMSTACK evalscript '0x200000000000000000000000000000000000000000000000000000000000000000 0x20F9308A019258C31049344F85F89D5229B531C845836F99B08601F113BCE036F9 CHECKSIGFROMSTACK' E907831F80848D1069A5371B402410364BDF1C5F8307B0084C55F1CE2DCA821525F66A4A85EA8B71E482A74F382D2CE5EBEEE8FDB2172F477DF4900D310536C0
{
"script": {
"asm": "0000000000000000000000000000000000000000000000000000000000000000 f9308a019258c31049344f85f89d5229b531c845836f99b08601f113bce036f9 OP_CHECKSIGFROMSTACK",
"hex": "20000000000000000000000000000000000000000000000000000000000000000020f9308a019258c31049344f85f89d5229b531c845836f99b08601f113bce036f9cc",
"type": "nonstandard"
},
"sigversion": "tapscript",
"script_flags": [
"CHECKSIGFROMSTACK"
],
"stack-after": [
"01"
],
"sigop-count": 0,
"success": true
}
```
[3] https://www.lnhance.org/#team
--
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/Z1mTiguyy5waz4Vg%40erisian.com.au.
next prev parent reply other threads:[~2024-12-11 13:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-29 14:08 /dev /fd0
2024-12-06 21:45 ` Jonas Nick
2024-12-07 0:29 ` /dev /fd0
2024-12-07 1:42 ` Yuval Kogman
2024-12-09 20:13 ` Anthony Towns
2024-12-09 20:45 ` Brandon Black
2024-12-11 13:28 ` Anthony Towns [this message]
2024-12-11 15:11 ` Brandon Black
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=Z1mTiguyy5waz4Vg@erisian.com.au \
--to=aj@erisian$(echo .)com.au \
--cc=bitcoindev@googlegroups.com \
--cc=freedom@reardencode$(echo .)com \
/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