How results are decided

3dSabong.com is a simulated sabong broadcast. Every fight decides its own result in the pit, and every random moment in it comes from a seed sealed before the fight and revealed after it, so anyone can check the result and run the fight again.

BroadcastON AIR
RNG self testPASS
Audit chain (server check)INTACT11,911 entries
Fights so far5,898

The life of a fight

  1. A secret seed is drawn. Before anything of a fight exists, the outcome RNG draws a secret 256-bit seed. Everything random in the fight comes from it: which two birds are matched, their build and temper, and every step, peck, kick and fall.
  2. The seed is sealed. The server immediately publishes SHA-256("fight|seed"), before the birds are even shown. The seed itself stays secret, so nobody can work out how the fight will go.
  3. The fight decides. Nothing is drawn in advance and nothing steers the birds. The result is whatever happens in the pit: a kill, a bird that runs or refuses to fight, or a draw when both die.
  4. The seed is revealed. When the fight ends the seed is published. Anyone can check it hashes to the sealed value, and run the same fight again from it: the same code and the same seed give exactly the same fight and the same result. Every fight page can do both in your browser.
The live stream runs a few seconds behind the server. Results, history and audit entries are only published once the stream has shown them, so nobody, including people reading the API, can learn a result early.

The outcome RNG

Source
Operating system CSPRNG via crypto.getRandomValues (Node.js v24.22.2)
Scaling
rejection sampling
Commitment
The fight decides the result. Everything random in a fight comes from a 256-bit seed drawn by this RNG; SHA-256("fight|seed") is published before the fight and the seed after it, so the fight can be run again to check the result (web/js/replay.js).
Start-up self test
Passed · monobit ✓ · poker ✓ · runs ✓ · long run ✓ · chi-square (6 cells, 5 df) ✓ (Nov 17, 2026, 6:57:39 AM)

At start-up the RNG passes the FIPS 140-2 monobit, poker, runs and long-run tests and a chi-square test, or play halts. Every block it produces is checked against the one before it. Each fight's seed comes from it; inside the fight a fast seeded generator (xoshiro128**, keyed with the whole seed) produces the fight's random numbers, so the fight can be run again exactly.

The RNG is built to the requirements of GLI-11 and GLI-19. Certification is done by an accredited test laboratory, not by software; this broadcast has not been certified.

The audit log

Every step of every fight is written to an append-only log. Each entry's hash covers its content and the hash of the entry before it, so changing, removing or reordering any past entry breaks every hash after it. The database itself refuses edits and deletions of the log.

Verify the whole chain in your browserRaw log (JSON)
Downloads every public audit entry and recomputes all the hashes here, without trusting the server's own check.

3DRoulette Live

The roulette table uses the same idea, and the same RNG. Every spin is on the roulette results record, back to the first.

3DKarera Live

Horse racing works the same way. Which twenty of the stable's hundred horses run in a race, and the state of the track, come from a schedule published ahead of time. As a race opens, a secret seed is drawn, and the SHA-256 of the race number, the seed and the ratings is published: the seal. At the off the finishing order is worked out from the seed on the game server, each runner's chance in proportion to its rating, and the race is run there to finish in that order. Nothing that leaves the server tells anyone the result before the race is over: the race is sent to viewers as it happens, a fraction of a second at a time, and the seed and the order are published only once every runner is past the post. Then anyone can check the seal and work the order out again. Every race is on the race results record, back to the first.

  1. A secret seed is drawn. As a spin opens, before any bet, the RNG draws a 256-bit seed. It is kept in the game server's memory only.
  2. The seed is sealed. The server publishes SHA-256("spin|seed") at once: on the table, in the results record and in its audit log. From then on the result cannot be changed without breaking the seal.
  3. Bets are taken, then closed. Nobody outside the server can work out the number from the seal.
  4. The seed is revealed. When the ball is at rest the seed is published and the number can be worked out from it (the game server works it out as the ball is released, and sends viewers the ball as it goes, never the number): SHA-256 of spin|seed|number, the first byte below 222, modulo 37. Bytes of 222 and over are passed by, so each of the 37 numbers is exactly equally likely. The ball you see is then thrown to land on that number; the picture decides nothing.

Each spin's page does both sums in your browser. The results page also counts how often every number has come up, so the spread can be compared with a fair wheel's. A spin interrupted before the ball is released is void and every bet on it is returned.

Check a result yourself

Open any fight from the results. Its page shows the sealed value and the revealed seed, checks one against the other, and can run the fight again in your browser. On any computer:

printf '%s' '1234|9f0c…(the 64-digit seed)' | sha256sum

The output must equal the value sealed before that fight. To run the fight again outside the site, use the open-source verifier: node scripts/verify-fight.mjs 1234 https://3dsabong.com. A replay is exact on the same simulation version (each fight records it) and on the V8 JavaScript engine the server uses (Node, Chrome, Edge); other browsers can compute some maths a hair differently. Fights before the change to fight-decided results were drawn from a weight table; their pages show that check instead.