Christian Decker 8e2abfcc70 jsonrpc: Added 'getchannels' RPC method.
'getchannels' returns a 'channels' array containing an object for each
known channel. Each channel object represents one direction of a
bidirectional channel, with a from and a to node ID along with the fees
for that direction. This matched the internal storage of channels and
allows unbalanced fees for each direction.
2016-10-02 12:22:28 +02:00
2016-09-06 13:47:07 +09:30
2016-07-01 12:00:17 +09:30
2016-08-18 22:07:35 -04:00
2016-01-22 06:41:46 +10:30
2016-09-14 05:28:51 +09:30
2016-08-18 14:25:13 +09:30
2016-08-18 14:25:13 +09:30
2016-07-01 12:00:17 +09:30
2016-08-18 14:23:46 +09:30
2016-09-06 16:47:48 +09:30
2016-09-07 23:49:39 +02:00
2016-09-07 23:49:39 +02:00
2016-09-14 05:28:51 +09:30
2016-09-14 05:28:51 +09:30

Lightning Protocol Reference Implementation

In this repository we're developing a reference implementation of bitcoin lightning (see: http://lightning.network which proposed the original "lightning network").

This implementation is being developed in parallel with the protocol definition, which you can find on my fork of the protocol description repository.

If you're interested in using the daemon to test payments, the JSON-RPC interface is documented in the following manual pages:

So far, we have inter-node encryption and transaction negotiation.

Routing between non-adjacent nodes is currently done manually using the 'dev-addroute' command; later on daemons will advertise their IP addresses, and publish routes and fees. These details are currently being hashed out on the mailing list and the IRC channel #lightning-dev on Freenode.

Final note: This is very much a testbed and work in progress; expect All The Things to change, all the time.

Welcome aboard!

Rusty.

Description
No description provided
Readme MIT 55 MiB
Languages
C 74.9%
Python 20.7%
Rust 1.5%
Makefile 1.1%
Assembly 0.9%
Other 0.8%