pull down to refresh

Recently, I opened a 1M size channel to LNBIG-hub3 and transferred 450,000 sats to another wallet. Now my Zeus wallet channel has 450,000 sats in inbound liquidity, but it cannot receive even 2,000 sats. All my LN wallets indicate that they cannot find a route to my Zeus wallet. Even when using invoices with the routing hint option, it still fails to find a route.
However, sending sats from my Zeus wallet works without any issues. What else should I consider? This is an unannounced channel, and yes, this is my only channel in Zeus. Since Zeus is the only wallet I am having trouble with, I suspect I might be doing something wrong. I believe it is synced, and all Neutrino peers respond with good ping times.
Or was opening a private channel to lnbig was my mistake??
Is it fully-synced to the LN graph yet ? If you dont use persistent mode, you have to wait several minutes to give Zeus enough time to properly sync-up to both the Chain and the LN Graph
I also have a channel with LNbig and it works just fine for me, even got free fee
reply
Is it fully-synced to the LN graph yet ?
How do i check if it is fully synced??
reply
I am seeing under my Node info, both Synced to Chain and Graphs shows "True"
reply
Try making payment now then, also make sure the sender's wallet is also online until the payment goes through
reply
tried coinos -> zeus, still no luck(not reachable). both are online.
reply
That's strange, both nodes have beefy public channel with ACINQ and WoS.
The last reason i can think of rn is the Coinos low swap fee is being abused on specific path (but as you said even 2k payment can't go through so it still strange)
@adam_coinos_io, any insight on this ?
reply
IMHO coinos is heavily abused.
reply
0 sats \ 3 replies \ @nym 11 Jan
I wonder how long they can stay around
when sending sats from Phoenix to Zeus with a routing hint included, Zeus is able to receive the sats. I'm not sure why thanks anyway
reply
  1. Is that Zeus embedded?
  2. If yes, then when you create a LN invoice use route hints or wrapped invoice. That is creating a predetermined path with your private channels. Otherwise the sender cannot "see" your private channels. So you practically inform the sender about the last hop (your LSP / aka one of your private channels) to find a route to it. Then the LSP is fw the sats to your channel.
I suggest you to read carefully these 2 guides I wrote about Zeus (where I explained these "tricks"):
These 2 guides are the most complete step-by-step walkthrough for Zeus embedded. Any new Zeus user MUST read them. Zeus have many functionalities and for a new user that doesn't know in details how LN works, these functionalities sometimes could be very complex. So that's why I wrote those guides.
reply
Thanks, never worked even if I included routing hints, but now it works.
reply
Another trick: when you pay yourself, I mean using 2 wallets on the same device, put Zeus in persistent mode. That will keep LND service always active. If that function is not active, when you switch from Zeus to another app, to pay the invoice, it can go fast into offline mode and you will lose the sync.
I use Zeus with always active persistent mode if I know that in that day I will use it several times. It cost nothing, in terms of battery, but help a lot. Once I know I wil not use it anymore that day, I just force close the persietent mode (from app info - force close) and done. Soon we will have a small button in the persitent notification that you can shut down gracefully the service.
reply
I think it is temporary error network and should be solved soon.
reply