mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-23 00:28:14 +00:00
CH07: Statlessnes is per-tx not per-script
Some of the information necessary to validate a transaction is contained within the transaction executing the script, such as the data the signature commits to plus its locktimes for OP_CLTV & OP_CSV.
This commit is contained in:
parent
38dd2398ae
commit
107e331b2f
@ -68,8 +68,9 @@ validation mechanism from being used as a vulnerability.
|
|||||||
|
|
||||||
((("stateless verification")))The bitcoin transaction script language is
|
((("stateless verification")))The bitcoin transaction script language is
|
||||||
stateless, in that there is no state prior to execution of the script,
|
stateless, in that there is no state prior to execution of the script,
|
||||||
or state saved after execution of the script. Therefore, all the
|
or state saved after execution of the script. All the
|
||||||
information needed to execute a script is contained within the script. A
|
information needed to execute a script is contained within the script
|
||||||
|
and the transaction executing the script. A
|
||||||
script will predictably execute the same way on any system. If your
|
script will predictably execute the same way on any system. If your
|
||||||
system verifies a script, you can be sure that every other system in the
|
system verifies a script, you can be sure that every other system in the
|
||||||
Bitcoin network will also verify the script, meaning that a valid
|
Bitcoin network will also verify the script, meaning that a valid
|
||||||
|
Loading…
Reference in New Issue
Block a user