dikaios1517 on Nostr: I'll take a stab at it. You've got a couple different things going on here. First is ...
I'll take a stab at it.
You've got a couple different things going on here.
First is how outside services use to communicate with your Alby Hub in order to get a lightning invoice to pay you.
Second is how the lightning network gets the funds from the sender to you as the receiver via the payment channels in-between.
Your Alby account that hosts your Alby lightning address is connected to your Alby Hub using Nostr Wallet Connect. This means that when someone wants to make a payment to you through your Alby lightning address, Alby uses a Nostr relay to communicate with your Alby Hub to request a lightning invoice. No one can pay you at all unless your node can provide them an invoice to pay. Lightning addresses work by providing a means for others to request an invoice to pay you, without you having to manually create an invoice to send them.
If that relay Alby uses to communicate with your Alby Hub is down, no one trying to get an invoice using your Alby lightning address is going to be able to do so. Alby can't communicate with your node's Alby Hub instance without that relay being up and running.
If someone using Zeus' Olympus wallet is wanting to pay you, having a direct channel with Zeus with plenty of incoming liquidity will help ensure the payment can reach you with relatively low fees, because there will likely only be a single hop between you and the sender, but it won't help the person on Zeus to get an invoice from you that they can pay if they are trying to send it to your Alby lightning address and their relay is down. Alby won't be able to fetch an invoice from your node, no matter how direct your channel is with the person wanting to pay you.
I would like to see NWC include redundancy in relay selection, the same way Amber can use multiple different relays for NIP-46 signing. That way, you can run your own relay for NWC AND have Alby's relay as a backup, in case your relay is down. The likelihood that both would be down at the same time is slim.
You've got a couple different things going on here.
First is how outside services use to communicate with your Alby Hub in order to get a lightning invoice to pay you.
Second is how the lightning network gets the funds from the sender to you as the receiver via the payment channels in-between.
Your Alby account that hosts your Alby lightning address is connected to your Alby Hub using Nostr Wallet Connect. This means that when someone wants to make a payment to you through your Alby lightning address, Alby uses a Nostr relay to communicate with your Alby Hub to request a lightning invoice. No one can pay you at all unless your node can provide them an invoice to pay. Lightning addresses work by providing a means for others to request an invoice to pay you, without you having to manually create an invoice to send them.
If that relay Alby uses to communicate with your Alby Hub is down, no one trying to get an invoice using your Alby lightning address is going to be able to do so. Alby can't communicate with your node's Alby Hub instance without that relay being up and running.
If someone using Zeus' Olympus wallet is wanting to pay you, having a direct channel with Zeus with plenty of incoming liquidity will help ensure the payment can reach you with relatively low fees, because there will likely only be a single hop between you and the sender, but it won't help the person on Zeus to get an invoice from you that they can pay if they are trying to send it to your Alby lightning address and their relay is down. Alby won't be able to fetch an invoice from your node, no matter how direct your channel is with the person wanting to pay you.
I would like to see NWC include redundancy in relay selection, the same way Amber can use multiple different relays for NIP-46 signing. That way, you can run your own relay for NWC AND have Alby's relay as a backup, in case your relay is down. The likelihood that both would be down at the same time is slim.