From 2409128defef2bb79947abe9f39db3b9a17268d6 Mon Sep 17 00:00:00 2001 From: clenser Date: Thu, 19 Oct 2023 12:04:40 +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 701892d0..fcd856d7 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -1767,7 +1767,7 @@ in a slightly different form, which we'll((("P2C (pay to contract)", startref="p [[scriptless_multisignatures_and_threshold_signatures]] === Scriptless Multisignatures and Threshold Signatures -In <>, we looked at scripts that require signatures from +In <>, we ((("scriptless multisignatures", id="scriptless-multi")))((("multisignature scripts", "scriptless", id="multisignature-scriptless")))((("threshold signatures", id="threshold-signature")))((("public key cryptography", "scriptless multisignatures", id="pub-key-scriptless")))looked at scripts that require signatures from multiple keys. However, there's another way to require cooperation from multiple keys, which is also confusingly called _multisignature_. To distinguish between the two types in this section, we'll call the @@ -1837,7 +1837,7 @@ auditability. For many users and use cases, the always reduced size and increased privacy of multisignatures outweighs its occasional challenges for -creating and auditing signatures. +creating and auditing((("scriptless multisignatures", startref="scriptless-multi")))((("multisignature scripts", "scriptless", startref="multisignature-scriptless")))((("threshold signatures", startref="threshold-signature")))((("public key cryptography", "scriptless multisignatures", startref="pub-key-scriptless"))) signatures. [[taproot]] === Taproot