pull down to refresh

I previously complained that I cannot pay Kagi via Zeus android wallet. I tried the same with Blixt and also couldn't pay Kagi. I noticed that these two wallets both use lnd. However i changer the pathfinding in zeus from bimodal to apriori and suddenly the payments work. So I am not sure what's going on here and why this happens.

50 sats \ 8 replies \ @DarthCoin 8h

Changing the path finding is useful ONLY in specific cases. And your case is not that one.
You still do not want to understand that your device is not updating correctly the LN graph.

With not a proper LN graph, no matter how you change the path finding, it doesn't work because the whole data is borked / wrong mapped.

Here is an explanation of path finding

https://docs.lightning.engineering/lightning-network-tools/lnd/pathfinding

reply

True my path finding has been borked for quite some time. The LN graph won’t update for my Zeus node. I believe Evan is working on a fix

reply

I think you do not understand how express graph sync works for Zeus and Blixt.

The path finding is done on YOUR device, not on Olympus or Blixt nodes.
Read more here: https://docs.zeusln.app/for-users/embedded-node/privacy#client-side-path-finding

Their nodes (Olympus and Blixt) have an always updated public LN graph, ofc because are 24/7 nodes.
From those nodes they push a compressed file to any Zeus user, at startup or on demand.
If you do not use too much your Zeus embedded node then your local LN graph is outdated, useless. So you need to download from Olympus or Blixt or any other LN node a latest LN graph.
Then your Zeus node can find the right path.
No matter if you have a channel open with the LSP. The LSP is just FW the payment with the instructions YOUR nopde is giving.

As I said many times: if you do not use Zeus ttoo often, at least just open it every 2-3 days and force to update the EGS at startup. Takes few seconds. no more. And all the trouble is gone.

reply

Then why all the zombie channels won’t go away with the updated ESG?

reply

zombie nodes and channels will always be there. Are all those nodes that went dead and now are marked as not usable. That's why you should not focus on the number of the zombies but on the number of online ones.
Here you can always check it out:
https://mempool.space/lightning

You will not have always the same number, but very close to it.

reply

So it is normal to see this?

reply
54 sats \ 1 reply \ @DarthCoin 3h

Yes that number is normal. The message I think is wrong. Instead of indicating the zombies number it should indicate that the online nodes number is wrong.

The zombie number do not affect your path finding, but the wrong number of online nodes yes.

That message is because your node is not syncing well with neutrino peers, so the EGS it also hang. So the app is alerting you that you should check your connection.

reply

I had the se situation before deleting the data and restoring the whole wallet. No amount of reseting the graph or chosing low ping peers fixed that. And yes, the nubmer of channels was incorrect.
After deleting and restoring the wallet yhe zombie channels get cleaned up and are usually below 100.
I am quite sure that this is some kind of a bug in the wallet.

My device seems to be updating properly now. I did delete the data and restored my wallet. I still couldn't pay Kagi. I changed the pathfinding and the payment passed immediately.
So yeah, theoretically bimodal pathfinding shouldn't result in failed payments, but in practice it did in my case. So it seems to be a bug. (Also keep in mind that failed pathfinding results in a message that there is no path, not in timeout with TemporaryChannelFailure in the logs. And while I have no idea how an error in pathfinding will give TemporaryChannelFailure, this has been my experience.)

reply