JoshR on Nostr: I’m implementing some zap request/receipt logic, and am finding the spec a little ...
Published at
2023-08-10 15:06:30Event JSON
{
"id": "ac8b5315a89302607a41972482315b61ae824b7e281a5e3fa34e1a7ceff38223",
"pubkey": "93e174736c4719f80627854aca8b67efd0b59558c8ece267a8eccbbd2e7c5535",
"created_at": 1691679990,
"kind": 1,
"tags": [
[
"imeta",
"url https://cdn.nostr.build/i/33c5175b79821e8d5f152c0aa01c2c064c8521469647fa13faf2045568b8cc86.png",
"blurhash e26H=h-;4nM{ITM{xuWBogxuIUaxoftRof-;xvM{t7WBD$%MayRixu",
"dim 984x276"
]
],
"content": "I’m implementing\tsome zap request/receipt logic, and am finding the spec a little ambiguous when it comes to the e tag and/or a tag.\n\nThe goal is to zap a replaceable event, with a custom kind of 32123. \n\nShould I include both the a tag and the e tag? Or, just the a tag event coordinate?\n\nFrom the spec (https://github.com/nostr-protocol/nips/blob/master/57.md#reference-and-examples):\nFrom the spec: https://cdn.nostr.build/i/33c5175b79821e8d5f152c0aa01c2c064c8521469647fa13faf2045568b8cc86.png ",
"sig": "3edf05f4e1cc3ee0128d22f2ba5fa3a1024d1142dd96cf2b362644815e1598acee4f72a9d37482ebf7d2d6ba74df8abf2572ea3923f70af00bd14142a6aaac7e"
}