Replying to Avatar Fascinating

I'm testing a new scheme from nostr:nprofile1qyghwumn8ghj7vf5xqhxvdm69e5k7tcpz4mhxue69uhkzet8d9ejuat50phjummwv5hsqgpm7rrrljungc6q0tuh5hj7ue863q73qlheu4vywtzwhx42a7j9n5zgwjy3 . If you've received more than 1000 sats in the last three months, you'll be able to access this exclusive post. I think it only works on Coracle or Jumble. Anyway, I'm really liking the idea. "onlyzappers"

https://jumble.social/?r=zapbox.fiatjaf.com

https://coracle.social/relays/wss%3A%2F%2Fzapbox.fiatjaf.com%2F

there could be a protocol where the content provider would set the rules, like minimum value and the renewal period, in a special event, and the relay would allow access if the zaps matched the rule.

something like

{...

tags: [

["minzap", 21000],

["renewaltime", "30", "days"],

["kinds", "1", "20", "22"],

...

]

...}

then the relay would apply the rules from this event to check if the reader could read events from this author.

Reply to this note

Please Login to reply.

Discussion

Yes, I've seen similar ideas suggested before, but I think this is broken in many levels, for example: it's ugly, lacks flexibility, commoditizes relays and centralizes implementations, it's annoying for everybody involved, people can't change their minds after publishing.

if the event is replaceable, they can change their mind. just replace with new rules.

it is still centralized in the sense you need to trust the relay to enforce this properly. I'm looking for ideas on how to implement this in a relay independent manner, completely decentralized. but couldn't figure out how yet.

Stop trying to be independent of relays.

i'm not, i just don't want to trust them to do anything beyond being the backbone of the network. i'm not trusting them to make privacy decisions in my place if i can enforce those decisions with cryptography or a well designed protocol.