-
Hello folks, I think I have a similar issue as described in here I am worried as I have a very large channel (1btc) opening, it is not progressing (as nothing has been broadcasted) and I fear losing funds if I don't properly manage this. Your environment The issue appeared as I tried to open a channel but I had some channels closing unconfirmed, I didn't have enough bitcoin available, hence the channel did not open. Now all my channels are ok, all the pending transactions are confirmed in the blockchain, but I still have this channel opening as pending:
Similar to what was described in issue #6048, but I don't have any limbo balance. In that issue the user rescanned opening LND and then used abandonchannel to get to a good status. Would I need to run the reset-wallet-transactions on LND? My channels are now OK, I don't have limbo balance, but I don't know if this needs to be run before the abandonchannel. Then, he used (from issue 6048): lncli abandonchannel --funding_txid --output_index what would be my own syntax, would it be lncli abandonchannel --funding_txid 4e27d78c4e4afd967a0cba5dc741a7afa108dce73ee5bfae6a7338646ca8bd93 --output_index 1 Sorry but as this is 1BTC, I prefer to double check with someone more experienced! thanks in advance for your help team. Long live Satoshi |
Beta Was this translation helpful? Give feedback.
Replies: 3 comments 14 replies
-
Do not abandon! That's dangerous (going to remove the flag from your text to avoid anyone copy/pasting it). How long ago did you open the channel? If it's been less than two weeks, please see https://docs.lightning.engineering/lightning-network-tools/lnd/unconfirmed-bitcoin-transactions#docs-internal-guid-d7a5497d-7fff-d4c9-e294-cb0cec6c9e86 (section "Channel opening" as well as "Rebroadcast transactions"). |
Beta Was this translation helpful? Give feedback.
-
I got into here because one of my peers mutually closed a channel, with a
low fee. I had all liquidity on my side, so it was important to me. He then
bumped the transaction, but the fee was again small as the fees were going
up. When I tried to bump it myself, it failed.
So this is when I tried to open a channel, using all my available funds
(thinking I was going to spend as well the output of the closing
transaction) and this got me in the state I'm currently.
The closing transaction eventually was mined, so onchain I am now ok, but
the opening transaction remains stuck as you saw.
I should have just waited, I know.
What would you suggest now?
El mar, 19 dic 2023, 23:00, Oliver Gugger ***@***.***>
escribió:
… Those three transactions also can't be found in public mempools, so they
never made it on chain. Not sure how you got into that situation. Are you
using a pruned or Neutrino chain backend? Or often use unconfirmed inputs
when sending on-chain?
—
Reply to this email directly, view it on GitHub
<#8294 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/A3QVQEDHVNCIEO2STMKY6SLYKIFAFAVCNFSM6AAAAABA3VCPHSVHI2DSMVQWIX3LMV43SRDJONRXK43TNFXW4Q3PNVWWK3TUHM3TSMBSGI4TK>
.
You are receiving this because you authored the thread.Message ID:
***@***.***>
|
Beta Was this translation helpful? Give feedback.
-
Okay, so given that If all funds are accounted for in your wallet balance after that, I think you're fine to continue. If not, you probably need to run with I would suggest to then spend all your coins into a new address (either a new channel with enough fees or just consolidate everything into a new wallet address using |
Beta Was this translation helpful? Give feedback.
Thanks. Looks like some inputs to the funding transaction also cannot be found... So to make sure they can never be confirmed either, can you please repeat the process (probably just grepping then posting the transaction dump here, no extra restart of
lnd
required as those probably already have been logged) for those transaction IDs:08d397514cf3b445229153be843291cf86c811a6459d847aed0fb422b20f5085
74d4efb036c2c63a1e43a94ec7608f73242d3e53eead30bf74d5cbbb8d58c9d3
b3f476b16861b6b7894a4746b0ef459d01022ed7c72947643f45d96aa09c0461
I know it's tedious, but you really want to make sure the transaction can never confirm before abandoning it. Otherwise it gets reeeally complicated to rescue.