1
0
mirror of https://github.com/bitcoinbook/bitcoinbook synced 2025-01-12 08:40:58 +00:00

ch12: Fix mistake in HTLC contract definition

Closes 
This commit is contained in:
Will Binns 2018-01-24 10:51:53 -06:00
parent d5e2316438
commit 1aa56ce982
No known key found for this signature in database
GPG Key ID: 302EBEAEEB74A404

View File

@ -426,13 +426,13 @@ IF
ELSE
# Refund after timeout.
<locktime> CHECKLOCKTIMEVERIFY DROP
<Payee Pubic Key> CHECKSIG
<Payer Pubic Key> CHECKSIG
ENDIF
----
Anyone who knows the secret +R+, which when hashed equals to +H+, can redeem this output by exercising the first clause of the +IF+ flow.
If the secret is not revealed and the HTLC claimed, after a certain number of blocks the payee can claim a refund using the second clause in the +IF+ flow.
If the secret is not revealed and the HTLC claimed, after a certain number of blocks the payer can claim a refund using the second clause in the +IF+ flow.
This is a basic implementation of an HTLC. This type of HTLC can be redeemed by _anyone_ who has the secret +R+. An HTLC can take many different forms with slight variations to the script. For example, adding a +CHECKSIG+ operator and a public key in the first clause restricts redemption of the hash to a named recipient, who must also know the secret +R+.((("", startref="BCApayment12")))