Thanks. Will try it out. I tried with fiatjaf's Jiraiya but is always saying that node is disconnected.
reply
Are some liquidity issues with that node? I was onboarding a noob with sbw and blixt and tx from blixt to sbw (satm node for hc) worked fine but when I tried to send from blixt (blixt node channel) to sbw (satm hosted channel) says "no route found". Quite strange, when I tested the ln invoice it could find a path.
reply
It may happen that fresh wallet needs to synchronize especially when it is legacy SBW
reply
Not the case. That SBW was already using the Motherbase default node. I was testing SATM node as HC provider after removed the motherbase HC. Payment from SBW to Blixt worked. So if it wasn't synced (any of them) will not finish the payment anyways. Could be that Blixt node (with which is a channel in Blixt wallet) couldn't find a suitable route to SATM node- Is strange because both nodes are quite well connected. Could be also a not suitable fee case. I will try another day to see how it works.
reply
Ok. I disabled one node feature which allowed to reduce spam traffic but unfortunately cut off mobile clients from receiving gossip data from SATM. Try it some day again, please.
reply
Still doesn't find a route. I think Hampus (Blixt) have to open a channel towards SATM node. I already told him and will look into. I will try from another Blixt wallet with more channels open to make a test and will let you know. Will be good for SATM to have a ch with ZFR node too.
reply
Also thanks for suggestion, I will try to resolve Blixt liquidity soon.
reply
Keep wallet open for a while with channels online. May be SBW triggers syncing. We are maintaining our own fork of the wallet but it is not clear for us yet when exactly it starts resyncing graph data.
reply
Well, just checked with graph. It seems there are plenty of paths so may be wallet needs some fresh info about network state, indeed.
reply
It is resolved now by Blixt developer. New channel is on the way.