arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-12-26 08:28:15 +00:00
Code Issues Releases Wiki Activity

Edited ch08_signatures.adoc with Atlas code editor

Browse Source
This commit is contained in:
clenser 2023-10-19 13:11:27 +00:00
parent 4e24b9ff43
commit 8a53c0957f
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
ch08_signatures.adoc
View File

@ -652,7 +652,7 @@ cases. More complex schemes have been proposed that address these
shortcomings.
In addition to the key cancellation attack, there are a number of
attacks possible against nonces. Recall that the purpose of the nonce
attacks possible against ((("nonce attacks")))nonces. Recall that the purpose of the nonce
is to prevent anyone from being able to use their knowledge of other values
in the signature verification equation to solve for your private key,
determining its value. To effectively accomplish that, you must use a
@ -666,13 +666,13 @@ there's no single multisignature protocol to recommend in all cases.
Instead, we'll note three from the MuSig family of protocols:
MuSig::
Also called _MuSig1_, this protocol requires three rounds of
Also called _MuSig1_, this protocol((("MuSig protocol"))) requires three rounds of
communication during the signing process, making it similar to the
process we just described. MuSig1's greatest advantage is its
simplicity.
MuSig2::
This only requires two rounds of communication and can sometimes allow
This only ((("MuSig2 protocol")))requires two rounds of communication and can sometimes allow
one of the rounds to be combined with key exchange. This can
significantly speed up signing for certain protocols, such as how
scriptless multisignatures are planned to be used in the Lightning
@ -680,7 +680,7 @@ MuSig2::
multisignature protocol that has a BIP as of this writing).
MuSig-DN::
DN stands for Deterministic Nonce, which eliminates as a concern a
DN stands ((("MuSig-DN protocol")))((("repeated session attack")))for Deterministic Nonce, which eliminates as a concern a
problem known as the _repeated session attack_. It can't be combined
with key exchange and it's significantly more complex to implement
than MuSig or MuSig2.