Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Bug]: Manually Setup LN connection to LND3 didn't return funds #2268

Closed
catch-21 opened this issue Oct 1, 2024 · 2 comments
Closed

[Bug]: Manually Setup LN connection to LND3 didn't return funds #2268

catch-21 opened this issue Oct 1, 2024 · 2 comments
Assignees
Labels
bug Something isn't working triage This issue needs to be looked over by the team

Comments

@catch-21
Copy link
Contributor

catch-21 commented Oct 1, 2024

Describe the bug

After closing a LN connection with LND3 that was setup using the Manual Setup flow, Bitkit told me that "Your funds have been transferred. You are able to use these funds immediately." yet there is no trace of an activity showing the funds have been returned. The closed connection has a Closure reason "ProcessingError".

Using sparrow, I can confirm there is no onchain transaction sent to this wallet, so perhaps I need to wait longer.

bitkit_ldk_logs_1727763581718.zip

Reproduce

  1. Go to Advanced settings -> Lightning Connections -> Add Connection
  2. Establish a new connection to a known usable LN node, such as LND3 03816141f1dce7782ec32b66a300783b1d436b19777e7c686ed00115bd4b88ff4b@34.65.191.64:9735
  3. Once the transaction is confirmed and transfer is complete, close the channel using the normal Transfer to Spending flow.
  4. Once the flow gets to the "FUNDS MOVED TO SAVINGS" "Your funds have been transferred. You are able to use these funds immediately." page, tap Continue button.
  5. Observe that no Transfer from Spending activity appears.
  6. Observe in Lightning Connections that the closed connection has Closure reason "ProcessingError"

Screenshots / Recording

Screenshot 2024-10-01 at 13 19 19

Operating system

Android 14

Bitkit version

1.0.5 (136)

Log output

No response

@catch-21 catch-21 added bug Something isn't working triage This issue needs to be looked over by the team labels Oct 1, 2024
@Jasonvdb Jasonvdb self-assigned this Oct 2, 2024
@Jasonvdb
Copy link
Collaborator

Jasonvdb commented Oct 3, 2024

The force close is unfortunate, not sure how we're ever going to get nodes we don't control to agree on fees.

2024-10-01 06:05:00 UTC ERROR (LDK): Closing channel 59e11f494092ecde6545be97bf9fa2d4ce5f0f26b6efcb7c236659eec8fa15dd due to close-required error: Unable to come to consensus about closing feerate, remote wants something (308 sat) lower than our min fee (361 sat) (lightning::ln::channelmanager 7236)
2024-10-01 06:05:00 UTC ERROR (LDK): Force-closing channel: Unable to come to consensus about closing feerate, remote wants something (308 sat) lower than our min fee (361 sat) (lightning::ln::channelmanager 9483)
2024-10-01 06:05:00 UTC DEBUG (LDK): Finishing closure of channel due to Channel closed because of an exception: Unable to come to consensus about closing feerate, remote wants something (308 sat) lower than our min fee (361 sat) with 0 HTLCs to fail (lightning::ln::channelmanager 3245)
2024-10-01 06:05:00 UTC INFO (LDK): Applying force close update to monitor 59e11f494092ecde6545be97bf9fa2d4ce5f0f26b6efcb7c236659eec8fa15dd with 1 change(s). (lightning::chain::channelmonitor 2891)

Logs show these are your funds that should be good to be swept if you open the wallet again. Confirmation height was 30 hours ago.

{"confirmation_height":863746,"type":"ClaimableAwaitingConfirmations","amount_satoshis":99457}

@catch-21 can you check this wallet again?

@catch-21
Copy link
Contributor Author

catch-21 commented Oct 4, 2024

I can confirm the funds have been returned onchain. We have #2270 and #2273 to improve communication to the user when force close occurs. So I will close this ticket now. Thanks @Jasonvdb.

@catch-21 catch-21 closed this as completed Oct 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working triage This issue needs to be looked over by the team
Projects
None yet
Development

No branches or pull requests

2 participants