Core Lightning — Lightning Network implementation focusing on spec compliance and performance
Go to file
Christian Decker 19c030ea1f routing: Make routing_state aware of its own ID
This is used to identify our own announcements.

Signed-off-by: Christian Decker <decker.christian@gmail.com>
2017-12-17 02:44:20 +00:00
bitcoin Share similar code between bitcoin_witness_p2sh_p2wpkh and bitcoin_scriptsig_p2sh_p2wpkh. 2017-12-10 12:46:25 +01:00
ccan ccan: update to get new ccan/io changes. 2017-10-25 18:34:35 +02:00
channeld Remove redundant code 2017-12-11 03:38:37 +00:00
cli Makefiles: simplify dependencies. 2017-08-29 17:54:14 +02:00
closingd Remove trailing whitespace 2017-12-11 03:35:59 +00:00
common options: don't leak memory when people override options. 2017-12-13 22:46:10 +01:00
contrib docker: Added clang to build dependencies 2017-12-12 02:31:03 +00:00
devtools bolt11: handle r value fee spec change. 2017-12-12 11:45:44 +01:00
doc Fix typos 2017-12-08 13:07:20 +01:00
external Makefile: clean needs to do more, distclean should remove everything. 2017-11-24 13:29:03 +01:00
gossipd routing: Make routing_state aware of its own ID 2017-12-17 02:44:20 +00:00
hsmd Modify hsm_sign_withdrawal to transmit scriptpubkey to withdraw to, rather than pkh. 2017-12-13 03:10:04 +00:00
lightningd bitcoind: don't leak memory on every call to bitcoin-cli. 2017-12-13 22:46:10 +01:00
onchaind Remove trailing whitespace 2017-12-11 03:35:59 +00:00
openingd Remove trailing whitespace 2017-12-11 03:35:59 +00:00
test update-mocks: move mock generation into tools/, fix and generalize. 2017-09-03 02:01:54 +02:00
tests Add test for withdrawing to P2WPKH and P2WSH. 2017-12-14 03:36:40 +00:00
tools Remove trailing whitespace 2017-12-11 03:35:59 +00:00
wallet wallet.c: Minor leak in wallet_invoices_load. 2017-12-15 10:41:54 +00:00
wire cleanup: Use check_act* in handshake and remove unused static inline 2017-12-12 02:31:03 +00:00
.gitignore Add build artefacts generated during "make"/"make check" to .gitignore 2017-12-08 13:07:50 +01: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: Add clang build to build matrix 2017-12-12 02:31:03 +00:00
LICENSE licensing: Make license explicit. 2016-01-22 06:41:46 +10:30
Makefile Fix typos 2017-12-08 13:07:20 +01:00
README.md README.md: Add link to waitanyinvoice 2017-12-14 03:07:20 +00:00

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 git build-essential libtool libgmp-dev libsqlite3-dev python python3
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.

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>

# Retrieves the raw transaction <rawtx>
bitcoin-cli -testnet getrawtransaction <txid>

# Notifies `lightningd` that there are now funds available:
cli/lightning-cli addfunds <rawtx>

Eventually lightningd will include its own wallet making this transfer easier, but for now this is how it gets its funds. 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.

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 6 confirmations in order for the channel to be usable. You can check the status of the channel using cli/lightning-cli getpeers, which after 1 confirmation should say that the status is in Normal operation. After 6 confirmations you can use cli/lightning-cli getchannels to verify that the channel shows up in the list of open channels.

Receiving and receiving payments

Payments in Lightning are invoice based. The recipient creates an invoice with the expected <amount> in millisatoshi, a <label> and a <description>:

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

This returns a random value called rhash that is part of the invoice. The recipient needs to communicate its ID <recipient_id>, <rhash> and the desired <amount> to the sender.

The sender needs to compute a route to the recipient, and use that route to actually send the payment. The route contains the path that the payment will take through the Lightning Network and the respective funds that each node will forward.

route=$(cli/lightning-cli getroute <recipient_id> <amount> 1 | jq --raw-output .route -)
cli/lightning-cli sendpay "$route" <rhash>

Notice that in the first step we stored the route in a variable and reused it in the second step. lightning-cli should return a preimage that serves as a receipt, confirming that the payment was successful.

This low-level interface is still experimental and will eventually be complemented with a higher level interface that is easier to 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.