Received: from sog-mx-1.v43.ch3.sourceforge.com ([172.29.43.191]
	helo=mx.sourceforge.net)
	by sfs-ml-4.v29.ch3.sourceforge.com with esmtp (Exim 4.76)
	(envelope-from <mh.in.england@gmail.com>) id 1TFT8j-0000QK-UB
	for bitcoin-development@lists.sourceforge.net;
	Sat, 22 Sep 2012 17:05:13 +0000
Received-SPF: pass (sog-mx-1.v43.ch3.sourceforge.com: domain of gmail.com
	designates 209.85.212.181 as permitted sender)
	client-ip=209.85.212.181; envelope-from=mh.in.england@gmail.com;
	helo=mail-wi0-f181.google.com; 
Received: from mail-wi0-f181.google.com ([209.85.212.181])
	by sog-mx-1.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128)
	(Exim 4.76) id 1TFT8f-00061a-Mn
	for bitcoin-development@lists.sourceforge.net;
	Sat, 22 Sep 2012 17:05:13 +0000
Received: by wibhm2 with SMTP id hm2so2379377wib.10
	for <bitcoin-development@lists.sourceforge.net>;
	Sat, 22 Sep 2012 10:05:03 -0700 (PDT)
MIME-Version: 1.0
Received: by 10.181.13.239 with SMTP id fb15mr2342111wid.22.1348333503513;
	Sat, 22 Sep 2012 10:05:03 -0700 (PDT)
Sender: mh.in.england@gmail.com
Received: by 10.216.139.134 with HTTP; Sat, 22 Sep 2012 10:05:03 -0700 (PDT)
In-Reply-To: <CAGQP0AEnkRqiEb2_COpQpLKkZfHf0fFgHmquO5oY4_Gh84k7cA@mail.gmail.com>
References: <CA+8xBpczY1DkgmHsVL8m30JaM1d+FwN_gpBhq6DFScm1nvLF5w@mail.gmail.com>
	<CAGQP0AEnkRqiEb2_COpQpLKkZfHf0fFgHmquO5oY4_Gh84k7cA@mail.gmail.com>
Date: Sat, 22 Sep 2012 19:05:03 +0200
X-Google-Sender-Auth: zytwWoMs5AzXfbchYQ0TN9z0xh0
Message-ID: <CANEZrP257oD26WkYNr4fXuMOkURstsiuA0NoD92gBxViyf9xWw@mail.gmail.com>
From: Mike Hearn <mike@plan99.net>
To: =?UTF-8?B?Sm9yZ2UgVGltw7Nu?= <timon.elviejo@gmail.com>
Content-Type: multipart/alternative; boundary=f46d043c7dd684042904ca4d5b13
X-Spam-Score: -0.5 (/)
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
	(mh.in.england[at]gmail.com)
	-0.0 SPF_PASS               SPF: sender matches SPF record
	1.0 HTML_MESSAGE           BODY: HTML included in message
	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: 1TFT8f-00061a-Mn
Cc: Bitcoin Development <bitcoin-development@lists.sourceforge.net>
Subject: Re: [Bitcoin-development] Atomic coin swapping?
X-BeenThere: bitcoin-development@lists.sourceforge.net
X-Mailman-Version: 2.1.9
Precedence: list
List-Id: <bitcoin-development.lists.sourceforge.net>
List-Unsubscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=unsubscribe>
List-Archive: <http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development>
List-Post: <mailto:bitcoin-development@lists.sourceforge.net>
List-Help: <mailto:bitcoin-development-request@lists.sourceforge.net?subject=help>
List-Subscribe: <https://lists.sourceforge.net/lists/listinfo/bitcoin-development>,
	<mailto:bitcoin-development-request@lists.sourceforge.net?subject=subscribe>
X-List-Received-Date: Sat, 22 Sep 2012 17:05:14 -0000

--f46d043c7dd684042904ca4d5b13
Content-Type: text/plain; charset=UTF-8

>
> Why "Signing the input scripts as well would obviously make it
> impossible to construct a transaction"?


As it states in the source code, signatures cannot sign themselves.  If
scriptSigs were included in the data that is being signed, the act of
inserting the newly calculated signature for one input would break the
signatures for all the others.

--f46d043c7dd684042904ca4d5b13
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

<div class=3D"gmail_quote"><blockquote class=3D"gmail_quote" style=3D"margi=
n:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Why &quot;Signing=
 the input scripts as well would obviously make it<br>
impossible to construct a transaction&quot;?</blockquote><div><br></div><di=
v>As it states in the source code, signatures cannot sign themselves. =C2=
=A0If scriptSigs were included in the data that is being signed, the act of=
 inserting the newly calculated signature for one input would break the sig=
natures for all the others.</div>
</div>

--f46d043c7dd684042904ca4d5b13--