From: Billy <fresheneesz@gmail•com>
To: bitcoin-dev@lists•linuxfoundation.org
Subject: [bitcoin-dev] op_checktemplateverify and number of inputs
Date: Fri, 24 Jan 2020 17:50:49 -0800 [thread overview]
Message-ID: <CAGpPWDYYYYEeuQVL6d97_OwN_f8ektdqv-5zXVT9fEqiS6qtoQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
I have a question about op_ctv related to the requirement to specify the
number of inputs. I don't quite see why its necessary, but most
importantly, I don't see why we want to *require* the user of the op to
specify the number of inputs, tho I see the reasoning why one would want to
specify it. If the op allowed both cases (specifying a number of inputs and
allowing any number), it seems like the best of both worlds. I started a
discussion on bitcointalk.org:
https://bitcointalk.org/index.php?topic=5220520
[-- Attachment #2: Type: text/html, Size: 709 bytes --]
next reply other threads:[~2020-01-25 1:51 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-25 1:50 Billy [this message]
2020-01-26 17:23 ` Jeremy
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=CAGpPWDYYYYEeuQVL6d97_OwN_f8ektdqv-5zXVT9fEqiS6qtoQ@mail.gmail.com \
--to=fresheneesz@gmail$(echo .)com \
--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