Fairness — how results are decided and proven

Results are decided with cryptographic randomness the moment you start, and with proof mode anyone can recompute them from public randomness.

How Playmoyeo decides results, and how anyone can check them.

The result is decided the moment you start

When you press start, the full order is decided first with the browser’s cryptographic random numbers (crypto.getRandomValues). Animations like stone skipping, the wheel or the marble race only reveal that result, so throw strength, timing and the device you watch on never change it. No server or operator is involved.

Equal odds, and weights only as written

The order uses a Fisher-Yates shuffle so every order is equally likely, and rejection sampling removes the tiny bias of fitting random numbers into a range. If you write a weight like "Alex*3", only that entry’s odds grow by that factor, and the result screen says the draw was weighted.

Proof mode

With "Keep a proof of the result" on, the list, pick count and weights are locked into a fingerprint (SHA-256) when you start, and a drand round a few seconds in the future is chosen. drand is randomness published every 3 seconds by universities and companies (the League of Entropy), so nobody — not the host, not Playmoyeo — can know it beforehand. The result is computed only from the fingerprint and that randomness, and anyone can recompute it from the certificate link.

What the proof guarantees, and its limits

The certificate guarantees that this list and this randomness produce this result, and that the randomness was signed and published by drand. The lock time, however, is a record in the link, so the link alone cannot show whether the host locked in advance. It is fully proven when viewers in a live room saw the lock screen before the result, or the round number was shared before the start.

How proof mode computes (check it yourself)

  1. Input: the list (names in on-screen order, blank slots as their numbers), pick count ("order" for a full order), weights (null if all 1), and the drand quicknet round.
  2. Fingerprint = SHA-256 of the JSON {"v":1,"items":[…],"pick":…,"weights":…,"round":…} with keys in that order.
  3. drand randomness = that round’s randomness (= SHA-256 of the signature). The signature is checked against the quicknet public key using bls-unchained-g1-rfc9380.
  4. Seed = SHA-256( "playmoyeo-proof-v1" ‖ 32-byte fingerprint ‖ 32-byte randomness ).
  5. Random stream: block i = SHA-256( seed ‖ i as 4-byte big-endian ), read 4 bytes at a time as big-endian integers. An integer in [0, n) discards values ≥ floor(2^32/n)·n and takes the remainder mod n.
  6. Order: without weights, for i from n−1 down to 1 swap with j = rand(i+1) (Fisher-Yates). With weights, repeatedly pick one of the remaining entries with rand(sum of remaining weights).
  7. Winners: the first pick-count entries of the order (the whole order for a full order).

Frequently asked questions

Can the operator change results?
No. Results are decided in your browser and never pass through a server. In proof mode they come only from public randomness published after the lock, and anyone can recompute them from the certificate.
Can I predict or change the result from the animation?
No. The result is decided before the animation starts. Throw strength, button timing and skipping do not change it.
Why does proof mode wait a few seconds?
Using randomness published after the list is locked means nobody can know the result in advance. drand publishes new randomness every 3 seconds, so the round 3–6 seconds after the lock is used.
What if drand can't be reached?
You are asked whether to continue with a regular draw. Regular draws are still decided fairly with cryptographic randomness, but no certificate is created.
Does the certificate link contain the result?
No. It only contains the locked list, pick count and round number. The browser that opens it fetches the randomness from drand and computes the result itself, so editing the link cannot show a different result.