Been looking into following zap data around the Nostr network as a latent web of trust/value. Still excited about the idea, but it turns out to be less trivial than I thought.
Basically, you can't just ask relays for zaps from or to specific accounts, because of the way NIP 57 works. To answer questions like "what zaps has Logan sent in the past week", you have to first get "all the zaps" (or as close as you can get on Nostr) and then *locally* filter that data down based on senders, recipients, etc.
Time to write a zap caching server! 😓😅 Unless there is already something out there like this? Anyone know of a service which aggregates zap data?
OgLog
npub1zt…cwcyy
2024-06-21 15:25:36
Author Public Key
npub1zteqcekncmnt07d3zulsayd4m4ppm3nh6m3upm9sasljy89h2efqzcwcyyPublished at
2024-06-21 15:25:36Event JSON
{
"id": "50992b5a0c89e72c61ef97ee14ef9132b6f7905b9173b213af9b69a1fd623e73",
"pubkey": "12f20c66d3c6e6b7f9b1173f0e91b5dd421dc677d6e3c0ecb0ec3f221cb75652",
"created_at": 1718983536,
"kind": 1,
"tags": [],
"content": "Been looking into following zap data around the Nostr network as a latent web of trust/value. Still excited about the idea, but it turns out to be less trivial than I thought.\n\nBasically, you can't just ask relays for zaps from or to specific accounts, because of the way NIP 57 works. To answer questions like \"what zaps has Logan sent in the past week\", you have to first get \"all the zaps\" (or as close as you can get on Nostr) and then *locally* filter that data down based on senders, recipients, etc.\n\nTime to write a zap caching server! 😓😅 Unless there is already something out there like this? Anyone know of a service which aggregates zap data?",
"sig": "1cac30b8ae903ab93863416d32145f5eeab0bc0fd333ddc52a6b9d3a98de2748a4b2325baebc6bd696e13279324c18873ec3ddb94278021c1f7d6459887a0c24"
}