Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.215.41 as permitted sender)
	client-ip=209.85.215.41; envelope-from=gmaxwell@gmail.com;
	helo=mail-la0-f41.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAD5xwhgyCOdJwnXw+YchptfXjtshDi_VVEGOjR-hG2qV=u6m2g@mail.gmail.com>
References: <CAD5xwhgyCOdJwnXw+YchptfXjtshDi_VVEGOjR-hG2qV=u6m2g@mail.gmail.com>
Date: Thu, 17 Jul 2014 13:08:24 -0700
Message-ID: <CAAS2fgQfuudYyOO7QPpLTMQBpsQqEDMnWRHDnm4xXx+wB6yKsw@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: Jeremy <jlrubin@mit.edu>
Content-Type: text/plain; charset=UTF-8
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Pay to MultiScript hash:
Precedence: list

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.