NXB

A PLAIN-LANGUAGE GUIDE

How NXB fairness works in a supported game session.

Start with the rules, follow the game state, then review the completed result and any proof information the experience makes available.

Explore BCRNGOpen NXB

Fairness is a flow, not a slogan.

A player’s understanding begins before a session. The game objective, available actions and active rules explain what the player is choosing. During play, the state shown in the interface—such as a timer, a turn, a committed status or a completed round—helps the player understand what is happening now.

After a game completes, the product can present the result and, in supported experiences, information relating to the BCRNG proof lifecycle. That lifecycle is a technical transparency mechanism: it can show that a session was committed before play, then revealed after a result for verification. It does not forecast or guarantee an outcome.

The useful question is always specific: “What did this session show, and how can I check it?” The answer comes from the current session information, the relevant game rules and the product support route—not from a generic claim that all outcomes will be favourable.

THE RESULT LIFECYCLE

Four stages of a transparent game result.

  1. Read the applicable rules. Every game begins with the rule set, objective and session conditions provided by the product. This is where a player learns how the format operates.
  2. Commit before play, where supported. BCRNG-supported sessions can show a committed state before gameplay proceeds. The purpose is to establish a pre-play reference for that specific session.
  3. Reveal after the result. Once the session completes, the product can present the result and move the associated proof information to a revealed state.
  4. Verify the session information. Where the experience exposes verification, use the proof or session reference shown there. A failed verification is a support matter; it is not something this public page can resolve.

BCRNG is an NXB protocol concept and a supported-game transparency feature. It is not presented here as an external certification, universal guarantee or public API promise.

WHY IT HELPS

Less ambiguity around a result

Clear timing and state labels help a player follow one game session from start to finish without relying on assumptions.

WHAT TO DO NEXT

Use the game’s own information

Open NXB, select a supported game and look for the current rules, status and result details. Use support if a session-specific question remains.

Open NXB