You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
Rusty Russell 42c9cb58c7 channeld: rename commit_index to next_index. 8 years ago
bitcoin script: Use pkh to construct p2pkh output scripts 8 years ago
ccan ccan: update to fix io_wake bug. 8 years ago
contrib contrib/pylightning: allow getpeer with log level. 8 years ago
daemon bitcoind: peer argument to bitcoind_sendrawtx is unused 8 years ago
doc doc: Adding compiled manpage 8 years ago
libsodium@fce6852d64 libsodium: add as submodule. 8 years ago
libwally-core libwally: Re-adding missing gen_context file 8 years ago
lightningd channeld: rename commit_index to next_index. 8 years ago
secp256k1 libsecp256k1: update. 9 years ago
test struct secret: use everywhere. 8 years ago
tests tests/test_lightningd.py: make test less flaky. 8 years ago
tools tools/generate-wire.py: unmarshall zero-length arrays as NULL. 8 years ago
wallet wallet_get_newindex: encapsulate routine to get a new keyindex. 8 years ago
wire channeld: update to send next commitment number on connection reestablish. 8 years ago
.gitignore Update .gitignore files. 8 years ago
.gitlab-ci.yml Add .gitlab-ci.yml 8 years ago
.gitmodules libsodium: add as submodule. 8 years ago
.travis.yml travis: Passing through some env variables 8 years ago
HACKING.md controlled_time: remove 8 years ago
INSTALL.md doc: Updating README and related documentation 8 years ago
LICENSE licensing: Make license explicit. 9 years ago
Makefile Makefile: use -f with pytest, to exit on first failure. 8 years ago
README.md doc: Updating README and related documentation 8 years ago
TODO.md TODO: remove to-dones. 8 years ago
check-bolt.c check-bolt: use new BOLTs. 8 years ago
close_tx.c permute_tx: reintroduce permute map. 8 years ago
close_tx.h Use global secp256k1_ctx instead of passing it around. 8 years ago
find_p2sh_out.c struct bitcoin_tx: remove explicit lengths, use tal_len()/tal_count() 8 years ago
find_p2sh_out.h Remove unused script functions now we use witness. 9 years ago
irc.c daemon/dns: hand netaddr we connected to through to callback. 8 years ago
irc.h Merge remote-tracking branch 'origin/pr/44' 8 years ago
lightning.pb-c.c bitcoin/preimage: struct preimage. 8 years ago
lightning.pb-c.h bitcoin/preimage: struct preimage. 8 years ago
lightning.proto bitcoin/preimage: struct preimage. 8 years ago
opt_bits.c opt_bits: parsing routines for 'bits' == 100 satoshi. 10 years ago
opt_bits.h header cleanup: sort include lines into alpha order, after config.h 9 years ago
overflows.h channel: support HTLC forwarding. 8 years ago
permute_tx.c permute_tx: generic pointer map. 8 years ago
permute_tx.h permute_tx: generic pointer map. 8 years ago
protobuf_convert.c bitcoin/preimage: struct preimage. 8 years ago
protobuf_convert.h bitcoin/preimage: struct preimage. 8 years ago
remove_dust.h channel: remove htlcs array. 8 years ago
type_to_string.c type_to_string: move formatting to appropriate files. 8 years ago
type_to_string.h struct secret: use everywhere. 8 years ago
utils.c utils: add tal_hex() helper. 8 years ago
utils.h utils: add tal_hex() helper. 8 years ago
version.c getinfo: add version information 8 years ago
version.h options: --help and --version are early args. 8 years ago

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 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.