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

Inaccurate Network Graph Data Leading to Payment Failures in Zeus Wallet v0.9.0 #2402

Closed
Perlover opened this issue Sep 9, 2024 · 5 comments

Comments

@Perlover
Copy link

Perlover commented Sep 9, 2024

Issue Description:

There seems to be a bug in the Zeus wallet related to the network graph data. I've noticed that many of my recent payments have failed, and upon investigating, I discovered the following:

  • When viewing the network graph data in the wallet, it shows approximately 40,000 nodes and 132,000 channels.
  • However, in reality, the number of nodes and channels is about three times lower.

To further investigate, I switched to the EGS provider in the settings and selected Blixt as the source. After restarting the wallet, it then displayed more realistic values of around 18,000 nodes and 40,000 channels.

If I switch back to the Zeus source and restart the app, it again shows 40,000 nodes and 132,000 channels. This suggests that your server, which provides data for Express Graph Sync, contains an excessive amount of inaccurate or redundant data. This likely leads to the high failure rate in payments, as too many routes are not being found.

Steps to reproduce:

  1. Use Zeus wallet v0.9.0.
  2. Check the network graph data (should show ~40,000 nodes and ~132,000 channels).
  3. Switch to EGS provider and select Blixt as the source.
  4. Restart the wallet and check the network graph data (should show ~18,000 nodes and ~40,000 channels).
  5. Switch back to Zeus source and restart the app.
  6. The inaccurate, inflated data will reappear.

This issue might be the reason why many payments are not completing, as invalid or excessive routing data is being used.

@kaloudis
Copy link
Contributor

kaloudis commented Sep 9, 2024

Thanks for reporting. The speedloader server has been restarted. We'll look to automate the process moving forward.

@kaloudis kaloudis closed this as completed Sep 9, 2024
@Perlover
Copy link
Author

Perlover commented Sep 9, 2024

Now it works! Thanks!

@Perlover
Copy link
Author

Now there is the same problem....

37K nodes, 105K channels...

@kaloudis kaloudis reopened this Sep 14, 2024
@kaloudis
Copy link
Contributor

Making great progress on our new Graph Sync server. Hoping to pop it in as a replacement some time next week after testing.

In the meantime, we'll be keeping an eye on the current server an resetting it when appropriate.

@kaloudis
Copy link
Contributor

kaloudis commented Oct 1, 2024

New express graph sync serer is finally in place!

@kaloudis kaloudis closed this as completed Oct 6, 2024
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