From 107e331b2f08fd10a66c0777ff63dc59e9b11b58 Mon Sep 17 00:00:00 2001 From: "David A. Harding" Date: Tue, 14 Mar 2023 09:09:13 -1000 Subject: [PATCH] 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. --- chapters/authorization-authentication.adoc | 5 +++-- 1 file changed, 3 insertions(+), 2 deletions(-) diff --git a/chapters/authorization-authentication.adoc b/chapters/authorization-authentication.adoc index f659d6cc..fec246fd 100644 --- a/chapters/authorization-authentication.adoc +++ b/chapters/authorization-authentication.adoc @@ -68,8 +68,9 @@ validation mechanism from being used as a vulnerability. ((("stateless verification")))The bitcoin transaction script language is stateless, in that there is no state prior to execution of the script, -or state saved after execution of the script. Therefore, all the -information needed to execute a script is contained within the script. A +or state saved after execution of the script. All the +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 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