mirrors/lightning-bolts
1
0
Fork 0
mirror of https://github.com/lightning/bolts.git synced 2024-11-19 10:00:04 +01:00
Code Issues Projects Releases Wiki Activity

Specify valid signature hash flags (SIGHASH_ALL)

Browse Source 
Clarify that this flag is only used for signing and not transmitted
This commit is contained in:
Orfeas Litos 2018-10-31 13:26:11 +00:00 committed by Rusty Russell
parent 8e62fd3a08
commit 24d5d33d67
1 changed files with 1 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
03-transactions.md
View File

@ -806,7 +806,7 @@ HTLC-success) results in weights of:
In the following:
- It's assumed that *local* is the funder.
- Private keys are displayed as 32 bytes plus a trailing 1 (Bitcoin's convention for "compressed" private keys, i.e. keys for which the public key is compressed).
- Transaction signatures are all deterministic, using RFC6979 (using HMAC-SHA256).
- Transaction signatures are all deterministic, using RFC6979 (using HMAC-SHA256). A valid signature MUST sign all inputs and outputs of the relevant transaction (i.e MUST be created with a `SIGHASH_ALL` [signature hash](https://bitcoin.org/en/glossary/signature-hash)), unless explicitly stated otherwise. Note that clients MUST send the signature in compact encoding and not in Bitcoin-script format, thus the signature hash byte is not transmitted.
The input for the funding transaction was created using a test chain
with the following first two blocks; the second block contains a spendable