From: Jeff Garzik <jgarzik@bitpay•com>
To: Jeremy <jlrubin@mit•edu>
Cc: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Pay to MultiScript hash:
Date: Thu, 17 Jul 2014 00:52:14 -0400 [thread overview]
Message-ID: <CAJHLa0OFEDQp5umz=6_LUx5oJJmiKJoF90W7nvJPv0CtML+ftA@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhgyCOdJwnXw+YchptfXjtshDi_VVEGOjR-hG2qV=u6m2g@mail.gmail.com>
On Wed, Jul 16, 2014 at 1:56 PM, Jeremy <jlrubin@mit•edu> wrote:
> Right now, this could be expressed multiple ways (ie, using an op_dup if
> then else chain) , but all would incur additional costs in terms of
> complicated control flows. Instead, I would propose:
Can you quantify "additional costs in terms of complicated control flows"?
> There is an implication in terms of increased utxo pool bloat, but also an
> implication in terms of increased txn complexity (each 20 byte hash allows
> for a 500 byte script, only one of the 500 byte scripts has to be
> permanently stored on blockchain).
When considering these costs, using a normal P2SH output + a script
with OP_IF and friends seems more straightforward?
Doing boolean logic with multisig groups is quite possible, e.g.
"group AND group", "group OR (group AND group)" etc. Definitely a
valid use case. I discussed how to do this on IRC with gmaxwell
several months ago. I call it "multi-multisig" for lack of a better
name.
next prev parent reply other threads:[~2014-07-17 4:52 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-16 17:56 Jeremy
2014-07-17 4:52 ` Jeff Garzik [this message]
2014-07-17 5:59 ` Jeremy
2014-07-17 6:21 ` Jeff Garzik
2014-07-17 19:55 ` Jeremy
2014-07-17 20:08 ` Gregory Maxwell
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='CAJHLa0OFEDQp5umz=6_LUx5oJJmiKJoF90W7nvJPv0CtML+ftA@mail.gmail.com' \
--to=jgarzik@bitpay$(echo .)com \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=jlrubin@mit$(echo .)edu \
/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