100 sats \ 1 reply \ @cointastical 21 Aug 2022
I would think since that was the default Hosted Channel that SBW should first put out an update that checks if the wallet is configured for this particular HC and then warn the user. And the update should also warn the user if they try to add this HC.
As a first-hand example, I had wanted to use SBW for use with RoboSats but then learned that the HC would not work for the RoboSats security bond (Hold invoice). Only then did I learn that the node was basically on autopilot with the Ukranian operator @akumaigorodski out providing relief to his country.
But not all existing users are aware of the uncertain future of the HC.
reply
25 sats \ 0 replies \ @notgeld OP 22 Aug 2022
Yes. But an update would require dev work and it seems, this is not so easy nowadays for multiple reasons.
reply
105 sats \ 14 replies \ @DarthCoin 21 Aug 2022
Let's also keep updated a list of other HC node providers that can be used with SBW.
I am trying to build one, but I need more feedback from other users.
reply
110 sats \ 13 replies \ @notgeld OP 21 Aug 2022
SATM node by Standard sats.
reply
1 sat \ 0 replies \ @DarthCoin 21 Aug 2022
Thanks. Will try it out.
I tried with fiatjaf's Jiraiya but is always saying that node is disconnected.
reply
0 sats \ 11 replies \ @DarthCoin 22 Aug 2022
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
0 sats \ 10 replies \ @notgeld OP 22 Aug 2022
It may happen that fresh wallet needs to synchronize especially when it is legacy SBW
reply
0 sats \ 9 replies \ @DarthCoin 22 Aug 2022
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
10 sats \ 8 replies \ @notgeld OP 23 Aug 2022
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
0 sats \ 7 replies \ @DarthCoin 23 Aug 2022
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
10 sats \ 0 replies \ @notgeld OP 23 Aug 2022
Also thanks for suggestion, I will try to resolve Blixt liquidity soon.
reply on another page
10 sats \ 5 replies \ @notgeld OP 23 Aug 2022
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.
view replies
0 sats \ 1 reply \ @cryptocoin 4 Sep 2022
Related:
SBW Wallet Developer: Safe to say I'll never return to bitcoin/ln dev
#66327
https://Twitter.com/akumaigorodski/status/1566374265393389568
https://nitter.it/akumaigorodski/status/1566374265393389568 <-- Shows the thread in a single, easy-to-read, web page
reply
25 sats \ 0 replies \ @notgeld OP 5 Sep 2022
Yes. It was apparent since long time.
reply