Oddbean new post about login | logout Zapit Development Summary | 80% Complete I've added a direct LN wallet proxy, eliminating the need for Lnbits. Additionally, I've implemented the LNURL LUD-10 protocol to package encrypted content, LN address, and a price into a single invoice, eliminating need for a centralized database. Thanks to Alby's excellent work, I've integrated NWC for recurring payments & subscription based service. If everything is implemented correctly, you won't even need my API. You can integrate Zapit features into your app using a simple library, no permissions required. This version of Zapit is a complete rebuild, designed from the ground up with best practices in mind. It's one of my most ambitious projects, and I'm not looking to gain anything from it. My goal is simply to create something I can be proud of. I understand that many Nostr users dislike paywalls. I respect that viewpoint, but I also believe that artists in the Bitcoin space deserve to have these option to monetize their work. I'll release an early version of Zapit soon and will continue to improve it based on user feedback. https://i.imgur.com/uEGzYUy.jpeg
I need some help. What is the best way to verify Lightning invoice payments without relying on a 3rd party Lightning service provider or full Lightning node? #NostrAsk #NostrDev Options I'm currently exploring https://github.com/lnurl/luds/blob/luds/21.md Context: nostr:nevent1qqst06reqv7rgrdhgqeeu5h7t7nye2kx7zsyrzj5rjr2z98eetxuzpgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygxx7urh795e65x0j25k22l7hlavqh7xss4eacu3pzwetxu26h2gl5psgqqqqqqsd7nf4a
Thank you for your work
Very cool. I’ve been trying to figure out a way to implement this into my photography publication @noicemag would love to talk with you more about it if you are open to it.
Once it's ready, I will help you with the integration 🫂
I dedicated nearly half of my weekend to this project, and it's undoubtedly one of the most ambitious ones I've taken on so far. Building regular lightning paywall services is relatively simple—I built one 1.5 years ago that's used by thousands today. However, building one without any middleman (no centralized server, no LNbits, no personal node, not even a central database) is an extremely difficult challenge. Here's what to expect: Seller side: Your content, price, and wallet address are all stored in a shareable QR code, secured by cryptographic encryption and signatures. Buyer side: When the QR code is scanned, it initiates the payment, and after it's completed, the content is decrypted and displayed. For Developers: Ideally, you shouldn't even need an API. You should be able to implement this functionality by simply importing a library with a one-liner, like: generatePaywallQR(contentURL, price, lnAddress) I'll be working on it this week, and hopefully by next weekend, I'll open it for some beta testing. After that, we can keep improving it based on feedback. nostr:nevent1qqst06reqv7rgrdhgqeeu5h7t7nye2kx7zsyrzj5rjr2z98eetxuzpgpr9mhxue69uhhyetvv9ujumt0d4hhxarj9ecxjmnt9upzp3hhqal3dxw4pnuj49jjhl4lltq9l35y9w0w8yggnk2ehzk46j8aqvzqqqqqqy0872r3
What's the maximum size for the content? I imagine there are only so many bytes you can encode+encrypt. and how will clients know how to display the content? MIME types?
It will support NWC. Currently, I'm exploring the user interface and considering how creators might utilize it. I would greatly appreciate any suggestions! #AskNostr nostr:nevent1qqst06reqv7rgrdhgqeeu5h7t7nye2kx7zsyrzj5rjr2z98eetxuzpgpz4mhxue69uhkummnw3ezummcw3ezuer9wchsygxx7urh795e65x0j25k22l7hlavqh7xss4eacu3pzwetxu26h2gl5psgqqqqqqsd7nf4a
