From 4e367e49384989b8ba955ad75b06bd2406fb994f Mon Sep 17 00:00:00 2001 From: Jordan Baczuk Date: Mon, 6 Aug 2018 14:41:44 -0600 Subject: [PATCH] fix the link to 8.1 in 7.1 --- 07_2_Running_a_Bitcoin_Script.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/07_2_Running_a_Bitcoin_Script.md b/07_2_Running_a_Bitcoin_Script.md index 8920329..742e262 100644 --- a/07_2_Running_a_Bitcoin_Script.md +++ b/07_2_Running_a_Bitcoin_Script.md @@ -246,7 +246,8 @@ Stack: [ True ] ``` This abstraction isn't quite accurate: for security reasons, the `scriptSig` is run, then the contents of the stack are transferred for the `scriptPubKey` to run, but it's accurate enough for understanding how the key of `scriptSig` fits into the lock of `scriptPubKey`. -> **WARNING** The above is a non-standard transaction type. It would not actually be accepted by nodes running Bitcoin Core with the standard settings. [§8.1: Building a Bitcoin Script with P2SH](08_1_Building_a_Bitcoin_Script_with_P2SH.md) discusses how you actually _could_ run a Bitcoin Script like this, using the power of P2SH. +> **WARNING** The above is a non-standard transaction type. It would not actually be accepted by nodes running Bitcoin Core with the standard settings. [§8.1: Building a Bitcoin Script with P2SH](08_1_Understanding_the_Foundation_of_P2SH.md +) discusses how you actually _could_ run a Bitcoin Script like this, using the power of P2SH. ### Get the Results