Public-record methodology

rustgambling.site maps narrow operator, policy, cashier and fairness claims to dated operator-controlled sources. It does not rank operators, infer missing facts or treat documentation as proof of safety, legality or successful payout.

Follow one claim from the table to the document

Start with the question you need answered: account verification, redemption conditions or game verification. Each row gives a recorded statement, its evidence state, a limitation and the source IDs used to support it.

For example, the RustClash account-check record points to its terms. Read the cited clause and the source observation date together. The record establishes published wording; it does not show that anyone completed the operator’s verification process.

Publication gate

An operator file becomes indexable only when it contains at least three official sources and all six required fields:

• Operator identity.
• Licence claim and regulator-match state.
• KYC and account-verification wording.
• Withdrawal, custody and settlement documentation.
• Operator-published location restrictions.
• Fairness, verifier or game-formula documentation.

A field may remain unknown. The gate requires an explicit record and limitation, not a positive result.

Evidence states

• Verified — the cited official source directly supports the narrow recorded claim.
• Partial — an official route exists, but a material detail or consistency check remains incomplete.
• Unknown — the current official-source pack did not establish the field.
• Conflict — current official sources disagree; publication must fail closed.

Hashes and freshness

Each source record has an observation date and a deterministic hash of its normalized URL, observation date and captured claim. It is labelled as a record hash and is not presented as a byte-for-byte archive hash of the remote page.

Where a scoped capture is recorded, its separate hash identifies only the named captured section. Several captured sections can share one URL. They help trace specific claims but do not count as independent corroborating sources.

• Source observation: when the named content was inspected. A new fairness observation does not refresh older identity or withdrawal records.
• Dataset revision: when published records changed. Individual sources can still have earlier observation dates.
• Source-health observation: whether a route responded to a monitor. Availability alone does not verify its policy text.

Inspect the source graph or view the separate source-status records.

Testing boundary

This dataset used no account, deposit, wager, KYC process, support contact or withdrawal. A formula check or public verifier route is not a fairness certification and does not audit production code.

Corrections and change reports

A source observation date changes only after that source is re-observed. Updating a page’s explanation does not renew the source dates. Policy-change reports remain noindex until two material before/after records have current official sources and approval state.