I’m involved in implementing a micro-transaction “paywall” that can enable nameless customers entry to an online software that I’m constructing. Every distinctive go to to the house web page of the applying would set off an api name that can generate an bill for that particular session and current the person with a QR code for them to make a cost that can grant entry for that individual session.
My query is, what number of invoices can realistically be monitored with SubscribeSingleInvoice
earlier than this is able to be an issue? Like if 100,000 folks concurrently visited the app, that may be 100,000 distinctive invoices generated and subscribed to… Which looks as if that could possibly be a nasty scene… Although I might be setting these invoices to run out some-what shortly, like 5-10 minutes, assuming in the event that they have not paid inside that timeframe, they’re almost definitely not going to be paying in any respect.
Are there any good tutorials to advocate for organising a paywall like this? I’ve been googling and googling and not likely discovering something helpful…… And the lightning documentation is a bit obscure and missing specifics.
Additionally, a aspect query is, to do that, is it actually essential to run a bitcoind backend? I used to be studying about neutrino, and noticed LND enables you to use that as a backend.. Since I’m solely involved in producing invoices and microt-ransactions and detecting once they have been paid, is it doable to make use of neutrino for this in order that my app can have much less of a heavy infrastructure footprint?