just gonna throw this out there: maybe the skateboard version is something like opennode. And then from there you move to something less-managed like voltage (if you decide to go that far). In the early days I think you want to be laser-focused on building the right protocol and UX, and not be spending time on managing channels, etc
Discussion
💯 on the not managing channels aspect of things. What makes you suggest opennode for our use case?
I don’t know a lot about your requirements, but I’m willing to bet that it’s like 70% UX, 15% nostr protocol bits, 10% music bits, and like 5% lightning. and I bet the lightning bits are:
- I need to programatically request payment
- I need to programatically see if my requested payment got paid
opennode gives you an API to generate an invoice, handles all the routing and liqudity details, and an API to see if things have been paid
The downside is its all custodial and centralized. But to get something off the ground (or for a centralized merchant), who cares? make it all decentralized and non-custodial once you get the core bits all working together