mirror of
https://github.com/bitcoinbook/bitcoinbook
synced 2024-11-22 16:18:11 +00:00
Edited ch08_signatures.adoc with Atlas code editor
This commit is contained in:
parent
853252006a
commit
f2d904633a
@ -922,7 +922,7 @@ as follows:
|
|||||||
[[nonce_warning]]
|
[[nonce_warning]]
|
||||||
=== The Importance of Randomness in Signatures
|
=== The Importance of Randomness in Signatures
|
||||||
|
|
||||||
As we saw in <<schnorr_signatures>> and <<ecdsa_signatures>>,
|
As we((("digital signatures", "randomness, importance of", id="digital-signature-random")))((("randomness", "importance in digital signatures", id="random-digital-signature"))) saw in <<schnorr_signatures>> and <<ecdsa_signatures>>,
|
||||||
the signature generation algorithm uses a random number _k_, as the basis
|
the signature generation algorithm uses a random number _k_, as the basis
|
||||||
for a private/public nonce pair. The value of _k_ is not
|
for a private/public nonce pair. The value of _k_ is not
|
||||||
important, _as long as it is random_. If signatures from the same
|
important, _as long as it is random_. If signatures from the same
|
||||||
@ -968,7 +968,7 @@ fault-injection attacks.
|
|||||||
|
|
||||||
If you are implementing an algorithm to sign transactions in Bitcoin,
|
If you are implementing an algorithm to sign transactions in Bitcoin,
|
||||||
you _must_ use BIP340, RFC6979, or a similar algorithm to
|
you _must_ use BIP340, RFC6979, or a similar algorithm to
|
||||||
ensure you generate a different _k_ for each transaction.
|
ensure you generate a different _k_ for each ((("digital signatures", "randomness, importance of", startref="digital-signature-random")))((("randomness", "importance in digital signatures", startref="random-digital-signature")))transaction.
|
||||||
|
|
||||||
=== Segregated Witness's New Signing Algorithm
|
=== Segregated Witness's New Signing Algorithm
|
||||||
|
|
||||||
|
Loading…
Reference in New Issue
Block a user