6 commits

Author	SHA1	Message	Date
Janus	f618bb4a67	lnhtlc: handle settles like adds (asymmetrical across ctns)	2019-08-20 09:03:11 +02:00
SomberNight	3a2ab149b9	lnchannel: add_htlc and receive_htlc now take and return UpdateAddHtlc ... also fix undefined vars in _maybe_forward_htlc and _maybe_fulfill_htlc in lnpeer	2019-08-20 09:03:11 +02:00
ThomasV	459f9aaee7	lnchannel: reformatting	2019-08-20 09:03:11 +02:00
ThomasV	5d26f51ad0	lnchannel: fix error message	2019-08-20 09:03:11 +02:00
ThomasV	a40207cbbb	Refactor LNPeer in order to support HTLC forwarding: ... 1. Do not perform channel updates in coroutines, because they would get executed in random order. 2. After applying channel updates, wait only for the relevant commitment (local or remote) and not for both, because local and remote might be out of sync (BOLT 2). 3. When waiting for a commitment, wait until a given ctn has been reached, because a queue cannot be shared by several coroutines	2019-08-20 09:03:11 +02:00
ThomasV	3dce65dc73	Rename lnchan, lnchannel_verifier, lnbase ... Auto-completions are a pain if files share a long prefix	2019-08-20 09:03:11 +02:00

Renamed from electrum/lnchan.py (Browse further)