5e7b3d02a1
We now keep a list of commitment transaction states for "us" and "them", as well as a "struct channel_state" for staged changes. We manipulate these structures as we send out packets, receive packets, or receive acknowledgement of packets. In particular, we update the other nodes' staging_cstate as we send out our requests, and update our own staging_cstate are we receive acks. When we receive a request, we update both (as we immediately send out our ack). The RPC output is changed; rather than expose the complexity, we expose our last committed state: what would happen if we have to drop to the blockchain now. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au> |
||
|---|---|---|
| bitcoin | ||
| ccan | ||
| daemon | ||
| doc | ||
| secp256k1 | ||
| test | ||
| test-cli | ||
| .gitignore | ||
| .gitmodules | ||
| close_tx.c | ||
| close_tx.h | ||
| commit_tx.c | ||
| commit_tx.h | ||
| find_p2sh_out.c | ||
| find_p2sh_out.h | ||
| funding.c | ||
| funding.h | ||
| HACKING.md | ||
| INSTALL.md | ||
| LICENSE | ||
| lightning.pb-c.c | ||
| lightning.pb-c.h | ||
| lightning.proto | ||
| Makefile | ||
| names.c | ||
| names.h | ||
| opt_bits.c | ||
| opt_bits.h | ||
| overflows.h | ||
| permute_tx.c | ||
| permute_tx.h | ||
| protobuf_convert.c | ||
| protobuf_convert.h | ||
| README.md | ||
| state_types.h | ||
| state.c | ||
| state.h | ||
| TODO.md | ||
| version.c | ||
| version.h | ||
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 [https://github.com/rustyrussell/lightning](on my fork of the protocol description repository).
So far, we are working on the [https://github.com/rustyrussell/lightning/blob/master/communications/low/01-encryption.md](inter-node encryption) and [https://github.com/rustyrussell/lightning/blob/master/communications/low/02-wire-protocol.md](transaction negotiation) phases.
Later steps will enhance the protocol to network individual daemons, advertise their IP addresses, publish routes and fees, and use that information to pay specific nodes. These details are currently being hashed out on the mailing list and the IRC channel #lightning-dev on Freenode.
The protocol requires features not currently in bitcoin, but can be tested with bitcoin (on testnet) with OP_NOP substitution.
Final note: This is very much a testbed and work in progress; expect All The Things to change, all the time.
Welcome aboard!
Rusty.