Nostr Web Client

hahahhahhaha

I’ll shoot it out tomorrow. It’s very simple

Kind 7001 is p tag with who you support, cadence tag is “daily”, etc, amount tag is “amount”, “unit” (I hate to admit it but I think fiat unit of account will be useful for normies). Optional e tag of 👇

Kind 7002 is plans creators can publish with a content, just like patreon does. Same deal, amount and p tag.

Supporters zap tagging the kind 7001 and p tagging the creator.

There, that’s basically it. 😂

Kwinten 2y ago

My first idea was that the client should be responsible for checking periodically if payments are due and doing them. But now I think that it’s better if a server (zapplepay/zapplanner/recipient server is doing it). The zap events can be authored by a 3rd party while the subscription event is authored by the end-user once, at the start.

Reply to this note

Please Login to reply.

Discussion

Kwinten 2y ago

Should the NWC pay request be updated to add the event that you are zapping, instead of just the invoice? Then wallets can show users in a decent way what they were paying.