pull down to refresh
500 sats \ 1 reply \ @k00b 15 Jan \ parent \ on: Zaps Failing, Fragility, and Bet Update meta
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.
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.
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