We need to know when changes are fully committed by both sides:
1) For their HTLC_ADDs, this is when we can fulfill/fail/route.
2) For their HTLC_FAILs, this is when we can fail incoming.
For HTLC_FULFULL we don't need to wait: as soon as we know the preimage
we can propogate it.
For the moment, we simply log and assert; acting on it comes later.
Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
In this repository we're developing a reference implementation of
bitcoin lightning (see:
http://lightning.network which proposed
the original "lightning network").
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.
Final note: This is very much a testbed and work in progress; expect
All The Things to change, all the time.