So you need a way to handle it when being offline? get it. That's what Nostr Wallet Connect is for?
Discussion
I think NWC is only for sending payments but I could be wrong about that. The problem youโre describing is that there needs to be a non-custodial way for receiving asynchronous payments like zaps, right? In order to do so, at some point in the process the Breez/Phoenix wallet node on your phone has to be reachable in order to serve the invoice to be paid, and there has to be some mechanism listening for a request to retrieve it from the receiving wallet and serve it to your wallet to pay it. Thatโs what LNURL does right now, and lightning addresses just utilize LNURL, but that all requires an always-on connection. So either the node on your phone would have to always be online, along with the corresponding LNURL server, or there would need to be some other mechanism to coordinate those payments asynchronously when to account for when your phone node goes offline.
Its a difficult problem to solve. ๐
Bolt12 offers would make it easier to be self sovereign because you only need to run a lightning node and then have a static adress which then queries the node for an invoice. No need to run a separate server.
Bolt12 helps a lot (removes the need to use web server), but it doesn't solve the offline receive problem. Async payments does (not a single bolt).
Async payments? Please tell me more. ๐คฉ
Sorry for being impatient i see now you guys are working hard on solving these issues. We are still early. Glad that you are here on Nostr.๐ค
No worries, i completely understand โค๏ธ
Here you go: https://lightningdevkit.org/blog/onion-messages-demystified/