An implementation of rgb on core lightning This fork of cln is maintained by Vincenzo Palazzo
Go to file
Christian Decker f27013c338 gossip: Only skip updates if we don't have channels yet 2018-01-14 23:40:04 +00:00
bitcoin bitcoin: Split pull_bitcoin_tx 2018-01-08 17:19:25 +01:00
ccan Revert "Functions for encoding reversed hex" 2017-12-21 11:05:38 +00:00
channeld channeld: ignore spurious open_channel packets. 2018-01-12 09:43:01 +01:00
cli Makefiles: simplify dependencies. 2017-08-29 17:54:14 +02:00
closingd peer_failed: use towire_errorfmtv() which doesn't add nul terminator. 2018-01-12 09:43:01 +01:00
common features: Move feature-handling code to a common/features.c source. 2018-01-13 11:29:42 +01:00
contrib JSON: Rename rhash to payment_hash in delinvoice, invoice, listinvoice, waitinvoice, waitanyinvoice. 2018-01-14 23:10:10 +00:00
devtools bolt11: handle r value fee spec change. 2017-12-12 11:45:44 +01:00
doc doc: manpages for pay, listpayments and decodepay. 2018-01-14 23:10:10 +00:00
external Makefile: clean needs to do more, distclean should remove everything. 2017-11-24 13:29:03 +01:00
gossipd gossip: Only skip updates if we don't have channels yet 2018-01-14 23:40:04 +00:00
hsmd Check return value of derive_simple_privkey(...) call in hsm_unilateral_close_privkey(...) 2018-01-10 04:05:49 +00:00
lightningd gossip: Pass --channel-update-interval to gossipd 2018-01-14 23:40:04 +00:00
onchaind subdaemon.c: subdaemon_setup() routine for all daemons. 2018-01-08 18:16:39 +01:00
openingd subdaemon.c: subdaemon_setup() routine for all daemons. 2018-01-08 18:16:39 +01:00
test Check return value of read_all(...) call 2018-01-10 04:03:58 +00:00
tests pytest: Verify that we forget nodes that have no channels anymore 2018-01-14 23:40:04 +00:00
tools generate-wire.py: Add scare comments to output. 2018-01-10 23:53:12 +00:00
wallet wallet: Store msatoshi_received in the DB 2018-01-14 23:10:10 +00:00
wire wire: move extract_channel_id to here. 2018-01-12 09:43:01 +01:00
.dir-locals.el emacs: add .dir-locals.el for linux style C 2018-01-10 04:01:56 +00:00
.gitignore test: add tests for parse_ip_port 2017-12-21 09:56:20 +00:00
.gitlab-ci.yml Add .gitlab-ci.yml 2016-12-11 13:24:27 +01:00
.gitmodules external/libbacktrace: new external library for backtrace support. 2017-09-12 23:00:53 +02:00
.travis.yml travis: Enable pytest-test-groups to split tests across several runs 2017-12-21 22:43:24 +00:00
LICENSE licensing: Make license explicit. 2016-01-22 06:41:46 +10:30
Makefile Makefile: Install subdaemons into pkglibexecdir instead of bindir. 2018-01-09 14:52:48 +01:00
README.md README: don't suggest low-level commands, talk about invoice, bolt11 and pay. 2018-01-14 23:10:10 +00:00

README.md

c-lightning: A specification compliant Lightning Network implementation in C

c-lightning is a standard compliant implementation of the Lightning Network protocol. The Lightning Network is a scalability solution for Bitcoin, enabling secure and instant transfer of funds between any two party for any amount.

For more information about the Lightning Network please refer to http://lightning.network.

Project Status

This implementation is still very much work in progress, and, although it can be used for testing, it should not be used for real funds. We do our best to identify and fix problems, and implement missing feature.

Any help testing the implementation, reporting bugs, or helping with outstanding issues is very welcome. Don't hesitate to reach out to us on IRC at #lightning-dev @ freenode.net, #c-lightning @ freenode.net, or on the mailing list lightning-dev@lists.linuxfoundation.org.

Getting Started

c-lightning currently only works on Linux (and possibly Mac OS with some tweaking), and requires a locally running bitcoind (version 0.15 or above) that is fully caught up with the network you're testing on.

Installation

Please refer to the installation documentation for detailed instructions. For the impatient here's the gist of it for Ubuntu and Debian:

sudo apt-get install -y autoconf build-essential git libtool libgmp-dev libsqlite3-dev python3 net-tools
git clone https://github.com/ElementsProject/lightning.git
cd lightning
make

Or if you like to throw docker into the mix:

sudo docker run \
	-v $HOME/.lightning:/root/.lightning \
	-v $HOME/.bitcoin:/root/.bitcoin \
	-p 9735:9735 \
	cdecker/lightningd:latest

Starting lightningd

In order to start lightningd you will need to have a local bitcoind node running in either testnet or regtest mode:

bitcoind -daemon -testnet

Wait until bitcoind has synchronized with the testnet network. In case you use regtest, make sure you generate at least 432 blocks to activate SegWit.

Make sure that you do not have walletbroadcast=0 in your ~/.bitcoin/bitcoin.conf, or you may run into trouble.

You can start lightningd with the following command:

lightningd/lightningd --network=testnet --log-level=debug

Opening a channel on the Bitcoin testnet

First you need to transfer some funds to lightningd so that it can open a channel:

# Returns an address <address>
cli/lightning-cli newaddr

# Returns a transaction id <txid>
bitcoin-cli -testnet sendtoaddress <address> <amount>

lightningd will register the funds once the transaction is confirmed.

If you don't have any testcoins you can get a few from a faucet such as TPs' testnet faucet or Kiwi's testnet faucet. You can send it directly to the lightningd address.

Confirm lightningd got funds by:

# Returns an array of on-chain funds.
cli/lightning-cli listfunds

Once lightningd has funds, we can connect to a node and open a channel. Let's assume the remote node is accepting connections at <ip> (and optional <port>, if not 9735) and has the node ID <node_id>:

cli/lightning-cli connect <node_id> <ip> [<port>]
cli/lightning-cli fundchannel <node_id> <amount>

This opens a connection and, on top of that connection, then opens a channel. The funding transaction needs 1 confirmations in order for the channel to be usable, and 6 to be broadcast for others to use. You can check the status of the channel using cli/lightning-cli getpeers, which after 1 confirmation should say that state is CHANNELD_NORMAL; after 6 confirmations you can use cli/lightning-cli getchannels to verify that the public field is now true.

Receiving and receiving payments

Payments in Lightning are invoice based. The recipient creates an invoice with the expected <amount> in millisatoshi (or "any" for a donation), a unique <label> and a <description> the payer will see:

cli/lightning-cli invoice <amount> <label> <description>

This returns some internal details, and a standard invoice string called bolt11 (named after the BOLT #11 lightning spec.

The sender can feed this bolt11 string to the decodepay command to see what it is, and pay it simply using the pay command:

cli/lightning-cli pay <bolt11>

Note that there are lower-level interfaces (and more options to these interfaces) for more sophisticated use.

Further information

JSON-RPC interface is documented in the following manual pages:

For simple access to the JSON-RPC interface you can use the cli/lightning-cli tool, or the python API client.