Zap Goals, Leaderboards and Public Money Games
When zaps become goals, rankings and games, money becomes a social signal. That can fund good work, but it also needs careful product language before status swallows context.
Visible support changes behavior
A private tip thanks someone. A public zap changes the room. When a post shows who supported it, how much moved and which comments carried money, attention starts to organize around value. That can be wonderful. It can also become theater.
Zap goals and leaderboards take that effect further. They turn small payments into a campaign, a scoreboard or a community game. A writer can fund a long essay. A developer can raise sats for maintenance. A streamer can unlock a segment. A venue can run a playful contest. A Crays award or voting game can turn fan attention into direct income.
The product challenge is to keep the signal useful. Money is a signal, not the only signal. A page that treats zap totals as absolute truth will mislead people. A page that explains what the total means, where it came from and what it buys can be genuinely useful.
What zap goals are trying to solve
Creators need ways to ask for support without turning every relationship into a subscription. Communities need a way to fund maintenance without heavy governance. Small projects need a public trail that says: this work has people behind it. Zaps are a natural fit because they are lightweight and already tied to Nostr identity.
A goal gives the payment a story. Twenty thousand sats for a new episode. Five hundred thousand sats for a conference livestream. A recurring monthly target for a relay. A bounty for documentation. The amount turns support into a shared object rather than a private receipt.
The trap is ambiguity. Is this a donation, a purchase, a vote, a pre-order, a membership fee or a game entry? Those are different legal and social promises. The page must say which one it is.
Leaderboards need context
Leaderboards are fun because they make invisible support visible. They are also dangerous because humans love rankings too much. A leaderboard can reward generosity. It can also reward flexing, coordinated promotion or status buying.
A serious leaderboard should show the measurement window, the counted event type, the currency unit, the included relays or wallet source, the update cadence and whether refunds, failed payments or suspicious activity are handled. Without that, a leaderboard is decoration with money attached.
For Crays, this matters because awards, community games and creator campaigns may use zap-like signals. If money influences visibility or status, the game rules have to be clearer than the visual excitement.
NIP-75 and the shape of goals
NIP-75 sits in this neighborhood because it gives zap goals a standardized shape. The details can evolve, but the need is stable: clients need a way to understand that a target, amount, beneficiary and context belong together. Otherwise every app invents a private campaign format and the signal becomes trapped again.
A standard goal can be discovered by different clients, displayed in different interfaces and linked back to the same identity. That is the Nostr pattern: the event is public and signed, while products compete on making it useful.
The practical point is not that every campaign must use one NIP forever. The point is that fundraising, goals and visible payment targets need shared grammar before they can become portable.
What can go wrong
Zap games can incentivize spam, shallow content and status chasing. They can also make people feel pressure to pay publicly when private support would be healthier. A creator can misstate what a goal funds. A client can double-count receipts. A relay can miss events. A wallet can produce payment records that the social client never sees.
None of this means zap goals are bad. It means public money needs plain labels. Donation. Tip. Vote. Purchase. Entry. Sponsorship. Bounty. Campaign. If the label is fuzzy, trust erodes fast.
Designing a good money game
A good money game shows the goal, the reason, the beneficiary, the time window, the wallet or receipt source, the rules, the refund stance and the social meaning of a zap. It does not pretend every sat carries the same moral weight. It does not hide the wallet path. It does not turn a payment into a promise the creator never made.
The best version feels light on the surface and exact underneath. People can play, support and cheer without reading a contract. If they do read the details, the details hold up.
How to read zap totals
Treat zap totals as energy, not audited revenue. They show that people engaged with money in public. They do not automatically prove profit, settlement, tax treatment, campaign fulfillment or long-term trust.
When a page uses zap totals to rank, reward or sell, open the details. If the details are clear, enjoy the game. If the details are missing, assume the signal is interesting but incomplete.
Sources worth opening
Open these when you want the specification, product documentation or implementation trail behind the article.
