From 5650f556af0f2514b0f87ba78c9b845339301f70 Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Thu, 20 Apr 2017 15:01:22 -0700 Subject: [PATCH] Update 5_5_Sending_a_Raw_Transaction_with_a_Locktime.md --- 5_5_Sending_a_Raw_Transaction_with_a_Locktime.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/5_5_Sending_a_Raw_Transaction_with_a_Locktime.md b/5_5_Sending_a_Raw_Transaction_with_a_Locktime.md index 6ddc15d..19a938e 100644 --- a/5_5_Sending_a_Raw_Transaction_with_a_Locktime.md +++ b/5_5_Sending_a_Raw_Transaction_with_a_Locktime.md @@ -42,7 +42,7 @@ _Why Would I Use a Blockheight?_ Unlike with timestamps, there's no fuzziness fo Once you have figured out your locktime, all you need to do is write up a typical raw transaction, with a third variable for `locktime`: ``` -$ $ rawtxhex=$(bitcoin-cli -named createrawtransaction transactions='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''{ "'$recipient'": 0.8, "'$changeaddress'": 0.0895 }''' locktime=1119160) +$ rawtxhex=$(bitcoin-cli -named createrawtransaction inputs='''[ { "txid": "'$utxo_txid'", "vout": '$utxo_vout' } ]''' outputs='''{ "'$recipient'": 0.8, "'$changeaddress'": 0.0895 }''' locktime=1119160) ``` Note that this usage of `locktime` is under 500 million, which means that it defines a block height. In this case, it's just a few blocks past the current block height, meant to exemplify how locktime works without sitting around for a long time to wait and see what happens.