Timeline for How OP_CHECKSIG knows the source of sig in pay to pubkey hash transaction
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Sep 11, 2018 at 14:38 | vote | accept | Carpemer | ||
| Sep 1, 2018 at 2:26 | comment | added | Carpemer | One more question, in step 9, why the sender will decide the fee (0.001) in the process of generation input. If it is true, how the verifier could know what is the fee from the hash code? Actually, from the code in GitHub, it looks like it uses the original amount directly, and in the gitbub, it output the amount and then sequence (FFFFFFFF), but in that post, the order like amount first, then output script in step 9 and step 10. | |
| Aug 31, 2018 at 17:15 | comment | added | JBaczuk | It's actually not simple, but there is a good explanation of what is hashed and signed here: bitcoin.stackexchange.com/a/5241/60443 | |
| Aug 31, 2018 at 15:22 | comment | added | Carpemer | The code in SignatureHash() looks reconstruct (l1217~1235) part of the transaction and hash again. Then use pubKey to verify the hash and sig. Is the "data" you mentioned above is that the reconstructed byte list? | |
| Aug 30, 2018 at 13:36 | history | edited | JBaczuk | CC BY-SA 4.0 |
added 54 characters in body
|
| Aug 30, 2018 at 13:08 | history | answered | JBaczuk | CC BY-SA 4.0 |