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

Order expired, LN still confirming #207

Closed
firedev opened this issue Aug 8, 2022 · 2 comments
Closed

Order expired, LN still confirming #207

firedev opened this issue Aug 8, 2022 · 2 comments

Comments

@firedev
Copy link

firedev commented Aug 8, 2022

Describe the bug
I opened an order 10938 on Aug 4th. It expired without a taker, but the LN invoice is still "Confirming" 4 days later.

Expected behavior
I expect the LN invoice to be canceled.

@Reckless-Satoshi
Copy link
Collaborator

Reckless-Satoshi commented Aug 8, 2022

Hey @firedev

We usually do not mix the open project development with the current operation. For some sort of support the telegram @RoboSats is best :D

In any case, I can confirm this invoice was "CANCELLED" by the backend (2022-08-04 22:30:28). In addition, the expiry height of that payment was block 748,511 (already past). So even if RoboSats had failed to cancel that payment, your wallet should have already accounted its return.

You are probably relying on a third party service (wallet) that is failing to notice the state of the HTLC changed. Please report to your wallet provider. Some wallets manage cancellations very poorly, this is quite common in Bluewallet and one of the reasons it is not recommended (though it eventually recognizes the payment had failed). Take a look at the wallet compatibility guide in https://learn.robosats.com/docs/wallets

Closing this issue as it is not related to a bug or the development.

@firedev
Copy link
Author

firedev commented Aug 8, 2022

Thanks. I am using Muun, will bother them then.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants