lightninglabs
URGENT: Loop In Operation Stuck - Funds Not Credited to Channel
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
log from lightning terminal:
2025-11-27 19:36:31.120 [INF] LOOP: 63963a Loop in swap state: HtlcPublished
2025-11-27 19:42:52.241 [INF] LOOP: 63963a Received swap invoice update: Open
2025-11-27 19:42:52.240 [INF] LOOP: 63963a Subscribing to swap invoice [SWAP_ID_REDACTED]
2025-11-27 19:42:52.240 [INF] LOOP: 63963a P2TR htlc confirmed
2025-11-27 19:36:31.358 [INF] LOOP: 63963a Published on chain HTLC tx [TXID_REDACTED], fee: 0.00000155 BTC
2025-11-27 19:36:31.026 [INF] LOOP: 63963a Loop in swap state: Initiated
Hi @shaltay74,
This issue could indicate a liquidity issue towards your node. If the payment doesn't complete in the next 1000 blocks, your client will sweep back the on-chain htlc automatically.
You should try using the new static loop in mode instead if you want to help avoid these waits
Hi @shaltay74,
This issue could indicate a liquidity issue towards your node. If the payment doesn't complete in the next 1000 blocks, your client will sweep back the on-chain htlc automatically.
Thank you for your response. However, the logs show the invoice remains in "Open" state with no payment attempts from server since HTLC confirmation. If there were actual routing issues, we should see:
- Payment attempts in our logs
- HTLC failure codes
- Specific routing errors My node is operational with adequate inbound capacity. Waiting 1000 blocks for refund is not acceptable without proof of actual payment attempts.
In loop in you would be the receiver of the payment not the sender, therefore there are no payment attempts in your logs
It will automatically retry the payment so if you loop out you could potentially get enough inbound to receive the funds, or if you wait it will automatically sweep the on-chain funds back to yourself in 1000 blocks. There is no way to take these funds early since the lock is in the Bitcoin script itself and therefore enforced by consensus