Safety and risk

Verify you are on the official site

In app footer → Security:

Some actions require token approvals.

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

In app footer → Security → Bot access:

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.

ClaimRush launches in two phases:

Phase 1 — Pre-freeze (launch through external audit)

The protocol is live and fully playable.
The admin (owner) retains the ability to re-wire contract addresses (e.g., swap in a fixed Furnace or router). This is intentional: it allows the team to apply fixes from the external security audit before locking the protocol permanently.
The guardian can pause takeovers, locking, or trading for incident response.
All gameplay, payouts, and rules are onchain and verifiable during this phase.

Phase 2 — Post-freeze (permanent)

The admin calls freezeConfig() on each core contract. This is a one-way, irreversible action.
After freeze, contract wiring cannot be changed. The protocol runs on code alone.
The guardian retains pause/unpause capability for safety, but cannot change economics, upgrade contracts, or move funds.

You can verify the current freeze status in the app footer under Security.

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

security@claimru.sh — phishing, bugs