Bitcoin Forum
March 11, 2026, 08:17:26 AM *
News: Latest Bitcoin Core release: 30.2 [Torrent]
 
   Home   Help Search Login Register More  
Pages: [1]
  Print  
Author Topic: Payment got stuck, what's the fastest safe way out?  (Read 58 times)
bitdude (OP)
Sr. Member
****
Offline Offline

Activity: 306
Merit: 256


View Profile WWW
March 09, 2026, 11:18:38 AM
Last edit: March 09, 2026, 11:53:40 AM by bitdude
Merited by ABCbits (2)
 #1

used lnpay command to pay for invoice and it did NOT go through (but did not fail either),

list_channels command has this in the affected channel:

        "local_unsettled_sent": 500001,

I tried to delete the invoice using delete_invoice, and it was deleted, but channel is still stuck with this amount.
Should I force close or wait for expiration?

Whale's Secret ScriptApiLib is a .NET library that provides unified API to different digital assets platforms with focus on easy of use and robust error handling.

Web: whalessecret.com/
Samples GitHub repo: [url=https://github.com/AITIS-s-r-o/
nc50lc
Legendary
*
Offline Offline

Activity: 3080
Merit: 8488


Self-proclaimed Genius


View Profile
March 09, 2026, 11:49:43 AM
Merited by ABCbits (2)
 #2

Should I force close or wait for expiration?
In case of the former, it's safer to use "Request Force-close" so it'll be initiated by the other end of the channel.
That's in case it didn't correctly update at your end, in which case, it could be be penalized if force-closed with an outdated channel state.

used lnpay command to pay for invoice and it did go through,
-snip-
Is this perhaps a typo, used "did" instead of "didn't"?

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits PREDICT..
█████████████████████████
█████████████████████████
███████████▀▀░░░░▀▀██████
██████████░░▄████▄░░████
█████████░░████████░░████
█████████░░████████░░████
█████████▄▀██████▀▄████
████████▀▀░░░▀▀▀▀░░▄█████
██████▀░░░░██▄▄▄▄████████
████▀░░░░▄███████████████
█████▄▄█████████████████
█████████████████████████
█████████████████████████
.
.WHERE EVERYTHING IS A MARKET..
█████
██
██







██
██
██████
Will Bitcoin hit $200,000
before January 1st 2027?

    No @1.15         Yes @6.00    
█████
██
██







██
██
██████

  CHECK MORE > 
bitdude (OP)
Sr. Member
****
Offline Offline

Activity: 306
Merit: 256


View Profile WWW
March 09, 2026, 11:53:22 AM
Last edit: March 09, 2026, 01:10:49 PM by hilariousandco
 #3

Is this perhaps a typo, used "did" instead of "didn't"?

Yes, sorry, it didn't go through, but didn't fail either. Will update OP.

In case of the former, it's safer to use "Request Force-close" so it'll be initiated by the other end of the channel.
That's in case it didn't correctly update at your end, in which case, it could be be penalized if force-closed with an outdated channel state.
Is this perhaps a typo, used "did" instead of "didn't"?

in close_channel command I see this

usage: electrum close_channel [-h] [--force] [--password PASSWORD] channel_point


so there is just --force and nothing else, so I have to go to GUI, right?

However, I believe I have correct update (though how can I be sure). I think it is just stuck HTLC.

How does remote force close vs my side force close compare in terms of funds releasing times?

Whale's Secret ScriptApiLib is a .NET library that provides unified API to different digital assets platforms with focus on easy of use and robust error handling.

Web: whalessecret.com/
Samples GitHub repo: [url=https://github.com/AITIS-s-r-o/
nc50lc
Legendary
*
Offline Offline

Activity: 3080
Merit: 8488


Self-proclaimed Genius


View Profile
March 09, 2026, 01:06:43 PM
Merited by ABCbits (2)
 #4

However, I believe I have correct update (though how can I be sure). I think it is just stuck HTLC.
Since there's a typo, you may be correct in this case.

How does remote force close vs my side force close compare in terms of funds releasing times?
It's been a while since I used the former
But AFAIK, if it's --forced regardless who's initiated it, you'll still have to wait for a timelock.

On the other hand, if it's a normal close, the funds should be available as soon as you close it.

in close_channel command I see this

usage: electrum close_channel [-h] [--force] [--password PASSWORD] channel_point
It's in a separate command: request_force_close

BTW, I'll ask a Mod to merge your consecutive posts since it's against a forum rule.

███████████████████████████
███████▄████████████▄██████
████████▄████████▄████████
███▀█████▀▄███▄▀█████▀███
█████▀█▀▄██▀▀▀██▄▀█▀█████
███████▄███████████▄███████
███████████████████████████
███████▀███████████▀███████
████▄██▄▀██▄▄▄██▀▄██▄████
████▄████▄▀███▀▄████▄████
██▄███▀▀█▀██████▀█▀███▄███
██▀█▀████████████████▀█▀███
███████████████████████████
.
.Duelbits PREDICT..
█████████████████████████
█████████████████████████
███████████▀▀░░░░▀▀██████
██████████░░▄████▄░░████
█████████░░████████░░████
█████████░░████████░░████
█████████▄▀██████▀▄████
████████▀▀░░░▀▀▀▀░░▄█████
██████▀░░░░██▄▄▄▄████████
████▀░░░░▄███████████████
█████▄▄█████████████████
█████████████████████████
█████████████████████████
.
.WHERE EVERYTHING IS A MARKET..
█████
██
██







██
██
██████
Will Bitcoin hit $200,000
before January 1st 2027?

    No @1.15         Yes @6.00    
█████
██
██







██
██
██████

  CHECK MORE > 
bitdude (OP)
Sr. Member
****
Offline Offline

Activity: 306
Merit: 256


View Profile WWW
March 09, 2026, 02:58:50 PM
 #5

Did not know about request_force_close being there.

Thank you for all the help!


Whale's Secret ScriptApiLib is a .NET library that provides unified API to different digital assets platforms with focus on easy of use and robust error handling.

Web: whalessecret.com/
Samples GitHub repo: [url=https://github.com/AITIS-s-r-o/
Pages: [1]
  Print  
 
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!