Security

The integrity of a result is only as good as the systems around it. This is how we protect ours.

Results

SeedsDrawn from the operating system's cryptographic generator, kept in the game server's memory only until the round is over, and committed to by a published SHA-256 seal before the round opens.
Nothing earlyNo public answer, feed, page or player carries a result, seed or finishing order before the round has finished. Races and spins are streamed to viewers a fraction of a second at a time, never ahead of the clock. Our automated tests check for it.
Audit logEvery step of every round is written to an append-only, hash-chained log. The database refuses edits and deletions of it, and anyone can check the chain.
Self testsThe random number generator must pass its statistical self tests every time the server starts, and is checked continuously while it runs, or play halts.

Integrations

Signed requestsEvery server-to-server request, in both directions, is signed with HMAC-SHA256 over its timestamp, method, path and exact body, and refused if the signature is wrong or the time is more than five minutes off.
Separate keysEach partner has its own identity and secret, shown once, and its own access to games. A key can be disabled at once without affecting anyone else.
WebhooksEvents we send are signed the same way and go only to https addresses on the public internet.
EmbedsOur players can only be framed by the domains we have agreed with each partner, and pass nothing to the page around them that is not already on the screen.

Our sites

Reporting a vulnerability

If you believe you have found a security problem in any BetStream 3D site, game or API, please tell us through contact with the subject "Security", before telling anyone else. Include what you found and how to reproduce it. We will acknowledge your report, keep you informed while we fix it, and credit you if you wish.

Please do not access other people's data, disrupt our services or run automated scans against them while testing.