Lightning channel stuck while opening due to low fee
See original GitHub issueI’m using Electrum from master branch. I tried to open a new channel to a node and set the fee manually using the static method. Looks like it wasn’t enough because I’ve got this in the log (there were no GUI error messages and no transactions appeared at the history tab):
I | transaction | adding signature for <nodeid>
D | transaction | is_complete True
I/n | network | broadcast_transaction error [DO NOT TRUST THIS MESSAGE]: RPCError(1, 'the transaction was rejected by network rules.\n\ninsufficient fee, rejecting replacement e249d9
535bef20c16b4dc3338a6d313e69b2d606f2762851942769e0a4ba5d23; new feerate 0.00010000 BTC/kvB <= old feerate 0.00010000 BTC/kvB\n[...]')
I/n | network | error: could not broadcast open_channel e249d9535bef20c16b4dc3338a6d313e69b2d606f2762851942769e0a4ba5d23, insufficient fee
Your transaction is trying to replace another one in the mempool but it does not meet the rules to do so. Try to increase the fee.
I don’t see the funding transaction in the history and it clearly hasn’t been broadcasted (this txid isn’t found on any block explorers). The channel now is stuck in REESTABLISHING
peer state, I tried to force close it (unsuccessfully, because there’s no funding tx). My balance is unchanged so the only problem is this stuck channel that I can’t remove. lnd has abandonchannel
command that I believe does exactly what I want, just remove it no questions asked… but I can’t find anything like that in the Electrum console or GUI.
Issue Analytics
- State:
- Created 2 years ago
- Comments:5 (3 by maintainers)
Top GitHub Comments
Yes, my mistake, should have done an import
from electrum.lnchannel import ChannelState
and then take the corresponding enumsChannelState.FORCE_CLOSING
as an argument for the set_state method.I can comment this line out but would be good to fix it!
After removing the line I get another error:
These enums aren’t available from the console it seems and integers aren’t a valid substitute. However, looks like it somehow worked and the channel state changed to
REDEEMED
, I was able to delete it after that. But this scenario should be fixed, it happened exactly before the recent tx flood.