Work/Web & Product/09

FairBreaks

Client FairBreaks

Role Product, brand, full-stack build, fairness standard

Year 2026

Stack Next.js 15, Supabase (Postgres, Realtime, RLS), drand quicknet, WebCrypto SHA-256, Stripe billing, OBS browser source, Vercel

Live fairbreaks.fun ↗

Provably fair card breaks: the buyer list locks before the randomness exists, and every buyer gets a receipt they can check from their phone.

The brief

Live card breaks run on trust. A seller spins a wheel or a list randomizer on stream and buyers see one result, with no way to know how many times it was spun, whether the list on screen matched the one that was sold, or which result was final. When a break is disputed, the only evidence is a replay. Breakers needed a way to prove the teams were assigned fairly, and buyers needed a way to check it without trusting anyone.

The public receipt: masked buyer handles, the drand round and one button to verify in the browser.

A buyer checks the break from their phone

The work

We wrote an open standard, FB-1, and built the product around it. A seller pastes buyers and locks the list, which publishes a SHA-256 fingerprint before any randomness exists. The break binds to a drand quicknet round that lands 30 seconds later, a public beacon run by the League of Entropy, and the shuffle is a fixed function of the two. Every buyer gets a public receipt with masked handles that re-runs the whole check in their browser. For the stream, a transparent 1920x1080 OBS overlay counts down, reveals each team on a name one at a time and ends on the verified mark. Around it sit a breaker lookup, Free and Pro plans billed through Stripe, an affiliate program with Wise payouts and a guide that explains the math in plain English.