From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-4.v43.ch3.sourceforge.com ([172.29.43.194] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R9guN-0005Lz-21 for bitcoin-development@lists.sourceforge.net; Fri, 30 Sep 2011 17:29:59 +0000 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; Received: from mail-qy0-f175.google.com ([209.85.216.175]) by sog-mx-4.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R9guM-0002s2-EX for bitcoin-development@lists.sourceforge.net; Fri, 30 Sep 2011 17:29:59 +0000 Received: by qyk10 with SMTP id 10so689062qyk.13 for ; Fri, 30 Sep 2011 10:29:53 -0700 (PDT) MIME-Version: 1.0 Received: by 10.229.226.209 with SMTP id ix17mr9103251qcb.147.1317403792799; Fri, 30 Sep 2011 10:29:52 -0700 (PDT) Received: by 10.229.214.144 with HTTP; Fri, 30 Sep 2011 10:29:52 -0700 (PDT) In-Reply-To: References: Date: Fri, 30 Sep 2011 13:29:52 -0400 Message-ID: From: Gregory Maxwell To: bitcoin-development@lists.sourceforge.net Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Spam-Score: -1.4 (-) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gmaxwell[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.0 T_TO_NO_BRKTS_FREEMAIL To: misformatted and free email service 0.2 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R9guM-0002s2-EX Subject: Re: [Bitcoin-development] Multisignature transations X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 30 Sep 2011 17:29:59 -0000 On Fri, Sep 30, 2011 at 1:21 PM, Gavin Andresen 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.