Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1R9hLG-0006Bl-6Y for bitcoin-development@lists.sourceforge.net; Fri, 30 Sep 2011 17:57:46 +0000 Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.215.175 as permitted sender) client-ip=209.85.215.175; envelope-from=gavinandresen@gmail.com; helo=mail-ey0-f175.google.com; Received: from mail-ey0-f175.google.com ([209.85.215.175]) by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1R9hLF-0000AL-79 for bitcoin-development@lists.sourceforge.net; Fri, 30 Sep 2011 17:57:46 +0000 Received: by eya25 with SMTP id 25so1782732eya.34 for ; Fri, 30 Sep 2011 10:57:39 -0700 (PDT) MIME-Version: 1.0 Received: by 10.223.45.140 with SMTP id e12mr11689544faf.27.1317405458935; Fri, 30 Sep 2011 10:57:38 -0700 (PDT) Received: by 10.152.25.105 with HTTP; Fri, 30 Sep 2011 10:57:38 -0700 (PDT) In-Reply-To: References: Date: Fri, 30 Sep 2011 13:57:38 -0400 Message-ID: From: Gavin Andresen To: Gregory Maxwell , Bitcoin Dev Content-Type: text/plain; charset=ISO-8859-1 X-Spam-Score: -1.6 (-) 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 (gavinandresen[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 AWL AWL: From: address is in the auto white-list X-Headers-End: 1R9hLF-0000AL-79 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:57:46 -0000 RE: 2 of 3 being far more useful: So create a clean pull request, unit tests, and test plan for an "IsStandard" 2-of-3 transaction, either using CHECKMULTISIG or groffers proposal: 0 OVER 2SWAP CHECKSIG SWAP HASH160 {pk1hash} EQUAL BOOLAND ADD OVER 2SWAP CHECKSIG SWAP HASH160 {pk2hash} EQUAL BOOLAND ADD OVER 2SWAP CHECKSIG SWAP HASH160 {pk3hash} EQUAL BOOLAND ADD 2 GREATERTHANOREQUAL The low-level support is relatively easy, reporting these transactions in listtransactions and figuring out if or how to report them in your wallet balance is tricky. I generated and then spent three multisig transactions on testnet: http://blockexplorer.com/testnet/block/0000000000cfe382f690777e3b52ea255717122465db6fcfd80efdf2d0080d8b Code I used to send them is: https://github.com/gavinandresen/bitcoin-git/tree/multisig_testing (that code is NOT intended for mainline bitcoin, I just needed a way of testing the new transactions). -- -- Gavin Andresen