@npub1q67p49masrcjf__d7qaq6mwh0q
stacking since: #263526
yeah I agree, but look like that option isn't available, did not specify any error either. Maybe via cli will be easier.
Anyhow, I got confirmation have zero sats on my local balance so I think I'm happy to close down the node ands start a new one, most probably s9. But if anyone has any other suggestion please let me know
Ok, this start to make sense now...
Also found this https://github.com/lightningnetwork/lnd/issues/7313 with the difference that it also has
ChansStatusDataLoss so I assume the data on my side is not lost then 🤞I'll update when I've any news
Thanks for now
tried the one that has vout =
1 and...[lncli] rpc error: code = Unknown desc = cannot close channel with state: ChanStatusRestoredTHat's great to hear. Thank you so much! Yeah for now I was just waiting to see if anything unfolded within the node.. but after a while I start questioning things and want to know why this is happening.
It's really weird that aren't force closing! how did you get to this conclusion?
wouldn't be better then to bump the fees as @TNStacker suggested?
In any case, the
closing_txid is empty on all 3 channels (I did not delete anything else apart replacing the values on remote_node_pub and channel_point with hidden) and also the Uis (TH and RTL) does not provide me that info, so how can I (re)try to force close?I wish I could do so, but if I cannot see the closing transaction ID, how can I bump the fees? any alternative way?
Thanks for your suggestion:
How did you close them? Any errors or odd behavior at the time you closed/force closed?
I do not remember if and what error I got when trying to close-mutually, that's why I ended up force-closing the remaining three channels
Did you maybe clean out the node before closing not leave enough in the wallet for anchor fees?
No I did not clean out the node before closing these last 3 channels, leaving all the sats from the previous closed channels in there on the onchain wallet
Now, using:
-
lncli listchannelsdoes not provide any output. Probably because have any active channels atm -
lncli pendingchannelsprovide the following
{ "total_limbo_balance": "0", "pending_open_channels": [ ], "pending_closing_channels": [ ], "pending_force_closing_channels": [ ], "waiting_close_channels": [ { "channel": { "remote_node_pub": "hidden", "channel_point": "hidden:0", "capacity": "43095473", "local_balance": "0", "remote_balance": "0", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_REMOTE", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "ChanStatusRestored" }, "limbo_balance": "0", "commitments": { "local_txid": "", "remote_txid": "", "remote_pending_txid": "", "local_commit_fee_sat": "0", "remote_commit_fee_sat": "0", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "" }, { "channel": { "remote_node_pub": "hidden", "channel_point": "hidden:1", "capacity": "30000000", "local_balance": "0", "remote_balance": "0", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_REMOTE", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "ChanStatusRestored" }, "limbo_balance": "0", "commitments": { "local_txid": "", "remote_txid": "", "remote_pending_txid": "", "local_commit_fee_sat": "0", "remote_commit_fee_sat": "0", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "" }, { "channel": { "remote_node_pub": "hidden", "channel_point": "hidden:0", "capacity": "10000000", "local_balance": "0", "remote_balance": "0", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_REMOTE", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "ChanStatusRestored" }, "limbo_balance": "0", "commitments": { "local_txid": "", "remote_txid": "", "remote_pending_txid": "", "local_commit_fee_sat": "0", "remote_commit_fee_sat": "0", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "" } ] }
- and
lncli listunspentprovide many UTXO
If some closing tx's are confirmed and you're just waiting on the timelock, you can power off the node and turn it on later to spend those UTXO's, it doesn't need to be online if you just want to keep your state for later use.
Ok it make sense, thanks. I'm just worried about the channels staying n that state forever! There's a way to check the status of the timelock?
;allow-circular-route=truealready on my lnd.conf but not sure how to go from there... any specific command should I run on the cli? Any reference will help