-
Notifications
You must be signed in to change notification settings - Fork 31
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
Lightning address payments not being received after a restart #1163
Comments
I see some of them being claimed:
I'm guessing that some of them are not showing up in the UI? Another thing, it looks like the wallet was restarted as some of them are being claimed. Can you confirm that your balance is not correct? Also do you use this wallet on multiple devices? |
"I guess some of them are not displayed in the user interface." "Another thing, it looks like the wallet has been restarted as some of them have been claimed." "Can you confirm that your balance is incorrect?" "Also, do you use this wallet on multiple devices?" |
Yes, it's possible. Perhaps double check your balance, try again, and see if there's any issue. Another thing you can try is to restore your wallet again. The wallet keeps track of the last payment you received through nostr DMs and if there was an issue there, it might have missed some older ones. But first just try again and leave it opened for a few seconds. |
OK, problem solved. Thank you very much |
We'll try to fix this easier than having a restore happen. I'll transfer this issue over to our node repo and track it until it's fixed. Thanks for trying that and reporting it. |
A strange thing happened today on my Mutiny address 3 payments that I sent correctly from another wallet of mine did not arrive.
![Screenshot_20240430-175333](https://private-user-images.githubusercontent.com/21236725/326893486-b313449a-78e9-46f7-affa-5e25939e1cc0.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MjQ1MDU2MDksIm5iZiI6MTcyNDUwNTMwOSwicGF0aCI6Ii8yMTIzNjcyNS8zMjY4OTM0ODYtYjMxMzQ0OWEtNzhlOS00NmY3LWFmZmEtNWUyNTkzOWUxY2MwLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDA4MjQlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQwODI0VDEzMTUwOVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE5Y2M5Yjk3ZjgwOTVjMTg0ZTZiYTk4Mzc4MGZkOTZkMzliYTk3N2Y5ZjY1MjdiZDQ2NzViMmI1MzAxMjFjNTImWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0JmFjdG9yX2lkPTAma2V5X2lkPTAmcmVwb19pZD0wIn0.Rd-laXSo0MNXaGD6vy590cqrf4mRV3HeTqFmvnmFy6Q)
What can I check?
mutiny-logs.txt
The text was updated successfully, but these errors were encountered: