How Case Battles Stay Fair

A solo game involves only you and us. A battle has several players in it, so it gets an extra source of randomness that none of the participants controls, us included: a public blockchain.

When a battle starts, we announce which upcoming block of the EOS blockchain will be used, a block that does not exist yet. Once that block is produced, its identifier becomes the battle’s public seed. The public seed is combined with the battle’s server seed, and that combination drives every pull in every round.

The server seed is committed and the block announced before the block exists, and once it appears its contents are public and beyond anyone’s influence. Neither we nor any player can steer what comes out.

Each player’s client seed is snapshotted when they take their seat. Bots use their username as their client seed, public from the moment they join. After the battle, everything needed to recompute every pull is available from the battle page. In Jackpot mode, the final draw combines every player’s client seed and weights the odds by unboxed value.

If the blockchain cannot be reached at the crucial moment, the battle is called off and every seat refunded in full, rather than falling back to randomness that we alone control.