arno/bitcoinbook
1
0
Fork 0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2024-11-26 09:58:22 +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 12:49:00 +00:00
parent 49321eaae5
commit 78635fa80c
1 changed files with 2 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
ch08_signatures.adoc
View File

@ -48,7 +48,7 @@ public key.
In Bitcoin's((("digital signatures", "creating"))) use of digital signature algorithms, the "message" being In Bitcoin's((("digital signatures", "creating"))) use of digital signature algorithms, the "message" being
signed is the transaction, or more accurately a hash of a specific signed is the transaction, or more accurately a hash of a specific
subset of the data in the transaction, called the _commitment hash_ (see subset of the data in the transaction, ((("commitment hash")))called the _commitment hash_ (see
<<sighash_types>>). The <<sighash_types>>). The
signing key is the user's private key. The result is the signature: signing key is the user's private key. The result is the signature:
@ -78,7 +78,7 @@ simpler serialization format is used.
==== Verifying the Signature ==== Verifying the Signature
The signature verification algorithm takes the message (a hash of parts of the transaction and related data), the signer's public key and the signature, and returns ++TRUE++ if the signature is valid for this message and public key. The((("digital signatures", "verifying")))((("verifying", "digital signatures"))) signature verification algorithm takes the message (a hash of parts of the transaction and related data), the signer's public key and the signature, and returns ++TRUE++ if the signature is valid for this message and public key.
To verify the signature, one must have the signature, the serialized To verify the signature, one must have the signature, the serialized
transaction, some data about the output being spent, and the public key transaction, some data about the output being spent, and the public key