tlnchannel: explain why if REMOTE f-closes we remain OPEN until mined - electrum - Electrum Bitcoin wallet
HTML git clone https://git.parazyd.org/electrum
DIR Log
DIR Files
DIR Refs
DIR Submodules
---
DIR commit b55f6430f24c374c3c50616e53adfc298106a243
DIR parent a03d8dc6ac9405e7e01ee89e6507417d0028ed2b
HTML Author: SomberNight <somber.night@protonmail.com>
Date: Fri, 19 Jun 2020 16:31:09 +0200
lnchannel: explain why if REMOTE f-closes we remain OPEN until mined
Diffstat:
M electrum/lnchannel.py | 4 +++-
1 file changed, 3 insertions(+), 1 deletion(-)
---
DIR diff --git a/electrum/lnchannel.py b/electrum/lnchannel.py
t@@ -80,7 +80,9 @@ class ChannelState(IntEnum):
OPEN = 3 # both parties have sent funding_locked
SHUTDOWN = 4 # shutdown has been sent.
CLOSING = 5 # closing negotiation done. we have a fully signed tx.
- FORCE_CLOSING = 6 # we force-closed, and closing tx is unconfirmed. (otherwise we remain OPEN)
+ FORCE_CLOSING = 6 # we force-closed, and closing tx is unconfirmed. Note that if the
+ # remote force-closes then we remain OPEN until it gets mined -
+ # the server could be lying to us with a fake tx.
CLOSED = 7 # closing tx has been mined
REDEEMED = 8 # we can stop watching