lightninglabs / lightninglabs/loop
URGENT: Loop In Operation Stuck - Funds Not Credited to Channel
- Dominant language
- Go
- Stars
- 595
- Forks
- 135
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 12
Description
Dear Lightning Labs Support,
I'm experiencing a critical issue with a Loop In operation that appears to be stuck.
Problem Summary:
Loop In operation for 1,490,000 sats shows "HTLC Published" status
On-chain transaction has 121+ confirmations
Funds have not been credited to any Lightning channel
Operation has been stuck in this state for over 24 hours
Technical Details (Safe to Share):
Operation Type: Loop In
Amount: 1,490,000 sats
Status: HTLC Published (stuck)
Confirmations: 121 blocks
Timestamp: November 27, ~7:36 PM
Evidence of Issue:
Lightning Terminal interface shows permanent "HTLC Published" status
Channel balances remain unchanged pre/post operation
Wallet balance does not reflect the Loop In amount
On-chain transaction confirmed but Lightning portion incomplete
What I've Verified:
All channels are active and healthy
Node is fully synced (chain + graph)
No error messages in logs related to this operation
Previous Loop operations completed successfully
Request:
Please investigate this stuck operation and either:
Complete the Loop In and credit funds to my Lightning channels, OR
Initiate a refund of the 1,490,000 sats
I'm available to provide additional technical details via private channels if needed.
Additional Context:
LND version: 0.20.0-beta
Loop operation via Lightning Terminal web interface
All other node functions operating normally
Thank you for your urgent attention to this matter.
Best regards,
Alex

Contributor guide
No contributing guide indexed for this repository
Research direction
The report concerns a Loop In operation shown in the Lightning Terminal interface, with LND 0.20.0-beta and an on-chain transaction confirmed 121+ times. Start by reviewing how the operation's HTLC Published state is tracked and reconciled; done means identifying why this operation did not credit a channel or reach a refund path, with the funds safely resolved.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend, payments
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100