-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Force close stuck, TX disappeared #1091
Comments
I noticed your issue and wanted to point to my issue which appears similar. |
|
Looking at the chain, we see: https://www.smartbit.com.au/tx/7cbc012a8c8c1472d560b77a5dbe9759288647d671aa550925bc0d59c4ada2e9 Which has both outputs spent, which means that all funds have been fully swept by |
No money was lost, if you follow the link above, you'll see that all the funds were properly swept. |
In response to your request for logs:
Thanks for the clarification. That puts me at ease (hopefully it fixes not just the issue but will also remove this phantom / stuck tx). Feel free to close this ticket. Thanks again. |
same as me; Where is the 59K Satoshi? Initial Balance; Payments stuck for a few days now afer closeallchannels forced. lncli pendingchannels Current Balance; net in;1006634 Loss;-59454 Never made a payment, paid additional fee's on-chain. Where did it go? |
@8KSS for those last two channels, everything has been fully resolved on-chain, meaning all funds have been swept. It's possible that the sum of your fees across all those channels went up to 59k satoshis, as there were multiple instances a transaction fee is paid: when opening a channel, when closing a channel, when sweeping time-locked funds from a channel. That co-op close issue has been fixed as of the latest version of master. Do you have start up logs for those force close channels that've actually been finalized? Thanks! |
Also if you do |
It's also the case that if you have any channels which at closing time had a "dusty" output, then those aren't able to be claimed, and will instead go to miner's fees. |
{ |
so total fees, 11187. 6000 was to get back to on-chain |
@8KSS upon updating to the latest master, do the pending close transactions still persist? Also note that intermediate sweeping transaction won't show up in |
Nope didn’t spend anything. |
For what it's worth, mine's still there.
lncli version 0.4.1 commit=b0709b45f7af9314481d06e617b1cee088fd708e |
We recently fixed another bug related to sending out notification of spends that are already confirmed in the chain. Note that this only affected the |
Is this something that should be cleared up in the latest version? lnd version 0.4.1-beta commit=86fd9e361e04716b6a0d2e7146d6c19c0b4f05b5 Still seeing this stuck channel with the non-existant TX :(
|
Yes, as in we'll always only act on the ultimately confirmed commitment transaction. In your case, both outputs have been fully spent on the transaction, meaning that if you had any funds, they've been swept into the wallet. |
By latest I meant what I just pulled, commit 86fd9e3. As you can see, that channel is still stuck there, it's been there for weeks probably. I'm just wondering when it'll expire or get removed by LND. Thanks. |
Yep, that's the latest commit. What I mean is that all funds have been fully recovered by |
That'll have to work, thanks. In the long run it'd be preferable if channels couldn't get stuck this way in the first place to have to 'clean up' after them. I don't know how easily this is doable. I'm sure there are challenges. But still. Many ghost channels piling up over time does not sound like a good thing to live with and it's suspcious that the solution could be automated. Anyway, I'm sure there are priorities, so for now a manual garbage collector is OK. Thanks in advance. |
Totally, that PR that just landed clears up all instances of weird situations like this we're aware of.
Defiantly, they shouldn't pile up at all. What you're seeing is lingering behavior of the recently fixed bug. When we fixed the bug, we could have remove the faulty channels in an automated fashion. But then with that, there's a risk that we'd accidentally remove a non-faulty channel. As a result, it's safer to give users tools to pin point these faulty channels and remove them manually. |
Some time ago a channel was closed. It's been sitting in pending_forced for very long so now I checked the TXID and it isn't in the blockchain, isn't in the mempool.
How can I get LND to give me the raw transaction so I can attempt to re-broadcast it? I'm worried about opening any more channels if I can lose the money because of failed closing transactions. I'd prefer to know what happened here and also be able to resolve it.
lnd version 0.4.1-beta commit=13945de8060ad42e077988c1cf69e205dc11e528 on a Debian with Bitcoind (0.16) as backend.
The text was updated successfully, but these errors were encountered: