From 2d2ac973e59ca891776f736592837dd9358ee61a Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Fri, 24 Jan 2020 09:11:25 -1000 Subject: [PATCH] Update 09_1_Understanding_Timelock_Options.md --- 09_1_Understanding_Timelock_Options.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/09_1_Understanding_Timelock_Options.md b/09_1_Understanding_Timelock_Options.md index 621ad31..d144aa3 100644 --- a/09_1_Understanding_Timelock_Options.md +++ b/09_1_Understanding_Timelock_Options.md @@ -1,6 +1,6 @@ # 9.1: Understanding Timelock Options -> **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning. +> :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.