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.