From: Murch <murch@murch•one>
To: bitcoindev@googlegroups.com
Subject: Re: [bitcoindev] CHECKSIGFROMSTACK(VERIFY/ADD)
Date: Fri, 15 Nov 2024 09:57:13 -0500 [thread overview]
Message-ID: <c91269ac-e579-4089-bf9a-fdc076e34727@murch.one> (raw)
In-Reply-To: <ZzZziZOy4IrTNbNG@console>
Hi everyone,
On 2024-11-14 17:02, Brandon Black wrote:
> * Should CHECKSIGFROMSTACKVERIFY (CSFSV) be added to pre-tapscript
> […]
> My personal thinking in initially including CSFSV in earlier script versions was basically that it's compatible with NOP forking, so why not.
If there is no compelling use case or concrete benefit, I don’t think "it’s compatible, why not" is convincing motivation, especially at the cost of a NOP.
On 2024-11-14 17:02, Brandon Black wrote:
> * Should we include CHECKSIGFROMSTACKADD?
I feel similar about this. If there is currently no demand for this, and future demand also seems unlikely, I would prefer a smaller, more focused set of changes.
Cheers,
Murch
--
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/c91269ac-e579-4089-bf9a-fdc076e34727%40murch.one.
next prev parent reply other threads:[~2024-11-15 15:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-14 22:02 Brandon Black
2024-11-15 10:14 ` 'moonsettler' via Bitcoin Development Mailing List
2024-11-15 14:57 ` Murch [this message]
2024-11-15 15:33 ` 'Antoine Poinsot' via Bitcoin Development Mailing List
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=c91269ac-e579-4089-bf9a-fdc076e34727@murch.one \
--to=murch@murch$(echo .)one \
--cc=bitcoindev@googlegroups.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