Skins. Codes. Clear answers.

Guides/Rust site guides

Rust site guides

Bandit.Camp: what Awaiting EOS Block means

Awaiting EOS Block means a selected future blockchain block is not available yet. Keep the round ID; verify the finished game with its block hash.

3 min read
Published Revised

THE QUICK ANSWER

The EOS wait belongs to result generation. After completion, use the full EOS block hash in the verifier, not the short block number.

Bandit.Camp logo
Bandit.Camp: EOS wait and verification

01

The round is waiting for its chosen block

Bandit.Camp documents “Awaiting EOS Block #XXXX” as a result-generation status: the game cannot roll until the future EOS block selected for it has been mined. The number in the message identifies that block; it is not a Steam offer number.

Keep the game type, round ID and the exact message. This lets you distinguish an unfinished round from a completed round whose result you want to check.

STRIKEPOT / EXPLAINED

Why an EOS round can pause

  1. Round opens

    A public commitment is visible.

  2. Game locks

    The future block is selected under the game’s rules.

  3. Awaiting EOS block

    The chosen block is not mined yet.

  4. Completed round

    Revealed data can be checked against the result.

Original explanation of the documented result timeline; not a screenshot or a measured delay.

Original explanation · not an account screenshot

02

Choose the verifier for the game

The operator describes EOS-based verification for Wheel of Fortune, Coinflip, Spinners, Crate Battles and Crate Jackpot. Beancan Blast, Crate Unboxing and Mines use client-seed pairs instead.

Do not fill an EOS field with a seed-pair value. First match the game name in history to the corresponding instructions in the official fairness article.

Two verification routes
EOS gameRound ID, revealed private key and selected EOS block hash.
Seed-pair gameClient seed and the revealed server secret from an inactive seed pair.

03

Open the completed game’s information

Bandit.Camp directs users to the small information button in game history. Its Game ID may also be labelled Round ID. Preserve that completed record before copying verification values.

For an EOS game, use View EOS block to locate the long hash. The official instructions specifically warn against entering the numeric block number in its place.

STRIKEPOT / EXPLAINED

The two values that look similar

  1. Block number

    Short numeric locator shown in the wait message.

  2. Block hash

    Long block ID used for EOS verification.

  3. Secret hash

    Commitment to a seed; not the revealed server secret.

  4. Revealed secret

    Inactive seed-pair input required by the verifier.

Use field names to avoid entering a commitment or locator where the verifier expects the underlying value.

Original explanation · not an account screenshot

04

A secret hash is not the revealed secret

For seed-pair games, the article says the server secret becomes visible only when the pair is inactive. Entering a new client secret rotates the pair. Read that control before changing it and retain the old pair’s record.

A failed check made with a still-hashed secret does not establish a changed result. Compare the field names and the complete values before drawing a conclusion.

05

Report a stalled round or a reproducible mismatch

For a persistent EOS wait, send support the round ID, selected block number, message and time with a time zone. The reviewed article gives no maximum waiting time, so there is no documented universal timeout to promise.

For a completed-game mismatch, state the verifier route and which values you used. Keep authentication and recovery secrets out of the report. Verifying a past result does not predict a later round.

BEFORE YOU CONTINUE

Quick checklist

  • Save the round ID and game type.
  • Separate the block number from its long hash.
  • Use a revealed server secret for an inactive seed pair.
  • Describe a stalled round separately from a completed-result mismatch.

Official sources

Official operator documentation reviewed on 26 October 2026. The checks below distinguish documented rules from suggested evidence to keep.

Public documentation only. No sign-in, payment, game, withdrawal or personal account test was performed. Recordkeeping suggestions are StrikePot editorial guidance.

Need the details for a particular website?

The code directory records each partner’s code, referral method and offer status. Use the relevant partner page when your question also involves one of those details.

Partner pages may include affiliate links. A listing does not confirm a reward or account eligibility.

KEEP READING

A useful next read.

All guides

Rust site guides · 3 min read

RustyPot: inventory and trade help

Check RustyPot’s inventory view, public Steam inventory and saved Trade URL. For a missing winning offer, keep the round ID and check My profile.

Read guide

Support · 3 min read

A better support ticket

Include the affected order or trade, the exact status and a dated timeline. Use the template to explain what happened and ask for the next step.

Read guide

Support · 2 min read

Share evidence, keep secrets

Show the error, affected item and useful reference. Hide passwords, codes, payment details and unrelated personal information before sharing.

Read guide