From 396ee26bf76f24f52fd50d2a7ddb1462af61952f Mon Sep 17 00:00:00 2001 From: Shannon Appelcline Date: Tue, 28 Mar 2017 10:35:06 -0700 Subject: [PATCH] Update 3_3__Using_Command-Line_Variables.md --- 3_3__Using_Command-Line_Variables.md | 6 ++---- 1 file changed, 2 insertions(+), 4 deletions(-) diff --git a/3_3__Using_Command-Line_Variables.md b/3_3__Using_Command-Line_Variables.md index 016bc7d..14b171d 100644 --- a/3_3__Using_Command-Line_Variables.md +++ b/3_3__Using_Command-Line_Variables.md @@ -21,12 +21,10 @@ $ echo $NEW_ADDRESS_1 n4cqjJE6fqcmeWpftygwPoKMMDva6BpyHf ``` -You could similarly save a signature like this: +Because you have your address in a variable, you can now easily sign a message for that address, without worrying about misstyping the address. You'll of course save that signature into a variable too! ``` $ NEW_SIG_1=$(bitcoin-cli signmessage $NEW_ADDRESS_1 "Hello, World") ``` -Just put _everything_ inside the parentheses! - The rest of this tutorial will use this style of saving information to variables when it's practical. -(When is it not practical? Saving your signature may not actually be practical if you're just going to have to send it to someone else, not use it yourself. In addition, in the future, some commands will output JSON objects instead of just a line of information, and variables can't be used to capture that information ... though there are alternatives.) +_When is it not practical? Saving your signature may not actually be practical if you're just going to have to send it to someone else, not use it yourself. In addition, in the future, some commands will output JSON objects instead of just a line of information, and variables can't be used to capture that information ... though there are alternatives._