Five on Nostr: I really like this approach! About zaps and verifiabilty: To my use-case in SatShoot, ...
I really like this approach!
About zaps and verifiabilty:
To my use-case in SatShoot, zaps are an important part of the Reputation of a client or freelancer, so the sybil attack would ruin this signal.
Therefore I use additional context to zaps that is the participants of the freelance deals themselves.
If the freelancer and the client both are part of my web of trust I will count the zaps on that deal.
Furthermore, a nutzap is inherently more verifiable because:
- I can look at mint recommendations and 10019 nutzap-receive preference events of my web of trust to assess a mint that the nutzap came from
- The sender of the zap receipt event is not a random LN node's pubkey but the actual person zapping
About zaps and verifiabilty:
To my use-case in SatShoot, zaps are an important part of the Reputation of a client or freelancer, so the sybil attack would ruin this signal.
Therefore I use additional context to zaps that is the participants of the freelance deals themselves.
If the freelancer and the client both are part of my web of trust I will count the zaps on that deal.
Furthermore, a nutzap is inherently more verifiable because:
- I can look at mint recommendations and 10019 nutzap-receive preference events of my web of trust to assess a mint that the nutzap came from
- The sender of the zap receipt event is not a random LN node's pubkey but the actual person zapping