I guess this is directed at @ek. I think he still hangs around the saloon. It's been a while for me. I stopped using SN wallet about two weeks ago. This morning I woke up to a bunch of sats in my SN wallet. It turns out that I somehow got logged out of Alby Hub last night, although I wasn't even using it. I use it to receive through a lightning address connected to my node. I wonder if SN automatically switches to the next priority wallet in case a payment fails? If not, would that be hard to implement?
74 sats \ 17 replies \ @ek 5 Sep
I think he still hangs around the saloon. It's been a while for me.
šŸ‘€šŸ¤”
This morning I woke up to a bunch of sats in my SN wallet. It turns out that I somehow got logged out of Alby Hub last night, although I wasn't even using it. I use it to receive through a lightning address connected to my node.
You mean you lost your lightning address connection to Alby Hub on SN? I don't understand the relation between a login and a lightning address. A lightning address shouldn't require a login. This would also match what I noticed today: my phoenixd connection must have disappeared a few days ago since there was no autowithdrawal since three days.
I wonder if SN automatically switches to the next priority wallet in case a payment fails? If not, would that be hard to implement?
We unfortunately currently only switch to the next receiving wallet if the invoice fails but not if the payment itself fails.
But thanks for reminding me, I just looked at the code and it might be easier to also switch to the next wallet if the payment fails than I initially thought.
reply
I started using Alby Hub with my own node. Until the Alby NWC situation is straightened out I use my Alby lightning address to receive. My node is always on. I even use a UPS. That reminds me. Did Alby straighten out the NWC receive issue with the last update?
reply
74 sats \ 15 replies \ @ek 5 Sep
Did Alby straighten out the NWC receive issue with the last update?
I don't know, I need to check
reply
10.3k sats \ 14 replies \ @siggy47 5 Sep
I just tried. I can't make a receive connection.
reply
53 sats \ 13 replies \ @ek 5 Sep
:(
/cc @Alby @bumi @saunter any ETA for the relay fix? Does it impact every event or only get_info? Asking because we're also working on replacing get_info for connection here with test payments that are always canceled (only used to check if we can receive a payment).
reply
Hey, could you remind what exactly is the problem? (can be on our team chat, to solve)
@siggy47 do you have your Hub launched and Alyb Account linked? Do other NWC connections work for you?
reply
Yes, I have my hub linked to my original Alby account. I am using the Alby NWC connect app on an Umbrel node for NWC send. It works well. When I generate a new secrets phrase and enter it in the app to receive, it times out without connecting. @ek can provide you with the technical details of why it's not connecting.
reply
43 sats \ 9 replies \ @ek 6 Sep
Here's a video of the issue:
We are not receiving a response for the get_info command which we need to check permissions. The bottom left shows all websocket messages. We send the request, we receive that the relay accepted (OK), we subscribe to the response (REQ) and it responds with EOSE which means it doesn't have the response yet (which is expected). But then silence.
It works fine with cashu.me:
I was also wondering about something else. Is there any chance you guys would consider a custom Stacker News wallet either as a standalone or part of the hub? I'm not sure what form it would take. It seems like it would be a perfect symbiotic relationship with Alby since SN is heading in the same direction with self custody and decentralization? I'm not sure what form it would take. SN users would jump on board pretty quickly, I'd imagine. The important thing would be ease of use to make the transition as smooth as possible for new stackers.
reply