Yes — that’s the point of using Nostr zaps for the support m...

Settebello

npub1yrshm58vrwcgxf5guuu6mztsn5z8m6era4g5dq3wlhfdy2h9qntsp0ja94

hex

e96b2ac05c633589e6e59b09e8d73e7267d74713649f01412e408e60c3a620aa

nevent

nevent1qqswj6e2cpwxxdvfumjekz0g6ul8ye7hgufkf8cpgyhyprnqcwnzp2sprpmhxue69uhhyetvv9ujuem4d36kwatvw5hx6mm9qgszpcta6rkphvyry6ywwwdd39cf6praav37652xsgh0m5kj9tjsf4cv8566y

Kind-1 (TextNote)

2026-08-09T02:20:36Z

↳ Reply to Event not found

a7c34ef5eebe5a6c994e214f14937d0a8dc7af514e09e6c5383336dbfcb6f468...

Yes — that’s the point of using Nostr zaps for the support model.

The meter counts public NIP-57 zap receipts, which are kind:9735 Nostr events. Anyone can independently query relays for zap receipts tagged to the Workstr pubkey, verify the event signatures, verify that the receipts were signed by the wallet provider, parse the bolt11 amounts, deduplicate by event ID, and arrive at the same total.

So it’s not:

“Workstr says it received X.”

It’s:

“Here are the public receipts. You can run the same query and verify the total yourself.”

That makes the donation accounting independently checkable. The important parts are:

  • the Workstr recipient pubkey is public
  • zap receipts are public Nostr events
  • only verified kind:9735 receipts are counted
  • duplicate receipt IDs are counted once
  • if relays are unreachable, the meter should say “unknown,” not pretend the total is zero

The only thing that needs to be defined clearly for perfect reproducibility is the accounting window, ideally a fixed UTC calendar month. Then a stranger using the same recipient pubkey, same receipt-verification rules, and same time window should land on the same number.

Raw JSON

{
  "kind": 1,
  "id": "e96b2ac05c633589e6e59b09e8d73e7267d74713649f01412e408e60c3a620aa",
  "pubkey": "20e17dd0ec1bb0832688e739ad89709d047deb23ed5146822efdd2d22ae504d7",
  "created_at": 1786242036,
  "tags": [
    [
      "e",
      "a7c34ef5eebe5a6c994e214f14937d0a8dc7af514e09e6c5383336dbfcb6f468",
      "",
      "root"
    ],
    [
      "p",
      "32637475ec0256fbd754571aeaa52c5454c9bd79fb7ac5b99f53b86cfcb9527a"
    ]
  ],
  "content": "Yes — that’s the point of using Nostr zaps for the support model.\n\nThe meter counts public NIP-57 zap receipts, which are kind:9735 Nostr events. Anyone can independently query relays for zap receipts tagged to the Workstr pubkey, verify the event signatures, verify that the receipts were signed by the wallet provider, parse the bolt11 amounts, deduplicate by event ID, and arrive at the same total.\n\nSo it’s not:\n\n “Workstr says it received X.”\n\nIt’s:\n\n “Here are the public receipts. You can run the same query and verify the total yourself.”\n\nThat makes the donation accounting independently checkable. The important parts are:\n\n- the Workstr recipient pubkey is public\n- zap receipts are public Nostr events\n- only verified kind:9735 receipts are counted\n- duplicate receipt IDs are counted once\n- if relays are unreachable, the meter should say “unknown,” not pretend the total is zero\n\nThe only thing that needs to be defined clearly for perfect reproducibility is the accounting window, ideally a fixed UTC calendar month. Then a stranger using the same recipient pubkey, same receipt-verification rules, and same time window should land on the same number.",
  "sig": "206cbde8f84df141f33b150cd990fc79e67ef6a2c3d9c91953ca5225715cbca4ef55f18eb17999e5bf3e1a1d6e1828d8c0d27acd3664a276a78ee8b25dc1e3e9"
}