Rust Gambling
rustgambling.site / research / fairness

fairness and verifier documentation: Rust operator evidence index

Official-source records for fairness and verifier documentation across eight documented Rust-facing operators. Unknown facts remain unresolved and no transaction testing is claimed.

Dataset version 2026-10-26.1 · published · revised · latest source observation in this topic . A revision date does not renew older source observations.

JSON datasetCSV datasetMethod

Which games does the verifier cover?

A fairness page can describe several different systems. Match the named game to its published inputs and verification steps before applying a statement to the operator’s whole catalogue.

  • Look for the pre-round commitment, the inputs disclosed afterwards and the game-specific calculation.
  • Distinguish a documented verifier from an independently replayed round. Neither a source link nor a seed explanation establishes payout performance.

Example from the registry: Bandit Camp’s help page distinguishes EOS-block formats from games using a client-seed system. The recorded scope therefore matters as much as the existence of a fairness page. Inspect the Bandit Camp verifier scope.

OperatorsRecorded fieldStatusEvidence
RustSnowballA public route documents completed-round verification for supported games.No live wager or completed round was independently replayed.verified
RustClashServer-seed, client-seed and game-specific verification topics are documented.No live round was independently recreated.verified
HowlA public verifier exposes seed records and completed-round fields.No live round was independently recreated.verified
BanditCampThe help page distinguishes EOS-block inputs for named multiplayer formats from a client-seed system for Beancan Blast, Crate Unboxing and Mines. Completed-game instructions distinguish the EOS block hash from its number and the revealed server secret from its hash.A documented workflow is not a fairness certification; no live round was replayed.verified
RustyLootA dedicated fairness route responded; client rendering limited the captured detail.A documented workflow is not a fairness certification; no live round was replayed.partial
RustMagicA dedicated provably-fair route responded; game-specific detail remains partial.A documented workflow is not a fairness certification; no live round was replayed.partial
RustReaperThe public fairness page describes server seed, client seed, nonce and game-specific algorithms.A documented workflow is not a fairness certification; no live round was replayed.verified
500 CasinoA dedicated fairness route is linked publicly; automated access was protected when checked.A documented workflow is not a fairness certification; no live round was replayed.partial

Methodology, limitations and citation

  • Public official sources only; no account, deposit, wager, KYC, support or withdrawal test was performed.
  • Unknown means the current source pack did not establish a field; it does not prove absence.
  • Record hashes identify normalized evidence records, not byte-for-byte archives of remote pages.

Suggested citation: rustgambling.site, Rust Operator Claim Graph 2026, version 2026-10-26.1, CC BY 4.0.

For a specific finding, include its claim ID, official source ID and source observation date. Link to the row anchor, for example rc-kyc, rather than citing the total number of sources. Download the derived coverage audit; unresolved values are preserved.