News

Can online backgammon be rigged?

Yes, it can be. A closed server can rig dice and results alone cannot prove it. What rigging looks like, and how commit-reveal dice make it detectable.

fairnessprovably fairdice

Yes, it can be. Online dice are rolled on a server you cannot see, and nothing physically stops an operator from changing a number before it reaches your board. Results alone will never prove it either way, so the honest question is not whether rigging is possible, it is whether a game can prove it did not happen.

We make a backgammon game, so we are not neutral here. That is exactly why we want to answer this properly, including the uncomfortable parts.

Why do the dice feel rigged on every site?

Because backgammon variance is brutal and human memory is biased. There are thirty-six ways two dice can land, streaks are not a glitch, they are a guarantee, and somewhere tonight an honest server will roll four doubles in a row against someone who played every checker correctly. You remember the 5-5 that hit your blot. You do not remember the miracle shot that saved you last Tuesday. Losses stick, escapes evaporate, and after three bad games in a row the dice feel personal. They feel personal over a real board in a real cafe too. Ask anyone who has pushed wooden checkers for forty years.

Here is the trap. A rigged game would feel exactly the same. Streaks prove nothing in either direction, so if your evidence is how the dice felt, you cannot tell an honest server from a dishonest one. Neither can we. That is not a defense of online dice. That is the problem with them.

Could a site actually rig its dice?

Technically, yes, and it would not even be hard. The server sees the whole board before it rolls. An operator who wanted to cheat could:

  • Tip a few rolls per hundred at the moments they matter most: the shot that hits, the entry that fails, the double that swings a lost game.
  • Keep matches artificially close, so sessions run longer and losses feel like near misses.
  • Quietly favor one side of a game the operator has an interest in.
  • Do it rarely enough that the dice still pass every statistical test a player could ever run.

We are not claiming any particular site does this. We are saying the architecture allows it. A closed server is a locked room: the operator rolls in private, reports a number, and asks you to take it on trust. From outside the door, honest and dishonest operators look identical.

Doesn't a certified RNG prove the dice are fair?

Read what the certificate actually covers. A lab tests a generator: an algorithm on a bench, producing millions of numbers that pass statistical checks. That certifies the component. It says nothing about delivery, meaning whether the number that reached your board came from that generator, at that moment, unmodified by anything in between. A certified scale in the back room does not prove your bread was weighed on it.

Certification is also a snapshot. Live servers redeploy all the time, and the code path between the generator and your game keeps changing long after the lab has gone home. So certified RNG answers a question nobody was really asking. The question that matters is not whether good dice exist somewhere on the premises. It is whether your game got them, every roll, tonight.

What does commit-reveal actually change?

It moves fairness from a promise to a proof. Before a game starts, the server draws a secret seed and publishes its fingerprint, a SHA-256 hash called the commitment. Every roll in the game is then derived from that seed, one HMAC-SHA256 computation per roll, in order. When the game ends, the server reveals the seed.

Now anyone can check two things. Hash the revealed seed: it must match the commitment published before the first move. Recompute the rolls: they must match every number that appeared on the board. If the server had altered even one die after seeing your position, the math would not line up. Rigging stops being a suspicion you cannot test and becomes a lie you can catch.

Dice that were locked before the game cannot react to it.

That is the heart of it. The useful kind of rigging is reactive: see the blot, roll the hitter. Commit-reveal takes the server's eyes away, because the entire sequence was fixed before the opening move and any tampering after the commitment is mathematically detectable. What it does not do is make the dice kind. The sequence was honest, not merciful. You will still sit on the bar at the worst possible moment, and now you will be able to prove it was fair.

How do you verify a game in practice?

This is how we built it in Orion. Every game played on our servers carries a commitment made before the first roll, the server validates every live move at source, and checking a finished game takes about a minute:

Open the verifier. Go to orion.arthea.ai/verify in any browser. Nothing to install, no account to create.

Enter the game ID. Every server game in Orion has one. Paste it in.

Let your browser do the math. The page recomputes the commitment and every roll using Web Crypto, locally, in your browser. Our word is not part of the check. If a single number had been changed, the recomputation would say so.

The verifier is live today. The game itself is finished, and the door at orion.arthea.ai/go carries the App Store and Google Play links and always shows what is available right now. Either way, the honest answer stands. Yes, online backgammon can be rigged. The fix is not a nicer promise. It is dice that show their work.