Abuse / identity limits on free ticket claims #29
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Follow-up from the free-ticket work.
Free tickets remove the Lightning-payment barrier that currently rate-limits ticket issuance implicitly. Without it, one user (or one script) can claim arbitrarily many seats and exhaust a free event's capacity.
Shape
user_idornostr_identifier(don't allow fully anonymous free issuance).api_ticket_createfor the free path (and ideally the paid path too, as a general cap).Scope: covers promo-derived-free, not just free events
The caps must apply to any ticket that takes the free path — i.e. a 100%-off promo on an otherwise-paid event (which #31 routes through the same no-invoice issuance), not only events with
price_per_ticket == 0. Otherwise a comp code becomes an uncapped free-mint on a paying event. Pairs with #32 (promo redemption limits) — that bounds redemptions per code, this bounds claims per identity; both are needed.Note also: comped/free tickets increment
soldand count towardmin_tickets, so they can push a conditional event over its threshold without real revenue and suppress the min-not-met refund to genuine payers — worth deciding whether free/comped seats should count towardmin_ticketsat all.Notes