I have been thinking about the complexity, user experience and privacy implications of NIP-57 zaps. Zapping involve having the nostr client doing calls to a users zap enabled lightning address service to make an invoice recording the event and npub of the payer.

Your payment will be linked to the event and your pubkey, not good for privacy.

If NIP-57 zap support become standard in most clients anon lnurl donation support like how it is today in nostr clients may suffer.

I am afraid Nip-57 Zaps will lead to a huge loss of payer privacy and centralisation around Nip-57 enabled clients, wallet and lightning address services that implement it.

Also i am not sure how anon tipping an zaps can interoperate when tipping posts. As i understand clients would have to support both methods, but how can that be done on the same zap button?

Its all very confusing. Especially since both Nip-57 and anon lnurl tipping are referred to as zaps by most users.

@jb55 et all please enlighten me if i am wrong here. Maybe we should pull the breaks on Nip-57 before we break user privacy and anon tipping on nostr?