From: Mike Hearn <mike@plan99•net>
To: "Jorge Timón" <timon.elviejo@gmail•com>
Cc: Bitcoin Development <bitcoin-development@lists•sourceforge.net>
Subject: Re: [Bitcoin-development] Atomic coin swapping?
Date: Sat, 22 Sep 2012 19:05:03 +0200 [thread overview]
Message-ID: <CANEZrP257oD26WkYNr4fXuMOkURstsiuA0NoD92gBxViyf9xWw@mail.gmail.com> (raw)
In-Reply-To: <CAGQP0AEnkRqiEb2_COpQpLKkZfHf0fFgHmquO5oY4_Gh84k7cA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 355 bytes --]
>
> 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.
[-- Attachment #2: Type: text/html, Size: 537 bytes --]
next prev parent reply other threads:[~2012-09-22 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-22 7:28 Jeff Garzik
2012-09-22 9:10 ` Jorge Timón
2012-09-22 11:04 ` Mike Hearn
2012-09-22 17:05 ` Mike Hearn [this message]
2012-09-22 17:09 ` Jeff Garzik
2012-09-22 18:24 ` Jorge Timón
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CANEZrP257oD26WkYNr4fXuMOkURstsiuA0NoD92gBxViyf9xWw@mail.gmail.com \
--to=mike@plan99$(echo .)net \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
--cc=timon.elviejo@gmail$(echo .)com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox