From 2aa2c0967d8b2d7e3653f2227c136e4d0f66e7bc Mon Sep 17 00:00:00 2001 From: 8go Date: Thu, 2 Jul 2020 06:43:08 +0000 Subject: [PATCH] simplifications --- node_client.asciidoc | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/node_client.asciidoc b/node_client.asciidoc index 9fc4258..d232da5 100644 --- a/node_client.asciidoc +++ b/node_client.asciidoc @@ -301,7 +301,7 @@ $ docker exec bitcoind bitcoin-cli -datadir=/bitcoind getblockchaininfo | jq .bl The +jq+ JSON decoder extract the result "189" from the +getblockchaininfo+, which we could use in a subsequent command. -As you will see in the following sections, we can run several containers and then interact with them individually, issuing commands to extract information (such as the Lightning node public key), or to take an action (open a Lightning channel to another node). The +docker run+ and +docker exec+, together with +jq+ for JSON decoding are all we need to build a working Lightning Network that mixes many different node implementations and allows us to try out various experiments, all on our own computer. +As you will see in the following sections, we can run several containers at the same time and then interact with them individually. We can issue commands to extract information such as the Lightning node public key, or to take actions such as opening a Lightning channel to another node. The +docker run+ and +docker exec+ commands together with +jq+ for JSON decoding are all we need to build a working Lightning Network that mixes many different node implementations. This enables us to try out diverse experiments on our own computer. === The c-lightning Lightning node project