pull down to refresh
176 sats \ 4 replies \ @SimpleStacker 15 Jan \ parent \ on: Zaps Failing, Fragility, and Bet Update meta
Ok, then I'm reasonably sure the error was related to NWC strings and not Lightning.
What I don't quite understand is that the wallet was working right up til last night. My computer restarted after I went to bed, and it wasn't working after restarting the wallet in the morning. It started working again after I downloaded the new Alby update, deleting my old NWC ones, and making new ones.
Restarting must have invalidate the NWC strings on Alby Hub's end.
The NWC connection isn't persistent or anything, so it wouldn't affect our end. On our end, if you give us an NWC string, whether good or bad, all we can do is sign messages with it and publish them to the relay specified then wait for responses.
Timeouts usually happen when responses don't come back, and responses don't come back when Alby considers the NWC string invalid afaik.
reply
So I guess I'm wondering if/where/when an Alby server sits between my computer and Stacker News?
Because I was running the same version of the Alby software on my computer as the night before, with the same NWC strings that failed in the morning. That shouldn't happen unless restarting somehow changed something on an Alby server somewhere, right?
Edit: Sorry, I know this is probably more a question for Alby. But I'm not really sure how NWC works, so this is all educational to me.
reply
Hmm I'm sure Alby has an explainer somewhere on how NWC works, but here's mine:
- Basically, Alby runs a nostr relay - a server with a public ip and a generic API for sending and receiving messages.
- When your Hub creates an NWC string, they generate a private key and associate it with the permissions to your lightning node that you specify.
- Your NWC string gives SN, or anyone you give the NWC string to, this private key.
- Hub listens for encrypted notes sent to Alby's relay where this public/private key is the recipient.
- If SN wants an invoice from you, it sends a message signed/encrypted with this private key to alby's relay, then listens for the result.
- Your hub, listening, sees the message, and checks if the bearer of that private key has permission to do the requested action.
- If it does, Hub performs the requested action, encrypts the result, then sends it to Alby's relay.
- SN, listening, now has the invoice it requested.
That shouldn't happen unless restarting somehow changed something on an Alby server somewhere, right?
Restarting more likely changed something on your computer, but it shouldn't have absent a bug or some reason only alby would know. I can't make sense of it.
reply
Interesting. Thanks for the explainer. Yes, I wonder if restarting affected my computer's communication with Alby's nostr relay somehow. That seems to be the most likely culprit.
reply