Coinflip Fairness

Why EOS, and why after join

Coinflip cannot copy roulette’s daily tape. A flip does not exist as a two-sided bet until someone joins the creator. If the winner were known at table creation, the creator could simply never list a losing side. Official help therefore defers generation until a player or bot joins, then selects an EOS block that will be mined a few seconds later.

EOS produces a new block every few seconds. Help’s argument is that using a block that does not exist yet means nobody can know the public seed at join time without seeing the future. After the block is mined, its id is public and can be combined with the round’s private seed.

How to create or join a flip, the documented 0.5% house cut, and bot max bets are in the coinflip game guide. Fairness here is only the result pipeline.

Private seed, public seed, round id

Help lists three generation variables:

• Private seed — a securely random value generated when the round is created. Example in help is a 32-character hex string. A SHA-256 of this value is available so you can later confirm the reveal.
• Public seed — the id of an EOS block that is to be generated after a challenger joins. Example in help is a 64-character hex block id.
• Round id — a unique id for that coinflip, such as 62005623 in the help walkthrough.

Those values are what csgoempire.com/fairness exposes under Coinflip. This website does not mirror them.

Checking the private seed

Help’s verification outline starts with a warning step: SHA-256 of the revealed private seed must equal the published private-seed hash. If that check fails, the rest of the arithmetic is meaningless — the secret does not match the commitment made at round creation.

Only after that match does the recipe combine private_seed-public_seed-round with SHA-256. We describe that combination in prose because this site does not paste operator PHP in full and does not ship a verifier. Run whatever method the current Help Centre article shows, locally or on a runner you choose.

Heads (T) and tails (CT)

From the digest, help takes the first eight hex characters as an integer, reduces modulo 2, then adds 1. A result of 1 is documented as Heads (T); the other value is Tails (CT). That is a two-sided mapping, unlike roulette’s fifteen pockets.

A two-sided mapping is still compatible with a house cut. Official coinflip help and the max-bet article describe operator economics separately from the EOS recipe. Verifying that round 62005623 hashed to Tails does not refund the 0.5% if you lost, and it does not make the next flip +EV.

Bots and timing

Help says the result waits until another player or bot joins. A bot join is still a join: the future block is selected after that event, not when the table was posted. The fairness claim is about unknown public randomness at join, not about whether your opponent was human.

If a flip never fills, there is nothing to verify — help says no result is generated until join. Troubleshooting a stuck lobby is a product issue; see coinflip issues and official support, not a fairness script.

What a match does not mean

Reproducing heads or tails from the published inputs shows that this round matches the documented algorithm and seeds. It cannot show that you will profit, that match betting is provably fair (it is excluded), or that CSGOEmpire.help independently audited the EOS block. We do not query the chain for you.

Case battles also wait on a future EOS block after the lobby is full, but they hash additional fields (round, player position, ticket quantity, tiebreakers). Do not reuse the coinflip three-variable recipe on a battle. See case battle fairness.