Skip to content

Instantly share code, notes, and snippets.

@npendery
npendery / 2026-04-07-bot-protection-design.md
Created April 8, 2026 03:10
Bot Protection Design Spec for Face Value

Bot Protection for Face Value Ticket Marketplace

Problem

Face Value has no bot protection. Automated scripts can create accounts, snipe tickets faster than humans, and abuse the purchase flow. This erodes trust in a marketplace built on fair, face-value ticket exchange.

Goals

  1. Prevent automated ticket sniping (primary)
  2. Block bulk bot account creation
@npendery
npendery / 2026-04-07-ticket-marketplace-design.md
Last active April 7, 2026 22:37
FaceValue — Fair-Price Ticket Marketplace Design Spec

FaceValue — Fair-Price Ticket Marketplace

Overview

An Elixir/Phoenix alternative to Cash or Trade that enforces face-value pricing, uses escrow-based payments, and delivers a real-time experience through Phoenix PubSub. The platform serves all live events nationally — music, sports, comedy, etc.

Core Differentiators

  • Face value enforcement — sellers cannot list above what they paid (verified via OCR + manual review)
  • Simple 5% buyer fee — no hidden fees, seller gets exactly their listing price
  • Escrow protection — funds held until buyer confirms ticket receipt