Received-SPF: pass (sog-mx-4.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.216.175 as permitted sender)
	client-ip=209.85.216.175; envelope-from=gmaxwell@gmail.com;
	helo=mail-qy0-f175.google.com; 
MIME-Version: 1.0
In-Reply-To: <CAAS2fgRRws5iG_oirKbgmyySZMZ4tzOC2Nq_12psqeuSH4GyDg@mail.gmail.com>
References: <CABsx9T2QzafV-uzn7yL01gs2mrzLaP0FCgjt_O--Ldw+s-Xm9w@mail.gmail.com>
	<CANEZrP2fqvivhnjSDsLiYdYJ09E7y+=EmsVH3BvLmA4tGri7bQ@mail.gmail.com>
	<CAAS2fgRCyppz27-_UhjLnK3a8=DBOVMixk1COv5-uYXGa6WuxA@mail.gmail.com>
	<CABsx9T1uxcyqk+Gxrkhb48moszNtCPVpKzuQdnFznr2ZtP_eiw@mail.gmail.com>
	<CAAS2fgRRws5iG_oirKbgmyySZMZ4tzOC2Nq_12psqeuSH4GyDg@mail.gmail.com>
Date: Fri, 30 Sep 2011 13:29:52 -0400
Message-ID: <CAAS2fgQG7iFPqSGNdCPCm=b11oHfsDW_d3NM472PJuvk-crjcA@mail.gmail.com>
From: Gregory Maxwell <gmaxwell@gmail.com>
To: bitcoin-development@lists.sourceforge.net
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Subject: Re: [Bitcoin-development] Multisignature transations
Precedence: list

On Fri, Sep 30, 2011 at 1:21 PM, Gavin Andresen <gavinandresen@gmail.com> w=
rote:
> Accepting this does not preclude adding more 'standard' transaction
> types in the future.

I think 2 of 3 is a _far_ more useful example than (a or b), =C2=A0it is
the prototype for a normal escrow transaction., and still only results
in three address and at most two signatures like the (A and B) or C
case.

You can also replicate the functionality of (a or b) in a hashish and
inefficient sort of way with two of three by simply using a public
known key as one of the roles.