From 4cbc60203d80dedf69c76cab07be3828b9910ad1 Mon Sep 17 00:00:00 2001 From: Javier Vargas Date: Thu, 23 Jul 2020 13:36:43 +0200 Subject: [PATCH] Update 13_3_Setting_Up_a_Channel.md --- 13_3_Setting_Up_a_Channel.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/13_3_Setting_Up_a_Channel.md b/13_3_Setting_Up_a_Channel.md index 66b08ec..e2ad745 100644 --- a/13_3_Setting_Up_a_Channel.md +++ b/13_3_Setting_Up_a_Channel.md @@ -72,7 +72,9 @@ Now that we have funded our c-lightning wallet we will get information about rem The first thing you need to do is connect your node to a peer. This is done with the `lightning-cli connect` command. Remember that if you want more information on this command, you should type `lightning-cli help connect`. The connect RPC command establishes a new connection with another node in the Lightning Network. -To connect your node to a remote peer you need it's id that represents the target node’s public key. As a convenience, id may be of the form id@host or id@host:port. Using `lightning-cli listnodes` command you obtain all nodes available on the network and choose one. +You have two options here, you could set up a Lightning node on a second machine using the Standup script and choose LND implementation or search a node to connect to. + +To connect your node to a remote peer you need it's id that represents the target node’s public key. As a convenience, id may be of the form id@host or id@host:port. Using `lightning-cli listnodes` command you obtain all nodes available on the network and choose one. ``` c$ lightning-cli --network testnet listnodes