FAQ & Troubleshooting

Common questions and fixes. If your issue isn’t here, check Security or reach out via Chat.

”Wrong network”

Switch to Base (8453). Browsing works read-only; actions blocked until you switch.

The wallet button says “Use claimru.sh”

You are on a non-canonical public host. ClaimRush intentionally disables wallet connects, signatures, and onchain writes there.

Fix: Open https://claimru.sh directly, then reconnect and continue from the official site.

”Price moved”

State changed before your transaction confirmed (someone took over, swap quote changed).

Fix: Refresh quote, retry. For takeovers, this usually means someone took over first.

I closed the action window while the wallet or transaction was still pending

The transaction may still be live in your wallet or already onchain.

Fix: Re-open the action page, reconnect if needed, and check the tx hash on the explorer before retrying. Do not spam retries while a previous transaction may still be pending.

Overview shows stale numbers after a transaction

Successful transactions trigger an immediate Overview cache refresh. If numbers still look off, it is usually indexer lag — the subgraph has not processed the block yet.

Fix: Wait a few seconds — the app automatically refreshes Overview data after a confirmed transaction. If numbers still look wrong, navigate away and back as a fallback.

If numbers still look wrong after 30 seconds, check the block explorer for your latest transaction to confirm its status.

The header says “Data delayed” or “OFFLINE”

That warning is about the app’s indexer, not necessarily the protocol itself. The protocol is still live — use Security or the block explorer to verify current state at any time.

Fix: Verify critical state on Security or on the block explorer. Recent activity, leaderboards, and some history views can lag even while the underlying action succeeded onchain.

”Insufficient funds”

Need ETH for gas.

ETH path: need ETH for the current cost + gas.
Token path (if available): need enough of the selected token + ETH for gas (and possibly a one-time approval).

Why can’t I withdraw my locked CLAIM?

Locks are time-based. You can only unlock after expiry (and AutoMax must be off).

Early exit paths:

Sell back to the Furnace for instant liquidity (protocol-quoted). See The Furnace — Exiting.
List on Market with a minimum payout floor. See Market — List Lock.

”Listing cooldown” (can’t delist or relist immediately)

Market listing state changes are rate-limited by a 1-block cooldown.

Typical symptom: you list, then immediately try to delist/relist, and the transaction reverts.

Fix: Wait for the next block, then try again.

Why didn’t LP rewards spike after a big Furnace event?

LP incentives are streamed over time. Big events fund the stream immediately, but rewards accrue smoothly — not as instant jumps.

Why is the “Sell now” quote low?

Sellback is protocol-quoted with a dynamic spread. Common reasons: high bonus environment (larger spread), long remaining time (especially AutoMax locks), large sell, or tight reserve.

Alternative: Use a Market listing to set a minimum payout floor and wait for a better quote. See Market.

Why does my veCLAIM go down?

veCLAIM decays as time remaining on the lock decreases. This is by design — it incentivizes extending or using AutoMax.

Maintain veCLAIM: Extend the lock (which also earns a bonus on your existing capital), enable AutoMax for automatic daily bonus growth, or compound into a long-duration lock.

Is AutoMax always on?

No. AutoMax is a per-lock toggle.

ON: Lock stays at 1-year remaining, maximum veCLAIM, no decay, automatic daily bonus growth from keepers, cannot unlock
OFF: Required to start the unlock countdown (1-year from when you disable)

Why is “Accrued ETH” lower than expected?

You collected recently
Your veCLAIM share changed (others locked more, or your lock decayed)
Very early game: accrual can look lumpy while the first veCLAIM checkpoints settle. The 100 veCLAIM safeguard applies only to residual/manual flushes, not to canonical takeover allocations.

Takeovers are paused. What happens?

Pauses are rare and guardian-controlled.

Nobody can become King
Current King stops accruing CLAIM immediately
Mining time lost during a pause is not compensated after unpausing

Locking is paused. What happens?

Cannot lock via the Furnace or use lock-routing actions like Collect & Lock / Harvest & Lock
Existing locks remain intact
In the app, lock-management writes (extend, merge, unlock) are also disabled until locking resumes, even though the underlying contracts do not enforce this restriction
Plain Collect ETH still remains available

Where do I see official addresses?

App footer → Security → contract explorer links. See Security.

Is there official Telegram or Discord?

No. Use in-app chat, X (@claimrushgame, @claimrushdev), or security@claimru.sh.