Need help to recover money. \ stacker news ~bitcoin

pull down to refresh

50 sats \ 7 comments \ @031c33df8f 2 Jul 2023 bitcoin

I have been open channel with PSBT. I signed transaction using electrum then broadcast by lnd. After that I do bump fee by using electrum and transaction has confirmed but channel do not open. after all I do force close with "lncli closechannel -force" but closing tx not broadcast. What can I do next. Thanks

Here is log when I use "lncli pendingchannels"

{ "total_limbo_balance": "3996530", "pending_open_channels": [ ], "pending_closing_channels": [ ], "pending_force_closing_channels": [ ], "waiting_close_channels": [ { "channel": { "remote_node_pub": "0294ac3e099def03c12a37e30fe5364b1223fd60069869142ef96580c8439c2e0a", "channel_point": "c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9:0", "capacity": "4000000", "local_balance": "3996530", "remote_balance": "0", "local_chan_reserve_sat": "40000", "remote_chan_reserve_sat": "40000", "initiator": "INITIATOR_LOCAL", "commitment_type": "ANCHORS", "num_forwarding_packages": "0", "chan_status_flags": "ChanStatusBorked|ChanStatusCommitBroadcasted|ChanStatusLocalCloseInitiator", "private": false }, "limbo_balance": "3996530", "commitments": { "local_txid": "e4832caedc0120f2e7c857f5475672101219ae529bfc75e670794aafe811c62d", "remote_txid": "61634480014ee03a7ddd8f3f255b9807df7c44000384b84722ac3131742266dd", "remote_pending_txid": "", "local_commit_fee_sat": "2810", "remote_commit_fee_sat": "2810", "remote_pending_commit_fee_sat": "0" }, "closing_txid": "e4832caedc0120f2e7c857f5475672101219ae529bfc75e670794aafe811c62d" } ] }

My node run on Bitcoin Core 25 and lnd V0.16.3

view all related items

0 sats \ 3 replies \ @Hakuna 2 Jul 2023

Okay, here's what I understood:

You opened the channel of 4M, likely in a high fee environment
the channel opening transaction never made it into the mempool, likely because your node purged it from your mempool (neither your local nor the remote txid can be found in mempool.space, which has a large mempool)
since channel openings with tx longer than 2 weeks ago, LND purges the opening tx as well
so you went ahead and force-closed the channel, which never got opened, and now it's borked

All suggestions come with a disclaimer, since it's a bit of an edge case, but many runners had this due to high fee May: some things have worked, some may not. Be a bit cautious on following my remote ideas:

doublecheck whether you have the opening tx still as unspent in LND: lncli listunspent --unconfirmed_only
if not, do a SUM comparison between all unspent UTXOs and your wallet: SUM of lncli listunspent vs SUM of lncli walletbalance. It should be pretty equal in sats.
if those are the same, it's likely those sats never left your wallet. What should have been done: before the end of the 2 weeks, you should have restarted your bitcoin instance with 1GB mempool (300MB is standard), and then RBF your opening transaction. This would be the setting in bitcoin.conf:

# Constrain the mempool to the number of megabytes needed:
#maxmempool=1000

IF the sats of unspent AND wallet are the same, you could validate those are really yours and no other mempool have mined your transaction by consolidating all UTXOs into one: lncli sendcoins --addr X --sweepall --sat_per_vbyte 10 (or some vByte of your preference), where X is created via lncli newaddress

If this went through, your channel might get discarded in the next two weeks. Otherwise please come back here, if that all doesn't work, guggero's chantools might be needed to sweep committed funds. But as I read it, you have force-closed the channel, so it might not be needed.

0 sats \ 2 replies \ @031c33df8f OP 2 Jul 2023

I don't funding with internal wallet. I use -PSBT funding from Hardware Wallet signing by electrum then broadcast via Node with low fees then I need to speed up transaction I do RBF with electrum after confirmation Channel Do not opened. I nervous and do close channel with "Lncli closechannel -force"

sats is gone. https://mempool.space/tx/3c1e505390269371ac152df474867a15b260a9973c02025c1695bbf2165ad614

0 sats \ 0 replies \ @Eximpius 2 Jul 2023

Lightning nodes cant use hardware wallets yet until VLS is out of beta. It has to be a hot wallet to sign TXs on the fly for like force closed channels on the other end. I think I getting that right, its been awhile so Im not 100% positive by far.

0 sats \ 0 replies \ @031c33df8f OP 2 Jul 2023

this is original TX https://mempool.space/tx/c2beb0f19ce58a7e56a3a359dee4aa1dfb4eb2424bef22502bb61ee5b882b1e9

and this RBF TX https://mempool.space/tx/3c1e505390269371ac152df474867a15b260a9973c02025c1695bbf2165ad614

0 sats \ 1 reply \ @PlebTag 2 Jul 2023

Maybe this can help you https://github.com/blckbx/NodeTools/blob/main/htlcScan.sh

0 sats \ 0 replies \ @031c33df8f OP 2 Jul 2023

I've try and no luck sir.

Thank you

0 sats \ 0 replies \ @AJ1992 2 Jul 2023

Your best bet would be either the LNDHub telegram group or other lightning developer groups like lnbits or makerbits on telegram to get some help.

Or message benarc on telegram he might be able to help?