From 36d2473d39b9025a5a808528d1a4fc8693c17596 Mon Sep 17 00:00:00 2001 From: claylock Date: Fri, 27 Oct 2023 11:57:09 +0000 Subject: [PATCH] Edited ch07_authorization-authentication.adoc with Atlas code editor --- ch07_authorization-authentication.adoc | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/ch07_authorization-authentication.adoc b/ch07_authorization-authentication.adoc index e5454b37..e1175ed0 100644 --- a/ch07_authorization-authentication.adoc +++ b/ch07_authorization-authentication.adoc @@ -1819,6 +1819,8 @@ multisignatures looks like every other scriptless multisignature and every single-signature, no privacy-reducing data is leaked. +++++ +

There are two downsides of scriptless multisignatures. The first is that all known secure algorithms for creating them for Bitcoin require more rounds of interaction or more careful management of state than @@ -1828,6 +1830,8 @@ devices and the keys are physically distributed. For example, if you keep a hardware signing device in a bank safe deposit box, you would need to visit that box once to create a scripted multisignature but possibly two or three times for a scriptless multisignature. +

+++++ The other downside is that threshold signing doesn't reveal who signed. In scripted threshold signing, Alice, Bob, and Carol agree (for example)