Why can't a transaction be redirected after it is signed?

1

Scenario:

Step 1: User-1 initiates the TXN-1 to pay to User-2 and the TXN is not yet confirmed with the ongoing block POW.

Step 2: What prevents fraudster (anyone a miner or someone listening/participating in the network), to double spend or divert the payment to User-3 with a new TXN-2 by copying the data from pending TXN-1 including the User-1's signature?

Step 3: if the miners reject both TXN-1 and TXN-2 as a suspicious or double spend activity in the current block POW, what prevents the same fraudster to issue a new TXN-3 by copying the TXN-2 with the next block POW?

Thanks in advance.

Hari.M

Posted 2015-12-13T22:40:54.623

Reputation: 11

Question was closed 2015-12-14T00:11:44.917

Answers

1

The signature corresponds to the transaction it signs. You can't use the same sig to send the money to another address, because that would require a different transaction for which the signature would not resolve to valid.

Murch

Posted 2015-12-13T22:40:54.623

Reputation: 41 609

Ok, Thanks. That should work but not sure how it can be confined to the signing TXN. So, can you clarify bit further as to how it is confined or refer any relevant link(s). Thanks. – Hari.M – 2015-12-13T23:20:58.703

1

The signing process uses transaction data and the sender's private key to generate the signature. This can then be checked by anyone using the provided public key and the transaction data. If the transaction was changed the checking script will not resolve to valid. https://bitcoin.org/en/developer-guide#term-signature

– Murch – 2015-12-13T23:59:54.403

I overlooked that fact when I went through the Wiki link. Got it now. Thanks. – Hari.M – 2015-12-14T03:25:29.680

Asked: 2015-12-13T22:40:54.623

Viewed: 144 times

Active: 2015-12-14T00:06:25.527