---

Our unwavering commitment is to offer our users an enjoyable and equitable gaming experience, and FortBux plays a significant role in achieving this goal. We‘ve implemented cutting-edge Provably Fair algorithms designed to demonstrate the fairness of our games.

While the specifics of the Provably Fair algorithm vary for each game, the fundamental objective remains consistent — to assure you that the outcome of the round remains untampered, irrespective of your participation. In simpler terms, we ensure that no games are manipulated in favor or against any players. Detailed explanations of each game‘s algorithm are provided below.

---

Blackjack

1. In Blackjack, every card draw is generated using a provably fair combination of the revealed server seed, client seed, hand nonce, and card index.
2. For each card draw, our system deterministically generates an HMAC-SHA256 hash using the server seed together with the client seed, nonce, and draw position.
3. The first portion of the resulting hash is converted into an integer and mapped to one of the 52 cards in a standard deck.
4. Since each card draw is generated independently from its own unique seed combination, every draw has the same probability distribution and does not rely on a pre-shuffled shoe.
5. Once the server seed has been revealed, players can independently reproduce every card dealt during the round and verify that the outcome was generated fairly.

The verifier below allows players to replay a blackjack round using the same card generation algorithm used by our backend servers, including player actions such as hit, stand, double, and split.

---

Cases Battles

1. In Cases Battles, every roll is generated using a provably fair combination of the revealed server seed, client seed, and roll nonce.
2. For each roll, our system computes an HMAC-SHA256 hash using the server seed as the secret key and the value clientSeed:nonce as the message.
3. The first 15 hexadecimal characters of the resulting hash are converted into an integer and transformed into a roll result between 1 and 100,000.
4. The roll result is then matched against the selected case‘s item ranges (rangeFrom to rangeTo) to determine which item is awarded.
5. Once the battle has completed and the server seed is revealed, anyone can independently reproduce and verify every roll result and item drop.
6. If a pre-battle server seed hash was published beforehand, players can additionally verify that the revealed server seed matches the original commitment.

The verifier below allows you to independently audit every battle roll using the same algorithm used by our backend servers.

---

Mines

1. In Mines, the board layout is generated using a provably fair combination of the revealed server seed, client seed, nonce, and selected mine count.
2. Our system generates deterministic bytes using HMAC-SHA256, with the server seed as the secret key and the value clientSeed:nonce:round as the message.
3. These bytes are grouped into sets of four and converted into floating-point values between 0 and 1.
4. The generated floats are used to shuffle the 25 board tiles, numbered from 0 to 24.
5. After shuffling, the first tiles from the shuffled result are selected as mine positions based on the chosen mine count.
6. Once the server seed has been revealed, players can independently reproduce the mine positions and confirm that the board layout matches the original game result.

The verifier below allows players to audit a Mines round using the same tile generation algorithm used by our backend servers.

---

Loot Unboxing

1. In Loot Unboxing, each roll is generated using a provably fair combination of the revealed server seed, client seed, and nonce.
2. For every roll, our system generates an HMAC-SHA256 hash using the server seed as the secret key and the value clientSeed:nonce as the message.
3. The first 15 hexadecimal characters of the generated hash are converted into an integer and transformed into a roll result between 1 and 100,000.
4. The roll result is then checked against the dropped item‘s range, using its rangeFrom and rangeTo values.
5. If the generated hash, roll result, and item range all match the recorded roll data, the Loot Unboxing result is verified.
6. Once the server seed has been revealed, players can independently reproduce the roll and confirm that the item drop was generated fairly.

The verifier below allows players to audit a Loot Unboxing roll using the same algorithm used by our backend servers.