Computed, not guessed
Theoretical RTP is derived in closed form and cross-checked by simulation. If the two disagree beyond sampling error, the build does not ship.
Most casino games ask you to take the maths on faith. We think the model should travel with the game — to the operator, to the test house, and to the player.
Slot maths is usually assembled by feel: pick a paytable, simulate, nudge, repeat until the RTP lands near the target. It works, but nobody can say precisely why the numbers are what they are — and when a strip changes, the whole thing has to be re-guessed.
We build the other way round. The RTP target and the split of that return across symbols are the inputs; the paytable is solved from them. Change a reel strip and the solver re-derives the pays in seconds, then an exact calculator and a simulation over tens of millions of rounds confirm the result independently.
Every game is server-authoritative. The browser sends a bet and receives a finished round; it holds no RNG, no paytable evaluation and no wallet arithmetic, because anything the client computes is something a player can tamper with.
Money is handled in whole minor units end to end. Floating point has no place in a wallet, and a rounding drift that shows up once in ten thousand rounds is a dispute waiting to happen.
Theoretical RTP is derived in closed form and cross-checked by simulation. If the two disagree beyond sampling error, the build does not ship.
The tools we use to check our own games are the tools we hand over. An operator should never have to take our word for a number.
We say plainly what is certified, what is in progress and what is still a prototype. Badges we have not earned do not go on this website.
Placeholder content. Replace the company details, dates and figures on this page with Dowin's real information before publishing.