From 378c4e845733a5ee8cdcc0fc1b6677b3a4b95190 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 21 Jul 2020 12:32:04 -1000 Subject: [PATCH] updating nums for 0.20 upgrade --- 11_1_Understanding_Timelock_Options.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/11_1_Understanding_Timelock_Options.md b/11_1_Understanding_Timelock_Options.md index d144aa3..ca85960 100644 --- a/11_1_Understanding_Timelock_Options.md +++ b/11_1_Understanding_Timelock_Options.md @@ -1,8 +1,8 @@ -# 9.1: Understanding Timelock Options +# 11.1: Understanding Timelock Options > :information_source: **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](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. +In [§8.1: Sending a Transaction with a Locktime](08_1_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