Core Lightning — Lightning Network implementation focusing on spec compliance and performance
Go to file
Christian Decker a1faccb9dc walletrpc: Split owned output detection out and use it for change
Splitting the detection for outputs that we own into a separate
`wallet_extract_owned_outputs` function and use it when the broadcast
succeeds to re-add the change output back to the database.
2017-06-23 16:02:20 +09:30
bitcoin script: Use pkh to construct p2pkh output scripts 2017-06-23 16:02:20 +09:30
ccan ccan: update to fix io_wake bug. 2017-06-07 09:19:04 +09:30
contrib contrib/pylightning: allow getpeer with log level. 2017-04-29 10:30:10 +02:00
daemon bitcoind: peer argument to bitcoind_sendrawtx is unused 2017-06-23 16:02:20 +09:30
doc doc: Adding compiled manpage 2017-02-27 14:55:53 +01:00
libsodium@fce6852d64 libsodium: add as submodule. 2017-01-11 09:29:40 +10:30
libwally-core libwally: Re-adding missing gen_context file 2017-02-21 16:54:05 +01:00
lightningd wallet: move can_spend to wallet.c and json_addfunds to walletrpc.c 2017-06-23 16:02:20 +09:30
secp256k1 libsecp256k1: update. 2016-07-01 12:00:17 +09:30
test struct secret: use everywhere. 2017-05-09 11:43:35 +09:30
tests wallet: Add unit test for withdrawal 2017-06-23 16:02:20 +09:30
tools tools/generate-wire.py: handle marshal/unmarshal of enum types. 2017-06-23 09:29:42 +09:30
wallet walletrpc: Split owned output detection out and use it for change 2017-06-23 16:02:20 +09:30
wire lightningd: update BOLT to add channel_reestablish message. 2017-06-23 09:29:42 +09:30
.gitignore Update .gitignore files. 2017-05-12 12:59:09 +02:00
.gitlab-ci.yml Add .gitlab-ci.yml 2016-12-11 13:24:27 +01:00
.gitmodules libsodium: add as submodule. 2017-01-11 09:29:40 +10:30
.travis.yml travis: Passing through some env variables 2017-05-07 12:06:56 +09:30
check-bolt.c check-bolt: use new BOLTs. 2017-01-04 14:09:20 +10:30
close_tx.c permute_tx: reintroduce permute map. 2017-02-07 12:14:22 +10:30
close_tx.h Use global secp256k1_ctx instead of passing it around. 2016-12-02 18:12:58 +10:30
find_p2sh_out.c struct bitcoin_tx: remove explicit lengths, use tal_len()/tal_count() 2017-01-25 11:03:55 +10:30
find_p2sh_out.h Remove unused script functions now we use witness. 2016-04-24 20:09:39 +09:30
HACKING.md controlled_time: remove 2016-11-09 18:54:15 +10:30
INSTALL.md doc: Updating README and related documentation 2017-05-20 20:02:45 +09:30
irc.c daemon/dns: hand netaddr we connected to through to callback. 2017-05-25 14:24:47 +09:30
irc.h Merge remote-tracking branch 'origin/pr/44' 2016-10-17 12:31:19 +10:30
LICENSE licensing: Make license explicit. 2016-01-22 06:41:46 +10:30
lightning.pb-c.c bitcoin/preimage: struct preimage. 2017-02-02 14:48:00 +10:30
lightning.pb-c.h bitcoin/preimage: struct preimage. 2017-02-02 14:48:00 +10:30
lightning.proto bitcoin/preimage: struct preimage. 2017-02-02 14:48:00 +10:30
Makefile Makefile: use -f with pytest, to exit on first failure. 2017-06-23 09:29:42 +09:30
opt_bits.c opt_bits: parsing routines for 'bits' == 100 satoshi. 2015-06-07 13:52:04 +09:30
opt_bits.h header cleanup: sort include lines into alpha order, after config.h 2016-01-22 06:38:08 +10:30
overflows.h channel: support HTLC forwarding. 2017-05-02 11:47:19 +02:00
permute_tx.c permute_tx: generic pointer map. 2017-02-21 15:15:29 +10:30
permute_tx.h permute_tx: generic pointer map. 2017-02-21 15:15:29 +10:30
protobuf_convert.c bitcoin/preimage: struct preimage. 2017-02-02 14:48:00 +10:30
protobuf_convert.h bitcoin/preimage: struct preimage. 2017-02-02 14:48:00 +10:30
README.md doc: Updating README and related documentation 2017-05-20 20:02:45 +09:30
remove_dust.h channel: remove htlcs array. 2016-08-18 14:23:46 +09:30
TODO.md TODO: remove to-dones. 2016-09-06 16:47:48 +09:30
type_to_string.c type_to_string: move formatting to appropriate files. 2017-01-04 14:07:15 +10:30
type_to_string.h struct secret: use everywhere. 2017-05-09 11:43:35 +09:30
utils.c utils: add tal_hex() helper. 2017-01-10 15:19:25 +10:30
utils.h utils: add tal_hex() helper. 2017-01-10 15:19:25 +10:30
version.c getinfo: add version information 2016-09-14 05:28:51 +09:30
version.h options: --help and --version are early args. 2017-01-04 14:04:15 +10:30

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 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 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 libprotobuf-c-dev 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:master

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

Once bitcoind has synchronized with the testnet/regtest network, you can start lightningd with the following command:

lightningd/lightningd --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>
daemon/lightgning-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:
daemon/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>:<port> and has the node ID <node_id>:

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

This opens a connection and, on top of that connection, then opens a channel. You can check the status of the channel using daemon/lightning-cli getpeers. The funding transaction needs to confirm in order for the channel to be usable, so wait a few minutes, and once that is complete it getpeers should say that the status is in Normal operation.

Receiving and receiving payments

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

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

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:

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

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 daemon/lightning-cli tool, or the python API client.