Do something close to NIP 42, but instead of an Auth message, the client can receive a PAY message with an lninvoice. Paying for it, proceeds with access. The idea is to present this to the user and get a one-click confirmation.
nostr:npub1gcxzte5zlkncx26j68ez60fzkvtkm9e0vrwdcvsjakxf9mu9qewqlfnj5z I think what we need is a nip generalizing service offering and billing. Whatās good for a relay is good for image hosting provider, bots, etc.
Those are my thoughts so far on the subject earlier
Do something close to NIP 42, but instead of an Auth message, the client can receive a PAY message with an lninvoice. Paying for it, proceeds with access. The idea is to present this to the user and get a one-click confirmation.
No replies yet.