From: Gregory Maxwell <gmaxwell@gmail•com>
To: Jeremy <jlrubin@mit•edu>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Pay to MultiScript hash:
Date: Thu, 17 Jul 2014 13:08:24 -0700 [thread overview]
Message-ID: <CAAS2fgQfuudYyOO7QPpLTMQBpsQqEDMnWRHDnm4xXx+wB6yKsw@mail.gmail.com> (raw)
In-Reply-To: <CAD5xwhgyCOdJwnXw+YchptfXjtshDi_VVEGOjR-hG2qV=u6m2g@mail.gmail.com>
On Wed, Jul 16, 2014 at 10:56 AM, Jeremy <jlrubin@mit•edu> wrote:
> Hey all,
> I had an idea for a new transaction type. The base idea is that it is
> matching on script hashes much like pay to script hash, but checks for one
> of N scripts.
This seems strictly less flexible and efficient than the Merkelized
Abstract Syntax Tree construction, though perhaps slightly easier to
implement it wouldn't be any easier to deploy.
Something like this was very recently proposed on this list (by Tier
Nolan), you might want to see the "Selector Script" thread.
prev parent reply other threads:[~2014-07-17 20:08 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
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 [this message]
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=CAAS2fgQfuudYyOO7QPpLTMQBpsQqEDMnWRHDnm4xXx+wB6yKsw@mail.gmail.com \
--to=gmaxwell@gmail$(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