b45b4eaba6
Three days of on and off debugging, before I realized my server was talking to a non-testnet bitcoind. There was a bitcoind on that machine running on testnet, but it uses the same dir and config, so the --bitcoin-datadir option couldn't help. This is more certain: specify whether we're testnet on every single query. Now we can skip the attempt to parse bitcoin.conf, too. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
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.