From 1c63fe595be1de828a3496a965a5546b937085d9 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 13 Jun 2017 11:57:54 -0700 Subject: [PATCH] Create 09_1_Understanding_Timelock_Options.md --- 09_1_Understanding_Timelock_Options.md | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/09_1_Understanding_Timelock_Options.md b/09_1_Understanding_Timelock_Options.md index 03b5088..621ad31 100644 --- a/09_1_Understanding_Timelock_Options.md +++ b/09_1_Understanding_Timelock_Options.md @@ -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. -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 @@ -46,3 +46,6 @@ You now have four options for Timelock: * CLTV to make a UTXO unspendable until a specific 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).