Home/PackDraw provably fair
Fairness
PackDraw Provably Fair: How It Works and How to Verify
"Provably fair" gets printed on every gambling site. On PackDraw it means something specific: you can take the inputs to any pack opening and recompute the result yourself. This page explains the system in plain terms and walks through a verification.
Code verified and last updated:
Two systems, one goal
PackDraw uses two different mechanisms depending on what you are doing:
- Solo pack openings use a server seed, client seed and nonce. Classic provably fair, as used across the industry.
- Pack Battles use the hash of a future EOS blockchain block. No seeds at all; the randomness comes from a public chain.
Both are designed so the operator cannot pick the outcome and you can check it afterwards.
Solo openings: server seed, client seed, nonce
PackDraw commits to a server seed
It generates a secret random string and shows you its hash. The hash is a fingerprint: it proves the seed exists and is fixed, without revealing it.
You set a client seed
Any string you like. Change it in the provably fair settings before you open packs. This is your input to the randomness.
Each opening increments a nonce
A counter: 1 for your first opening with this seed pair, 2 for the next, and so on. It makes every result unique.
The three combine into a number
Server seed + client seed + nonce run through a hash function produce a number. That number is mapped onto the pack's drop table to select the item.
You verify afterwards
Rotate your server seed. PackDraw reveals the old one. Check its hash matches the one you were shown, then recompute any opening.
The key insight: because the server seed's hash was shown before you opened, PackDraw could not swap the seed to change results. And because you supplied the client seed, PackDraw did not control all the inputs.
Open packs with 5% extra balance (code WAGER)
Battles: EOS block hash
When a battle fills, PackDraw records the number of an EOS block that has not been produced yet. The battle waits until that block exists. Its hash, which nobody could have known in advance, seeds every pull in the battle. Anyone can look the block up on an EOS explorer and recompute the outcomes. This removes even the theoretical concern that a secret server seed could be mishandled.
Published odds and expected value
Fairness only tells you the dice are honest. The odds tell you whether the game is good. Every PackDraw pack lists each item with its exact drop percentage. Multiply each item's value by its percentage and add them up, and you have the pack's expected return. Compare it to the price.
| Example $20 pack | Value | Chance | Contribution |
|---|---|---|---|
| Headline sneaker | $600 | 0.5% | $3.00 |
| Mid-tier item | $80 | 5% | $4.00 |
| Common item A | $12 | 44.5% | $5.34 |
| Common item B | $9 | 50% | $4.50 |
| Expected return | $16.84 (84% of $20) | ||
Illustrative numbers, not a real pack. The pattern is typical: a fair system, honest odds, and an expected return below the price. That gap is the house edge, and no bonus changes it. The 5% from code WAGER just means you start with a little more balance.
Why "it's rigged" still gets said
A 0.5% item will not hit in 200 openings for about 37% of players. Those players feel cheated; the maths says they are exactly on schedule. Verifying your own openings is the antidote: it does not make the odds better, but it proves the result you got was the honest one.
Enter WAGER in the code field on the deposit screen. 18+ only. Terms apply.
Provably fair FAQ
Is PackDraw rigged?
Outcomes are generated from a committed server seed, your client seed and a nonce, and battles from a public EOS block hash. Both can be verified after the fact, so PackDraw cannot alter a result without it being detectable. What people experience as "rigged" is usually variance on packs where the headline item has a tiny drop rate.
What is a server seed and client seed?
The server seed is a secret random value PackDraw generates and commits to (by publishing its hash) before you open anything. The client seed is a value you control. Combined with a nonce that counts each opening, they produce the result. Because the hash was published first, PackDraw cannot change the server seed afterwards.
How do I verify a PackDraw pack opening?
Open the provably fair section on your account, rotate your server seed to reveal the previous one, then plug the revealed server seed, your client seed and the nonce into the verifier (PackDraw's or an independent one). The output should match the item you received.
Can I change my client seed?
Yes, at any time from the provably fair settings. Setting your own seed before a session is the whole point: it guarantees PackDraw did not choose both inputs.
Why do battles use EOS instead of seeds?
In a battle several players are involved, so a single client seed is not enough. Using the hash of a future public blockchain block means no participant, and not PackDraw, controls the random input.
Does the affiliate code affect fairness?
No. Code WAGER adds 5% balance on deposits. It has no connection to the random number generation or the published odds.