From 9044787d57033caa447f9cec4b367b77a67679bd Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Francisco=20Calder=C3=B3n?= Date: Wed, 22 Jul 2020 11:48:33 -0300 Subject: [PATCH] Fixes some typos --- node_client.asciidoc | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/node_client.asciidoc b/node_client.asciidoc index 9fc4258..10fbfe5 100644 --- a/node_client.asciidoc +++ b/node_client.asciidoc @@ -30,13 +30,13 @@ In most of the examples here, we will be building the software directly from the To keep things consistent, we use the +bash+ shell in all command-line examples. While other shells will behave in a similar way, and you will be able to run all the examples without it, some of the shell scripts are written specifically for the +bash+ shell and may require some changes or customization to run in another shell. For consistency, you can install the +bash+ shell on Windows and Mac OS, and it comes installed by default on most Linux systems. -==== Donwloading the book repository +==== Downloading the book repository All the code examples are available in the book's repository. The repository will be kept up-to-date, as much as possible, so you should always look for the latest version in the repository, instead of copying it from the printed book or ebook version of this test. You can download the repository as a ZIP bundle by visiting +github.com/lnbook/lnbook+ and selecting the "Clone or Download" green button on the right. -Alternatively, you can use the +git+ command, to create a version-controlled clone of the repository on your local computer. Git is a distributed version control system that is used by most developers to collaborate on software development and track changes to software repositories. Donwload and install +git+ by following the instructions on https://git-scm.com/. +Alternatively, you can use the +git+ command, to create a version-controlled clone of the repository on your local computer. Git is a distributed version control system that is used by most developers to collaborate on software development and track changes to software repositories. Download and install +git+ by following the instructions on https://git-scm.com/. To make a local copy of the repository on your computer, run the git command as follows: @@ -258,7 +258,7 @@ For now, there are no transactions. But we now have some test bitcoin that has b ===== Interacting with the Bitcoin Core Container -In the mean time, we can also interact with the bitcoind container by sending it shell commands. The container is sending a log file to the terminal, displaying the mining process of the bitcoind process. To interact with the shell we can issue commands in another terminal, using the +docker exec+ command. Since we previously named the running container with the +name+ argument, we can refer to it with that name when we run the +docker exec+ command. First, let's run an interactive +bash+ shell: +In the meantime, we can also interact with the bitcoind container by sending it shell commands. The container is sending a log file to the terminal, displaying the mining process of the bitcoind process. To interact with the shell we can issue commands in another terminal, using the +docker exec+ command. Since we previously named the running container with the +name+ argument, we can refer to it with that name when we run the +docker exec+ command. First, let's run an interactive +bash+ shell: ---- $ docker exec -it bitcoind /bin/bash @@ -538,7 +538,7 @@ Setting TEST_NETWORK... regtest $ ---- -Next, we use the +make+ command to build the libraries, components and executables of the c-lightning project. This part will take several minutes to complete and will use your computers CPU and disk aggressively, so expect some noise from the fans! Running make: +Next, we use the +make+ command to build the libraries, components and executables of the c-lightning project. This part will take several minutes to complete and will use your computer's CPU and disk aggressively, so expect some noise from the fans! Running make: ---- $ make @@ -856,7 +856,7 @@ Java version: 11.0.7, vendor: Ubuntu, runtime: /usr/lib/jvm/java-11-openjdk-amd6 We have OpenJDK 11.0.7 and Maven 3.6.1, so we're ready. -==== Copying the LND source code +==== Copying the Eclair source code The source code for Eclair is on Github. The +git clone+ command can create a local copy for us. Let's switch to our home directory and run it there: @@ -1008,7 +1008,7 @@ To make things easier, we have a little helper script that sets up the network, [TIP] ==== -Beofre running the setup-channels script: Wait a minute or two after starting the network with docker-compose, to make sure all the services are running and all the wallets are funded. To keep things simple, the script doesn't check whether the containers are "ready". Be patient! +Before running the setup-channels script: Wait a minute or two after starting the network with docker-compose, to make sure all the services are running and all the wallets are funded. To keep things simple, the script doesn't check whether the containers are "ready". Be patient! ==== Let's run the script to see its effect and then we will look at how it works internally. We use +bash+ to run it as a command: @@ -1087,7 +1087,7 @@ Now, on Gloria's node, we create a new invoice, for 10,000 satoshi: lncli -n regtest addinvoice 10000 | jq .payment_request ---- -The +addinvoice+ command creates an invoice for the specified amount (in satoshis) and produces a JSON object with the invoice details. From that JSON object, we only need the actual bech32-encoded payement request, and we use +jq+ to extract it. +The +addinvoice+ command creates an invoice for the specified amount (in satoshis) and produces a JSON object with the invoice details. From that JSON object, we only need the actual bech32-encoded payment request, and we use +jq+ to extract it. Next, we have to wait. We just created a bunch of channels, which means that our nodes broadcast a bunch of funding transactions. The channels can't be used until the funding transactions are mined with 6 confirmations. Since our Bitcoin regtest blockchain is set to mine blocks every ten seconds, we have to wait 60 seconds for all the channels to be ready to use.