Funds stuck on Force Close Channel with negative blocks till maturity anchor LOST #10868
Unanswered
medisoft
asked this question in
Troubleshooting
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hello! I have 3 force closed TX, with negative blocks til maturity. I verified that the closing tx are in the blockchain, and are confirmed, and that my bitcoind node have them. I also looked for pending sweeps and it is empty, looked for the outputs for the closing transactions and seems that they are used by my lnd wallet.
I'm not totally sure that the funds were recovered, and neither I'm sure why the limbo balance and the pending force close channels are still there.
{ "total_limbo_balance": "611953", "pending_open_channels": [], "pending_closing_channels": [], "pending_force_closing_channels": [ { "channel": { "remote_node_pub": "0290c9722262f78df35002923e202d67b53a51153d69970956862d984da1bc6351", "channel_point": "79eef528b8e393d1a5f841ea3c0f577d223e2ca99f2baa65607afb2fcff25d30:1", "capacity": "3000000", "local_balance": "30754", "remote_balance": "2942684", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_LOCAL", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "", "private": false, "memo": "", "custom_channel_data": "" }, "closing_txid": "5fbb085fe2ee1c7cbbad8c0bb642638a5d9a957463ddcd9f0a37ba9e83bc816f", "limbo_balance": "55756", "maturity_height": 949045, "blocks_til_maturity": -2953, "recovered_balance": "0", "pending_htlcs": [ { "incoming": true, "amount": "25002", "outpoint": "5fbb085fe2ee1c7cbbad8c0bb642638a5d9a957463ddcd9f0a37ba9e83bc816f:2", "maturity_height": 949043, "blocks_til_maturity": -2955, "stage": 1 } ], "anchor": "LOST" }, { "channel": { "remote_node_pub": "0304b5d7f02400b2c34f5f1ff10e68a1125e5bce4d3a513c7a8d0bba912451773a", "channel_point": "d397e0a7eaf834e46972c8032facb6c3ddaee8d1a2ee261859ad4f5cb25f0f5c:1", "capacity": "3000000", "local_balance": "470539", "remote_balance": "2500557", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_LOCAL", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "", "private": false, "memo": "", "custom_channel_data": "" }, "closing_txid": "0f8caa3457da5be246b465f068c7201aa05493cb2a80586ab9c3edf2ac156a9f", "limbo_balance": "495541", "maturity_height": 949045, "blocks_til_maturity": -2953, "recovered_balance": "0", "pending_htlcs": [ { "incoming": true, "amount": "25002", "outpoint": "0f8caa3457da5be246b465f068c7201aa05493cb2a80586ab9c3edf2ac156a9f:2", "maturity_height": 949043, "blocks_til_maturity": -2955, "stage": 1 } ], "anchor": "LOST" }, { "channel": { "remote_node_pub": "0324ba2392e25bff76abd0b1f7e4b53b5f82aa53fddc3419b051b6c801db9e2247", "channel_point": "4c7703b59dfeb3fe39f51ce5fabc3d0c1f72bf7f3e1d713ddd7147c89100ad8b:1", "capacity": "4000000", "local_balance": "60656", "remote_balance": "3936664", "local_chan_reserve_sat": "0", "remote_chan_reserve_sat": "0", "initiator": "INITIATOR_LOCAL", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "", "private": false, "memo": "", "custom_channel_data": "" }, "closing_txid": "10718ea31ff968a6d66bff3815e4fc9b5f93859b4564f39178d11d30b507d386", "limbo_balance": "60656", "maturity_height": 948722, "blocks_til_maturity": -3276, "recovered_balance": "0", "pending_htlcs": [], "anchor": "LOST" } ], "waiting_close_channels": [] }pending sweeps
{ "pending_sweeps": [] }All of them return null, so the outputs are already spent.
Something that is different from other posts in the discussion group:
This does not look like the usual case where the force-close output is mature but still waiting to be swept. In this case, the relevant force-close outputs are already spent. The local outputs were spent by LND wallet transactions labeled 0:sweep and recognized by lncli wallet gettx. However, lncli pendingchannels still reports the same channels under pending_force_closing_channels with recovered_balance = 0 and the original limbo_balance.
Is this expected if the HTLC outputs were spent by non-wallet transactions?
Should contractcourt/channel arbitrator automatically mark these channels as resolved once the outputs are spent?
Is there a safe way to force LND to reconcile the close arbitrator state without running reset-wallet-transactions, since my bitcoind backend is remote and a full wallet rescan is very slow?
Are there specific logs or DB state entries I should inspect?
What could be the problem? And the solution?
Thank you for your help!
All reactions