A lot of high quality components are needed to really solve this:
- A receiver side service that can create subscriptions and request invoices
- An always-on wallet that can pre-authorize recipients and pay invoices
Discussion
Yeah, I built my own NWC server for my own service. I could see implementing this easily; the hard part is digging in to make sure the requirements are right. I’ll keep this on my list of todos. I see having a ‘root’ secret that could add and delete subscriptions. Each subscription would have their own root and some sort of authorized declining balance.