mirrors/core-lightning
1
0
Fork 0
mirror of https://github.com/ElementsProject/lightning.git synced 2025-01-18 13:25:43 +01:00
Code Issues Projects Releases Wiki Activity

removed unwanted lines and added punctuation marks

Browse Source
This commit is contained in:
lakshit24 2020-10-17 11:24:04 +05:30 committed by Christian Decker
parent db19f19eb3
commit 1070e9b766
1 changed files with 4 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
README.md
View File

@ -38,9 +38,9 @@ Pruning (`prune=n` option in `bitcoin.conf`) is partially supported, see [here](
There are 4 supported installation options: There are 4 supported installation options:
- Installation from the [Ubuntu PPA][ppa] - Installation from the [Ubuntu PPA][ppa].
- Installation of a pre-compiled binary from the [release page][releases] on Github - Installation of a pre-compiled binary from the [release page][releases] on Github.
- Using one of the [provided docker images][dockerhub] on the Docker Hub - Using one of the [provided docker images][dockerhub] on the Docker Hub.
- Compiling the source code yourself as described in the [installation documentation](doc/INSTALL.md). - Compiling the source code yourself as described in the [installation documentation](doc/INSTALL.md).
For the impatient here's the gist of it for Ubuntu: For the impatient here's the gist of it for Ubuntu:
@ -154,8 +154,7 @@ lightning-cli connect <node_id> <ip> [<port>]
lightning-cli fundchannel <node_id> <amount_in_satoshis> lightning-cli fundchannel <node_id> <amount_in_satoshis>
``` ```
This opens a connection and, on top of that connection, then opens This opens a connection and, on top of that connection, then opens a channel.
a channel.
The funding transaction needs 3 confirmation in order for the channel to be usable, and 6 to be announced for others to use. The funding transaction needs 3 confirmation in order for the channel to be usable, and 6 to be announced for others to use.
You can check the status of the channel using `lightning-cli listpeers`, which after 3 confirmations (1 on testnet) should say that `state` is `CHANNELD_NORMAL`; after 6 confirmations you can use `lightning-cli listchannels` to verify that the `public` field is now `true`. You can check the status of the channel using `lightning-cli listpeers`, which after 3 confirmations (1 on testnet) should say that `state` is `CHANNELD_NORMAL`; after 6 confirmations you can use `lightning-cli listchannels` to verify that the `public` field is now `true`.