Create 09_1_Understanding_Timelock_Options.md

This commit is contained in:
Shannon Appelcline 2017-06-13 11:57:54 -07:00 committed by GitHub
parent 90886da5a1
commit 1c63fe595b

View File

@ -2,7 +2,7 @@
> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. > **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
In [§6.4: Sending a Transaction with a Locktime](6_4_Sending_a_Transaction_with_a_Locktime.md), `nLocktime` offered a great first option for locking transactions so that they couldn't be spent until some point in the future — based either on time or blockheight. But, that's not the only way to put a timelock on a transaction. In [§6.4: Sending a Transaction with a Locktime](06_4_Sending_a_Transaction_with_a_Locktime.md), `nLocktime` offered a great first option for locking transactions so that they couldn't be spent until some point in the future — based either on time or blockheight. But, that's not the only way to put a timelock on a transaction.
## Understand the Limitations of nLockTime ## Understand the Limitations of nLockTime
@ -46,3 +46,6 @@ You now have four options for Timelock:
* CLTV to make a UTXO unspendable until a specific time. * CLTV to make a UTXO unspendable until a specific time.
* CSV to make a UTXO unspendable until a relative time. * CSV to make a UTXO unspendable until a relative time.
## What's Next?
Continue "Empowering Timelock" with [§9.2: Using CLTV in Scripts](09_2_Using_CLTV_in_Scripts.md).