What is a provably fair randomizer?

A randomizer whose result anyone can check afterward. It locks in a secret seed and publishes the seed's fingerprint before the draw, then reveals the seed so anyone can rerun the draw and get exactly the same result.

In a random team break, the randomizer decides who gets which team. Most breakers use a wheel or a list shuffle on screen: viewers see the result, but have no way to confirm it wasn't set up in advance or run again until it came out a certain way. Publishing the fingerprint first fixes the outcome before anyone knows it, so a changed result would no longer match.

How it works

Before the draw, the randomizer picks a secret number called a seed. That seed decides the entire result. The seed isn't shown yet. Instead, its fingerprint is published: a short code made from the seed that can't be reversed to reveal it. Once the fingerprint is public, the seed can't be swapped without the fingerprint changing.

After the draw, the seed is revealed. Anyone can then check two things: that the seed matches the fingerprint published earlier, and that running the draw with that seed produces exactly the assignments seen on stream. If both check out, the result was locked before anyone knew who would get what.

What it proves, and what it doesn't

It proves the assignment wasn't changed after the fingerprint was published. It doesn't prove anything about the product. A randomizer can't tell you whether a box was resealed or whether a card left the frame. Those are separate problems, and they're why fair breaks need both a verifiable randomizer and a record of every pull.

Where BreakersDNA fits

On BreakersDNA random team breaks, the wheel's seed fingerprint is published when the break opens for spot sales, before any spin, and the seed is revealed when the break completes. Player breaks use a verifiable list draw: once the buyer list and the player list are locked, the draw commits to a secret seed and to a public random value from the drand beacon that nobody, including BreakersDNA, knows in advance.

Either way, anyone can recompute the result on the break's public verify page, with no account. Breaks that started before these features shipped used an ordinary server-side draw, which can't be recomputed afterward.