From d82404326ac318095bda429227089d2eebcf5de1 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 19:49:05 +0000 Subject: [PATCH] Edited ch07_authorization-authentication.adoc with Atlas code editor --- ch07_authorization-authentication.adoc | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc index aeefdd3e..23525a74 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -465,7 +465,7 @@ workaround to an oddity in the ((("scripts", "multisignature", startref="script- [[p2sh]] === Pay to Script Hash -Pay to script hash (P2SH) was((("scripts", "P2SH (pay to script hash)", id="script-p2sh")))((("P2SH (pay to script hash)", id="p2sh"))) +Pay to script hash (P2SH) was((("scripts", "P2SH (pay to script hash)", id="script-p2sh")))((("P2SH (pay to script hash)", id="p2sh-ch7"))) introduced in 2012 as a powerful new type of operation that greatly simplifies the use of complex scripts. To explain the need for P2SH, let's look at a practical example. @@ -677,7 +677,7 @@ P2SH output scripts contain the hash of a redeem script, which gives no clues as to the content of the redeem script. The P2SH output will be considered valid and accepted even if the redeem script is invalid. You -might accidentally receive bitcoin in such a way that it cannot later((("scripts", "P2SH (pay to script hash)", startref="script-p2sh")))((("P2SH (pay to script hash)", startref="p2sh"))) be +might accidentally receive bitcoin in such a way that it cannot later((("scripts", "P2SH (pay to script hash)", startref="script-p2sh")))((("P2SH (pay to script hash)", startref="p2sh-ch7"))) be spent. ====