lightninglabs / lightninglabs/loop

Charge for failed Loop Outs (30,000 Sats each time)

Open
#449 11 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Go
Stars
595
Forks
135
Avg merge
1d 8h
Merged PRs (30d)
12

Description

I've tried to Loop Out twice, but both times it's failed and has charged me 30,000 Sats (each time) for "Cost Server". I thought I shouldn't be charged if the Loop Out failed.

Expected behavior

If the Loop Out fails, I was expecting there to be no charge.

Actual behavior

I was charged 30,000 for each failed Loop Out. My node is also reflecting these charges (identified as "Prepay" in the screenshot attached)

image
image

To reproduce

I have reproduced the issue by conducting the Loop Out twice, both times is failed and both times I was charged 30,000 Sats.

System information

LIghtning Terminal

Did you install using Umbrel?
Yes

CMD or Lightning Terminal UI?
Lightning Terminal UI

0.11.2-beta from Umbrel app store

Windows 10
Intel(R) Core(TM) i5-1035G4 CPU @ 1.10GHz 1.50 GHz
250GB SSD NTFS

Windows 10 Home
Version 20H2

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Use the reported Loop Out flow in the Lightning Terminal UI on Loop 0.11.2-beta as the starting point, comparing a failed attempt with the recorded 30,000-sat “Prepay”/“Cost Server” charge. Confirm whether failed Loop Outs should retain that charge and establish a reproducible result using the reported system details and screenshots.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
payments
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.