spesmilo / spesmilo/electrum

Bitcoin Lightning payment stuck after 30 attempts, are the funds lost?

Open
#8,730 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
Python
Stars
8.6k
Forks
3.5k
Avg merge
2d 8h
Merged PRs (30d)
61

Description

I'm using Electrum 4.4.6 AppImage on Ubuntu 22.04, I'm not using trampoline routing, and I only have one channel open with ACINQ. On December 2nd I tried to pay an invoice but the payment got stuck on the 30th attempt, so I "deleted" the payment from the list of invoices and paid with another wallet. Since then, I have had an "HTLC in current commitment transaction" in the channel details, and (apparently) I can't send more than ~0.0018 even tho I have ~0.0055...
image
EDIT: Payment hash: 96dd791e762253e7c11721a61e4281bc2c516f5410984099f67796d9f20d846f
image

Now, I thought that when the "CLTV expiry" block number was mined everything would return back to normal... but it didn't.

How can I solve this without closing the channel? (another detail is that in this state it only lets me force-close)

I'm attaching two more screenshots that may or may not provide additional information that might help you understand the issue:
image
This is the transaction details, note the insanely high fee...
image
Here's the invoice:
lnbc2364090n1pjkhaulpp5da49gmju0m0vcp9us4uw6pqx60smqjehvv0u3rjyq8tjxmnkakcsd29gpkxuupjwppx7apq95sygetscwehx6t5dusx2m3qvashyctwwnp66cfqfaexgetwyq3nvdfkvfnrwdphxajrveps8qmnsdesvverqcenx5sz6gzkg489gsfq0qsy6nzryqcnqvpq95s9x3fqgd85u369f3qjq32wyppyjnzvg42y25jp9cs9xefqd35kyetjvys82mnpypmx273qv44x2cm4w3jjqtmjv4kx2ctnv5hzq5n9w3hhymnpypsjqmrpypmkzmrvv46zqumfypjkcgrrdakhqunpv3hhygrwdusxxmmwve5hymtpypjkcgrsv9nk7cqzf2xqrrsssp5yyg544cn5259puq6we96hduwc95uvuy3h0rr9an83hc4fx8edxdq9qyyssqwaf0r97t8uf06k49jg7ecx097hxurupwsdjfpfyxulqahuh8npvnv8pfham08rzkq4jzaahlwpn0hh07e7cavfzzla6pa4mzenpwlrgqtkdkfs
Thanks in advance!

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

No source file, test, or entry point is identified in the report. Start by reviewing the payment hash, channel details, screenshots, and CLTV state against the Lightning-channel handling; done means determining whether the HTLC and funds can be resolved without closing the channel.

Written by the indexing model from the issue text.

Assessment

Tech stack
python, ubuntu
Domain
blockchain, payments
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.