Received: from sog-mx-2.v43.ch3.sourceforge.com ([172.29.43.192] helo=mx.sourceforge.net) by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1UFBlB-0001hW-UG for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 23:04:01 +0000 Received-SPF: pass (sog-mx-2.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.216.53 as permitted sender) client-ip=209.85.216.53; envelope-from=jtimonmv@gmail.com; helo=mail-qa0-f53.google.com; Received: from mail-qa0-f53.google.com ([209.85.216.53]) by sog-mx-2.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1UFBlA-0001OJ-R2 for bitcoin-development@lists.sourceforge.net; Mon, 11 Mar 2013 23:04:01 +0000 Received: by mail-qa0-f53.google.com with SMTP id z4so1284015qan.19 for ; Mon, 11 Mar 2013 16:03:55 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.224.213.134 with SMTP id gw6mr19781067qab.72.1363043035308; Mon, 11 Mar 2013 16:03:55 -0700 (PDT) Received: by 10.49.11.140 with HTTP; Mon, 11 Mar 2013 16:03:55 -0700 (PDT) Date: Tue, 12 Mar 2013 00:03:55 +0100 Message-ID: From: =?ISO-8859-1?B?CUpvcmdlIFRpbfNu?= To: 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 (jtimonmv[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 X-Headers-End: 1UFBlA-0001OJ-R2 Subject: [Bitcoin-development] Can this tx be formed? 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: Mon, 11 Mar 2013 23:04:02 -0000 Say Alice signs and broadcasts a tx with input Ai, with SIGHASH_SINGLE to Ao and SIGHASH_ANYONECANPAY Bob signs and broadcasts a tx with input Bi, with SIGHASH_SINGLE to Bo and SIGHASH_ANYONECANPAY Can Carol complete the tx so that it is valid to be published in the chain? It only has to make Ai + Bi + Ci + F = Ao + Bo + Co but it all must be contained in a single transaction.