Oddbean

Trust me, no one knows this better than I do. I built one a year and a half ago, and the biggest problem we always faced was its reliance on an Lnbits server or personal node. This solution completely eliminates that dependency, it doesn’t even require a database. The content is encrypted and packaged within a QR code, and it is decrypted only when the payment is completed. It connects directly with the user's wallet, no login, no middleman 🤌

The idea is simple: it encrypts the content URL, packages it with a price, LN address, and a digital signature, and turns it into a shareable QR code or URL. When the QR code is scanned, it first verifies the integrity of the packaged data, deconstructs it, and uses an LN proxy to initiate the payment. Once the payment is settled, it decrypts the content. This approach does not require any database, BTC Pay server, or LNbits. Instead, it uses lightweight server functions, and with the upcoming LNURL standards LUD-10 and LUD-21, even this lightweight backend will be eliminated.