flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-06-08 08:26:17 +00:00
Code Issues Releases Wiki Activity

Update 9_3_Using_CSV_in_Scripts.md

Browse Source
This commit is contained in:
Shannon Appelcline 2017-05-26 13:42:00 -07:00 committed by GitHub
parent c455f1e123
commit ccf35601a6
1 changed files with 5 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
9_3_Using_CSV_in_Scripts.md
View File

@ -57,10 +57,12 @@ Issue the transaction, but it can't legally be mined until enough blocks or enou
Except pretty much no one does this. The new [BIP 68](https://github.com/bitcoin/bips/blob/master/bip-0068.mediawiki) definitions for `nSequence` were incorporated into Bitcoin Core at the same time as [BIP 112](https://github.com/bitcoin/bips/blob/master/bip-0112.mediawiki) which describes the CSV opcode, which works with `nSequence`, just like the CLTV opcode works with `nTimeLock`. Just like CLTV, CSV offers increased capabilities. So almost all usage of relative timelocks has been with the CSV opcode, not with the raw `nSequence` value on its own.
<center>
| | Absolute Timelock | Relative Timelock |
|------------------|-------------------|-------------------|
| Lock Transaction | nTimeLock | nSequence |
| Lock Output | OP_CHECKLOCKTIMEVERIFY| OP_CHECKSEQUENCEVERIFY |
|:----------------:|-------------------|-------------------|
| **Lock Transaction** | nTimeLock | nSequence |
| **Lock Output** | OP_CHECKLOCKTIMEVERIFY| OP_CHECKSEQUENCEVERIFY |
</center>
## Understand the CSV Opcode