BCRNG BY NXB

Game-result transparency through a commit, reveal and verify lifecycle.

BCRNG is NXB’s blockchain-locked random-number protocol concept for supported game sessions. It helps describe the journey from a pre-play commitment to a post-result verification state.

See the player guide Open NXB

What BCRNG is—and what it is not.

BCRNG is NXB’s fairness and proof-lifecycle concept. In a supported session, the protocol can establish a commitment before play, keep the session locked during gameplay, and make relevant information available after a result so the proof can move through revealed and verified states.

This gives players and technical partners a more concrete way to discuss a result: not merely “trust the game,” but “look at the state and reference that belong to this session.” It is useful only when it is tied to the actual supported experience and its displayed proof information.

BCRNG does not change an outcome, predict a future result, or turn a general marketing page into a result-verification tool. NXB does not claim on this page that BCRNG is independently certified, universally applicable to every product, or available as a public API. A functioning external verifier and documentation would be published separately if and when they are available.

HOW BCRNG IS USED

A session-based record rather than a broad promise.

A supported game starts a session. The relevant experience establishes its own rules, state and session information before the player follows the action.
The protocol can commit the session. A commitment is created before the result is known in the game flow. This is the pre-play reference point.
The result is revealed when the session completes. After the game flow produces a result, the product can expose the related proof information and status.
The proof may be verified. The actual implementation can show a verified state or an available verification path. If a check fails, players should contact support with the session or proof reference.

Use BCRNG terminology precisely. “Commit,” “reveal” and “verify” describe a proof lifecycle in supported sessions; they are not claims of guaranteed outcomes, gaming licences, public audits or investment returns.

FOR PLAYERS

Understand the status you can see

A proof status is most useful alongside the relevant game result and rules. Check the session-specific information provided by NXB.

Read the player guide

FOR PARTNERS

Discuss evidence, not buzzwords

Technical fairness claims require working evidence and documentation. NXB will not describe an unsupported public verification API as available.