From f4f7e4199f2bf59e32c050b39bd4d0d4bc05c5b8 Mon Sep 17 00:00:00 2001 From: Javier Vargas Date: Tue, 20 Jul 2021 10:09:28 +0200 Subject: [PATCH] Update 19_3_Setting_Up_a_Channel.md --- 19_3_Setting_Up_a_Channel.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/19_3_Setting_Up_a_Channel.md b/19_3_Setting_Up_a_Channel.md index 1d2e39b..19259aa 100644 --- a/19_3_Setting_Up_a_Channel.md +++ b/19_3_Setting_Up_a_Channel.md @@ -80,7 +80,7 @@ Now that you have funded your c-lightning wallet you will need information about The next 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`. -To connect your node to a remote peer you need its id, which represents the target node’s public key. As a convenience, `id` may be of the form `id@host` or `id@host:port`. You may have retrieved this with `lightning-cli getinfo` (on c-lightning) or `lncli --network=testnet getinfo` (on LND) as discussed in the [previous interlude](18_2__Interlude_Accessing_a_Second_Lightning_Node.md). +To connect your node to a remote peer you need its id, which represents the target node’s public key. As a convenience, `id` may be of the form `id@host` or `id@host:port`. You may have retrieved this with `lightning-cli getinfo` (on c-lightning) or `lncli --network=testnet getinfo` (on LND) as discussed in the [previous interlude](19_2__Interlude_Accessing_a_Second_Lightning_Node.md). We've selected the LND node, `032a7572dc013b6382cde391d79f292ced27305aa4162ec3906279fc4334602543`, which is located at IP address `45.33.35.151`, which we're going to connect to from our c-lightning node: