-
Notifications
You must be signed in to change notification settings - Fork 119
Loop in stuck, could somebody help me or provide more information? #939
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
Comments
Hi, our Server is still trying to pay the invoice. It could be that your inbound is not sufficient and our node is not able to find a route. |
I appreciate you taking time to respond. It's very strange that it isn't going through. I have a channel with more than sufficient inbound liquidity to handle the transaction. In fact, rebalancing the channel was the aim of the loop-in to begin with. As shown in the picture here. Any advice on what my next steps should be? |
If the swap payment hasn't made it until now chances are that the swap won't be successful. The funds your client sent to the htlc address will be automatically swept once the htlc contract expires. For more flexibility in these scenarios you could use static address loop-ins that allow you to retry the swap if it fails. For more info see https://docs.lightning.engineering/lightning-network-tools/loop/static-loop-in-addresses |
After around 1,000 confirmations the balance was refunded on-chain. I'll be closing the thread now. Thanks everyone. |
Today I was rebalancing some of my channels by using Lightning Terminal's Loop-In feature. I am using Umbrel. Of the three loops in I did today two succeeded. Unfortunately, the largest loop-in is still processing and stuck in a state of "HTLC Published" and has been all day now. Is there any information anybody could provide or help me better understand the issue or how to move forward?
This is the mempool transaction for the loop. At the time of writing it has well over a day's worth of confirmations: https://mempool.space/tx/7c662f1529bb37ea98888bb112646666b7b83f455bd32bf209bc0875cf4e8d71
I have an unpaid invoice waiting to receive the funds. The payment hash is 7b951eb94713f373bf9adef491c1a0836cf9190a3e1a9e3d45dd8d8e4362504c
Any information provided would be greatly appreciated.
The text was updated successfully, but these errors were encountered: