2329820460
We got horribly out-of-sync by sending a feechange and commitment after we'd re-xmitted the commitment_signed: lightning_channeld(16003): pid 16003, msgfd 19 lightning_channeld(16003): TRACE: init LOCAL: remote_per_commit = 03e40b239118ab37bd94fe48de0dbc7565a38f7f1028a20f045b4e5fcd6bbb6172, old_remote_per_commit = 03117de1f3de183697e0393e71dc3a04b04d5bec03a23e7371212bb93a67bcce7a next_idx_local = 1 next_idx_remote = 2 revocations_received = 0 feerates 39251/40838 (range 35398-204190) lightning_channeld(16003): TRACE: Read decrypt 01003b6fdc3ce9edc8524c943ebd833ae02b0fbdbb871f9bdce1c58c8637ebacfaa60a5e4dd8df4046852d783194bc3eeef10388f5a5d8983fbefe9bd0ff24b2a548282dd2eb3bc28015e039f8debf18077904342cd0146622df371c408db3fbe4eb2eb959aac6fd0771cc6a47ce270ec31042b235a2198696656c52c56d42219e4d8bd1f6d3c3b6c108c3cc0ee692d0449a4f4969eb227a9949cb8ab7229fc64f8a5d01b89ff779ac56f085d8a11942f8b5d702b2eba6d19ded7b69baf58bdfaf9443d162751dbab9f9d55e2a467cb1450bc19b832a60e0949bcd253ddc29e7b52922c009df541d8db761b04ad9862bc82ee2d86cfa0f3e730f3d01885b9977ab4200006fe28c0ab6f1b372c1a6a246ae63f74f931e8365e15a089c68d619000000000007905c000581000103aaa47d8296a795110154fa5fca7075d59a10d5914622a6d09ffe20a2ffbd5bb703bc4b957d5ad27b797d6fffa863d74e7946723e67b9084842622fe5e6357475690342423c8dab471815487b40a6ef7f06270c8343e1bbd0bfb80d22096e0ff1f15002d6cda71dde0903fde1939d7afa4f62ffed50c550d9f31f7d8b78955384473f46 lightning_channeld(16003): TRACE: Read decrypt 008854e83a6fa081ae34ddefc9ea3462689732fa3b4c5a4ea571d8d3a109f037e5a400000000000000010000000000000000000000000000000000000000000000000000000000000000000000000000000003117de1f3de183697e0393e71dc3a04b04d5bec03a23e7371212bb93a67bcce7a lightning_channeld(16003): TRACE: Got reestablish commit=1 revoke=0 lightning_channeld(16003): TRACE: Derived key 029cd90c564384a612ea608933bd63aee72543f3b3998a7cbc5ca77ca41c9cb6bc from basepoint 038401ee88c0f7dc9ada0c37a9ce5265ccabce18686649f632bc244fae71bf840d, point 03e40b239118ab37bd94fe48de0dbc7565a38f7f1028a20f045b4e5fcd6bbb6172 lightning_channeld(16003): TRACE: Creating commit_sig signature 1 30440220152767c3ea9d42b19d44ea781f07d5411de918935b674927e43d5f537769376602206cdf2b557207b02bf9ee9805017856462e53fde619d2e3d75476b5c567ea3e14 for tx 020000000154e83a6fa081ae34ddefc9ea3462689732fa3b4c5a4ea571d8d3a109f037e5a5010000000058e9fe8001a22d070000000000160014d0898dc01e4061f7c6b01dba14d1d00a4319c78c81b92f20 wscript 5221022fe5495e572f8f58cbc745e3475427ff6ff51e44dfa8586366b15d1524dbe9ca2103bfd10b2265b5ca1362eba4e7664c250e0d937717e50ec0f14cd47ff25bd6203b52ae key 022fe5495e572f8f58cbc745e3475427ff6ff51e44dfa8586366b15d1524dbe9ca lightning_channeld(16003): TRACE: peer_out WIRE_FUNDING_LOCKED lightning_channeld(16003): TRACE: peer_out WIRE_UPDATE_FEE lightning_channeld(16003): TRACE: peer_in WIRE_FUNDING_LOCKED lightning_channeld(16003): TRACE: peer_out WIRE_COMMITMENT_SIGNED lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_in WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_ANNOUNCEMENT lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_in WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_ANNOUNCEMENT lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_ANNOUNCEMENT lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_CHANNEL_UPDATE lightning_channeld(16003): TRACE: peer_out WIRE_NODE_ANNOUNCEMENT lightning_channeld(16003): TRACE: peer_out WIRE_NODE_ANNOUNCEMENT lightning_channeld(16003): TRACE: Trying commit lightning_channeld(16003): TRACE: Can't send commit: nothing to send lightning_channeld(16003): TRACE: Now dealing with deferred WIRE_CHANNEL_FEERATES lightning_channeld(16003): TRACE: Setting REMOTE feerate to 40840 lightning_channeld(16003): TRACE: Trying commit lightning_channeld(16003): TRACE: Derived key 029cd90c564384a612ea608933bd63aee72543f3b3998a7cbc5ca77ca41c9cb6bc from basepoint 038401ee88c0f7dc9ada0c37a9ce5265ccabce18686649f632bc244fae71bf840d, point 03e40b239118ab37bd94fe48de0dbc7565a38f7f1028a20f045b4e5fcd6bbb6172 lightning_channeld(16003): TRACE: Creating commit_sig signature 2 304402204f0a041f8626fd28d001cb813c1094f40ebd4b5f99bdd7a06bebaee0de35db200220702c5c62544e512e422fdc141444fddc76410cbda4bbd512d88dc864bd979780 for tx 020000000154e83a6fa081ae34ddefc9ea3462689732fa3b4c5a4ea571d8d3a109f037e5a5010000000058e9fe8001a02d070000000000160014d0898dc01e4061f7c6b01dba14d1d00a4319c78c82b92f20 wscript 5221022fe5495e572f8f58cbc745e3475427ff6ff51e44dfa8586366b15d1524dbe9ca2103bfd10b2265b5ca1362eba4e7664c250e0d937717e50ec0f14cd47ff25bd6203b52ae key 022fe5495e572f8f58cbc745e3475427ff6ff51e44dfa8586366b15d1524dbe9ca lightning_channeld(16003): TRACE: Telling master we're about to commit... lightning_channeld(16003): TRACE: Sending master WIRE_CHANNEL_SENDING_COMMITSIG lightning_channeld(16003): UPDATE WIRE_CHANNEL_SENDING_COMMITSIG lightning_channeld(16003): TRACE: ... , awaiting WIRE_CHANNEL_SENDING_COMMITSIG_REPLY lightning_channeld(16003): TRACE: Got it! lightning_channeld(16003): TRACE: Sending commit_sig with 0 htlc sigs lightning_channeld(16003): TRACE: peer_out WIRE_UPDATE_FEE lightning_channeld(16003): STATUS_FAIL_PEER_IO: peer connection broken: Connection reset by peer lightning_channeld(16003): Status closed, but not exited. Killing Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
---|---|---|
bitcoin | ||
ccan | ||
channeld | ||
cli | ||
closingd | ||
common | ||
contrib | ||
devtools | ||
doc | ||
external | ||
gossipd | ||
hsmd | ||
lightningd | ||
onchaind | ||
openingd | ||
test | ||
tests | ||
tools | ||
wallet | ||
wire | ||
.gitignore | ||
.gitlab-ci.yml | ||
.gitmodules | ||
.travis.yml | ||
LICENSE | ||
Makefile | ||
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
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>:<port>
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 throught 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.