Safety & Risk

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

In app footer → Security:

Copy/verify addresses, open explorer links
Check pause status (takeovers, locking, trading)
See live core owner/guardian addresses plus routing-registry owner/guardian/detected-owner-delay status
Treat /security as a cross-checking tool; verify critical addresses and permissions on the explorer too

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 has two protocol phases:

Phase 1 — Governed launch window

The protocol is live and fully playable. ClaimToken and VeClaimNFT are permanent direct roots. MineCore, Furnace, MarketRouter, and ShareholderRoyalties are proxy-backed runtime contracts, so governance can apply audited runtime fixes without changing their canonical addresses.
The live governance chain is Safe -> TimelockController -> ProxyAdmin -> runtime proxy, plus Safe -> TimelockController -> protocol owner().
Guardian-controlled pause surfaces remain available for incident response, subject to the temporary genesis bootstrap handoff described below.
All gameplay, payouts, and rules are onchain and verifiable during this phase.

Phase 2 — Freeze-and-burn finality

ClaimToken is already frozen and ownerless from Wire.s.sol.
Governance then schedules one timelocked freeze-and-burn batch. That batch freezes the remaining four freeze-gated contracts (MineCore, Furnace, VeClaimNFT, and ShareholderRoyalties) and burns the four runtime ProxyAdmins for MineCore, Furnace, MarketRouter, and ShareholderRoyalties.
The timelock delay is a public onchain countdown to finality. The exact calldata is visible before execution, and the Safe can still cancel during that waiting period if anything looks wrong.
After execution, core wiring is frozen and runtime logic upgrades are no longer possible.
Operational peripherals and routing contracts remain owner-managed through the timelock. That means post-finality admin changes still require schedule -> wait -> execute.
A small set of operational allowlists (for example settlement and compounding keepers) remains owner-managed onchain. The MarketRouter owner retains a documented break-glass settlement path during the keeper grace window. These controls do not change game economics.
After the genesis handoff is complete, the long-term guardian retains pause/unpause capability for safety, but cannot change economics, upgrade contracts, or move funds. During the launch bootstrap only, MineCore.guardian may temporarily be the LaunchController contract for the one-shot genesis finalization flow.

You can verify the current freeze/finality 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