Replying to Avatar Joshr

In the wavman app, we set it up to zap the kind 1 event (non-replaceable). So when a user sends a zap to a track, it is sent directly to the kind 1 event and not to a person. The kind 1 event id is set the e tag in the zap.

There is also a kind 32123 (replaceable) metadata event, which is used to house all the track's data. The kind 32123 event is not being zapped by wavman (though we have the endpoint setup to accept zaps to this, albeit this is untested).

I'm interpreting NIP-57 to mean that a zap request MUST use an e tag set to the event id of the kind 1 event being zapped (since its not a person). Should the a tag be included in addition to the e tag?
Avatar
PABLOF7z 2y ago

also, I tried to zap the kind 32123 but your server is responding with a generic 500 😕, even when I double URI encode

also, all references to nip-33 events should use the "a" reference, otherwise, if the event is replaced, the reference breaks as the ID points to an old version; NIP-57 mentions either tagging via `e` or `a` 😉

Reply to this note

Please Login to reply.

Discussion

No replies yet.