minor typo - not CLTV but CSV ?

This commit is contained in:
Ann-Jie Ching 2018-04-09 22:52:11 -05:00 committed by GitHub
parent 13dc3b70d9
commit 4c8d4f71c2
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -110,9 +110,9 @@ A script that would lock funds until six months had passed following the mining
<+6Months> OP_CHECKSEQUENCEVERIFY OP_DROP OP_DUP OP_HASH160 <pubKeyHash> OP_EQUALVERIFY OP_CHECKSIG
```
### Encode a CLTV Script
### Encode a CSV Script
When you encode a CLTV script, be careful how you encode the integer value for the relative locktime. It should be passed as a 3-byte integer, which means that you're ignoring the top byte, which could inactivate the relative locktime. Since it's an integer, be sure you convert it to little-endian.
When you encode a CSV script, be careful how you encode the integer value for the relative locktime. It should be passed as a 3-byte integer, which means that you're ignoring the top byte, which could inactivate the relative locktime. Since it's an integer, be sure you convert it to little-endian.
This can be done with the `integer2lehex.sh` shell script from the previous chapter.