Skip to Content
Safety & Risk

Safety & Risk

TL;DR — Only use claimru.sh. Verify addresses via the in-app Security page. Bot sessions are not token approvals. This is a paid onchain game — do not play with funds you cannot afford to lose.

ClaimRush is a paid onchain game. This page covers how to stay safe and what risks to understand before playing.

Verify you are on the official site

  • Only official domain: claimru.sh
  • Do not trust link aggregators or “support” DMs
  • In Chat, only *.claimru.sh/* links are clickable

Protocol guarantees

  • No premine, no treasury — launch seed CLAIM goes into locked LP, not wallets. See Genesis for the full accounting.
  • 0% platform fee
  • Payouts and core rules are onchain
  • Contract addresses published in-app

Verify contract addresses

In app footer → Security:

  • Copy/verify addresses, open explorer links
  • Check pause status (takeovers, locking, trading)
  • See live governance and pause-control addresses, plus routing configuration details
  • Treat /security  as a cross-checking tool; verify critical addresses and permissions on the explorer too

Approval safety

Some actions require token approvals.

  • Check spender address in wallet prompt
  • Prefer exact or finite approvals
  • Revoke unused approvals

Bots and delegation sessions (optional)

If you use third-party automation, use Bot access sessions to grant a trusted address limited permissions.

In Header menu → AdvancedBot access:

  • Add the bot address
  • Select only the permissions you need
  • Set a short expiry (start with 1 day)
  • Revoke anytime

Notes:

  • Bot access sessions are not token approvals. They do not let a bot spend your ERC20 balance.
  • Always verify addresses and revoke sessions you no longer use.

See: Bots & Automation

Governance state

ClaimRush moves through two governance phases. Before finality, the game is live and fully playable, with core contracts patchable through a time-delayed governance process and a guardian able to pause for incident response. After finality, governance has executed a single onchain ceremony that permanently freezes core configuration and burns the runtime upgrade keys; core game logic can no longer be upgraded. The Security page in the app footer detects the current phase automatically.

See Finality for the full explanation of both phases, the freeze-and-burn ceremony, what stays adjustable afterward, and what changes in the app when finality lands.

Risk & eligibility

  • This is a paid onchain game. You can lose money.
  • Token prices move quickly; swaps may execute at worse prices (slippage/MEV)
  • Network fees apply; transactions irreversible once submitted
  • Locking CLAIM is not instantly withdrawable
  • Early exit is by listing the lock on Market (limit sell to Furnace) or selling back to the Furnace directly (instant liquidity, protocol-priced)
  • Smart contracts and infrastructure can fail or have bugs
  • Only use if 18+ (or age of majority) and allowed to use crypto in your jurisdiction
  • Do not play with funds you cannot afford to lose

Report issues

Contact form  — phishing, bugs, and other reports

See also

  • Security — Verify addresses and check pause status
  • Genesis — Launch event and the genesis LP lock
  • Finality — Freeze-and-burn ceremony and post-finality governance
  • The House — The developer-controlled player and fairness guarantees
  • Bots & Automation — Delegation safety
  • Core Concepts — Understanding the protocol