flywithu/Learning-Bitcoin-from-the-Command-Line
1
1
Fork 0
mirror of https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git synced 2025-10-31 18:37:36 +00:00
Code Issues Releases Wiki Activity

Merge pull request #71 from jakobalexander/patch-1

Browse Source 
Shell prompt typos corrected / made uniform
This commit is contained in:
Shannon Appelcline 2018-11-29 10:43:08 -08:00 committed by GitHub
commit ee4fb6c59a
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
04_2__Interlude_Using_JQ.md
View File

@ -70,7 +70,7 @@ $ bitcoin-cli listunspent | jq -r '.[0]'
``` ```
You can then capture an individual value from that selected array by (1) using a pipe _within_ the JQ arguments; and then (2) requesting the specific value afterward, as in the previous example. The following would capture the `txid` from the 0th JSON object in the JSON array produced by `listunspent`: You can then capture an individual value from that selected array by (1) using a pipe _within_ the JQ arguments; and then (2) requesting the specific value afterward, as in the previous example. The following would capture the `txid` from the 0th JSON object in the JSON array produced by `listunspent`:
``` ```
~$ bitcoin-cli listunspent | jq -r '.[0] | .txid' $ bitcoin-cli listunspent | jq -r '.[0] | .txid'
2b5f5798359e0e23e02764588166f222d4ce056419dec83c743b72aad171d708 2b5f5798359e0e23e02764588166f222d4ce056419dec83c743b72aad171d708
``` ```
Carefully note how the `' 's` go around the whole JQ expression _including_ the pipe. Carefully note how the `' 's` go around the whole JQ expression _including_ the pipe.
@ -154,7 +154,7 @@ $ bitcoin-cli listunspent | jq -r '.[] | { txid: .txid, vout: .vout, amount: .am
``` ```
You could of course rename your new keys as you see fit. There's nothing magic in the original names: You could of course rename your new keys as you see fit. There's nothing magic in the original names:
``` ```
~$ bitcoin-cli listunspent | jq -r '.[] | { tx: .txid, output: .vout, bitcoins: .amount }' $ bitcoin-cli listunspent | jq -r '.[] | { tx: .txid, output: .vout, bitcoins: .amount }'
{ {
"tx": "2b5f5798359e0e23e02764588166f222d4ce056419dec83c743b72aad171d708", "tx": "2b5f5798359e0e23e02764588166f222d4ce056419dec83c743b72aad171d708",
"output": 1, "output": 1,
@ -179,7 +179,7 @@ The JQ lookups so far have been fairly simple: you use a key to look up one or m
This example uses the following raw transaction. Note that this is a more complex raw transaction with two inputs and two outputs. We'll learn about making those in a few sections; for now, it's necessary to be able to offer robust examples. Note that unlike our previous examples, this one has two objects in its `vin` array and two in its `vout` array. This example uses the following raw transaction. Note that this is a more complex raw transaction with two inputs and two outputs. We'll learn about making those in a few sections; for now, it's necessary to be able to offer robust examples. Note that unlike our previous examples, this one has two objects in its `vin` array and two in its `vout` array.
``` ```
$ $ bitcoin-cli decoderawtransaction $rawtxhex $ bitcoin-cli decoderawtransaction $rawtxhex
{ {
"txid": "6f83a0b78c598de01915554688592da1d7a3047eacacc8a9be39f5396bf0a07e", "txid": "6f83a0b78c598de01915554688592da1d7a3047eacacc8a9be39f5396bf0a07e",
"hash": "6f83a0b78c598de01915554688592da1d7a3047eacacc8a9be39f5396bf0a07e", "hash": "6f83a0b78c598de01915554688592da1d7a3047eacacc8a9be39f5396bf0a07e",