BitcoinCash/specification
1
Fork 0
Code Issues Pull Requests Releases Activity

Merge remote-tracking branch 'bu/master'

Browse Source
This commit is contained in:
Josh Green
2021-02-11 14:35:57 -05:00
parent 8f7270c2ab d2abf149bd
commit 3c9fa43a71
8 changed files with 3 additions and 37 deletions
Download Patch File Download Diff File Expand all files Collapse all files
protocol/blockchain/transaction/transaction-signing.md
+1 -2
View File
@@ -1,5 +1,4 @@
# Transaction Signatures
# Transaction Signing
Transaction signatures are central to how [Bitcoin Cash transactions](/protocol/blockchain/transaction) are generally secured, preventing people other than the intended recipient of funds from spending them.
Bitcoin Cash signatures are created using [asymmetric cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) and involve generating a [hash](/protocol/blockchain/hash) of the transaction and performing a signature operation using the sender's private key.
protocol/blockchain/transaction/unlocking-script.md
+1 -1
View File
@@ -5,4 +5,4 @@ This is accomplished by first executing the unlocking script and then executing
If this execution triggers no failures and leaves a single non-zero (TRUE) value on the stack, the UTXO has been successfully unlocked.
One way to look at this is that the unlocking script provides an initial state that acts as an inverse to the previously published locking script.
For more information about how script execution works, see [Script](/protocol/blockchain/script). For information on how signatures (which typically go in the unlocking script) are generated, see [Transaction Signatures](/protocol/blockchain/transaction/signatures).
For more information about how script execution works, see [Script](/protocol/blockchain/script). For information on how signatures (which typically go in the unlocking script) are generated, see [Transaction Signatures](/protocol/blockchain/transaction/transaction-signing).