From 9b6ed8c3e9b614788f10c7e2ed04adc5ee79d3e5 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Fri, 24 Jan 2020 09:11:53 -1000 Subject: [PATCH] Update 09_2_Using_CLTV_in_Scripts.md --- 09_2_Using_CLTV_in_Scripts.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/09_2_Using_CLTV_in_Scripts.md b/09_2_Using_CLTV_in_Scripts.md index e6c65ae..399e630 100644 --- a/09_2_Using_CLTV_in_Scripts.md +++ b/09_2_Using_CLTV_in_Scripts.md @@ -1,10 +1,10 @@ # 9.2: Using CLTV in Scripts -> **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. `OP_CHECKLOCKTIMEVERIFY` (or CLTV) is the natural complement to `nLockTime`. It moves the idea of locking transactions by an absolute time or blockheight into the realm of opcodes, allowing for the locking of individual UTXOs. -> **VERSION WARNING:** CLTV became available with Bitcoin Core 0.11.2, but should be fairly widely deployed at this time. +> :warning: **VERSION WARNING:** CLTV became available with Bitcoin Core 0.11.2, but should be fairly widely deployed at this time. ## Remember nLockTime