Bots & Automation

TL;DR — Grant a trusted bot a time-bound, permissioned session to act for your address. Bot access sessions are onchain delegations, not token approvals — no wallet custody, no spending rights. Use short expiries (start with 1 day) and only the permissions you need.

ClaimRush is permissionless — EOAs and smart contracts can play, and anyone can build automation. This page covers how to grant a trusted bot limited access to act on your behalf.

Bot access is an onchain permission grant, not a token approval — it lets a trusted address perform specific game actions on your behalf without giving it custody of your wallet. For governance and contract architecture details, see Safety & Risk — Governance state.

Should I use a bot?

Most players do not need one. Bots are useful if you:

Want to take over the Crown automatically when the cost drops to a target range
Want to auto-collect royalties or compound without logging in
Want a bot to maintain your locks (extend, merge, unlock expired) on a schedule

If you’re just locking CLAIM and collecting royalties occasionally, you don’t need bot access. The app’s built-in auto-compound handles the most common automation use case without delegation.

Session mechanics

A bot session is:

a delegate address (the bot)
a permission set (what it can do)
an expiry time (when it automatically stops working)

Sessions are off by default and can be revoked at any time. A bot session does not give custody of your wallet and does not approve spending your ERC20 tokens — it only enables specific protocol functions.

Common uses

Crown automation: A bot pays ETH and takes over for you on a schedule. See Crown bot routing for how payouts are directed.
Collect automation: A bot runs Collect ETH / Collect & Lock for you and withdraws any fallback King payout buckets.
Furnace automation: A bot enters the Furnace for you using its own ETH/CLAIM/tokens.
Lock maintenance: A bot extends locks, merges locks, or unlocks expired ones. CLAIM always returns to you.
Config automation: A bot updates your auto-lock / auto-compound settings.

Where to manage bot access

Header menu → Advanced → Bot access. (See: Security page)

You can: add a delegate address, choose permissions, set an expiry, Grant / Revoke.

What a bot cannot do

Spend your tokens. No permission lets a bot transfer CLAIM or other tokens from your wallet.
Manage Market positions. Listing, selling, and escrow management are intentionally not delegated in v1.0.0. For Market automation, use a bot-owned wallet.
Access your private key. Bot sessions are onchain delegation, not key sharing.

Safety checklist

Only delegate to a bot address you control or deeply trust.
Use short expiries (start with 1 day).
Start with minimal permissions and expand only if needed.
Revoke sessions you no longer use.
Use Radar notifications for security events (bot session used, session granted/revoked, recipients changed).
Verify contract addresses in the app footer → Security.

Review and alerts

The Bot access screen helps you review automation permissions “like approvals”:

shows each session’s delegate, expiry, and permissions
highlights high-risk permissions with clear warnings
shows last used time + last action type
links to the transaction hash for recent activity
includes an emergency stop: Revoke all sessions

Crown bot routing

When a bot takes over for you:

You become the King identity.
By default: the bot receives the 75% ETH payout (so it can keep looping), your mined CLAIM stays with you.
Optional: grant Route reign CLAIM to bot to send mined CLAIM to the bot instead.

Mid-reign routing changes live under Advanced routing controls (collapsed by default in the Bot access UI). Prefer scoped restore options (“restore to bot only” / “restore to you only”) when possible.

Permissions reference

Permissions are grouped in the UI. Only grant what you need.

Crown (MineCore)

Permission	Meaning
Takeover for you	Bot can pay ETH to take over, but your address becomes King.
Set reign ETH recipient	Bot can redirect the dethroned-King 75% ETH payout for your current reign. High risk.
Restore reign ETH recipient (bot only)	Bot can restore the current reign so the dethroned ETH payout recipient is the bot (repair only).
Set reign CLAIM recipient	Bot can redirect the mined CLAIM stream of your current reign. High risk.
Restore reign CLAIM recipient (to you only)	Bot can restore mined CLAIM routing back to you.
Route reign CLAIM to bot (optional)	At takeover time, lets a delegated takeover start with mined CLAIM routed to the bot instead of you.

Collect (payouts)

Terminology note: some onchain action types are named with the word claim (for example the claimShareholderEth SDK method). In user flows, these correspond to Collect / Collect & Lock.

Permission	Meaning
Withdraw King ETH	Bot can withdraw your fallback King ETH bucket (ETH always goes to you).
Collect shareholder rewards	Bot can run your Baron payout (Collect ETH or Collect & Lock).
Harvest (collect + withdraw)	Bot can run the bundled collect-all flow for you (Baron payout + King ETH bucket withdraw).

Furnace

Permission	Meaning
Enter Furnace with ETH	Bot pays ETH, you receive the veCLAIM lock + bonus.
Enter Furnace with CLAIM	Bot pays CLAIM, you receive the veCLAIM lock + bonus.
Enter Furnace with token	Bot pays an allowlisted token, you receive the veCLAIM lock + bonus.

Locks (veCLAIM maintenance)

Permission	Meaning
Extend veCLAIM lock	Bot can extend your lock duration (can only increase, cannot shorten).
Merge veCLAIM locks	Bot can merge two of your locks into one (irreversible).
Unlock expired veCLAIM lock	Bot can unlock an expired lock; CLAIM always returns to you.

Automation settings

Permission	Meaning
Set King auto-lock config	Bot can update your King auto-lock settings (config only; does not move funds).
Set shareholder auto-compound config	Bot can update your shareholder auto-compound settings (config only; does not move funds).
Set LP auto-compound config	Bot can update your LP staking auto-compound settings (config only; does not move funds).

Developers

If you want to build a bot that plays from its own wallet (no delegation), see the developer manual: Agents and automation .

Talk to an AI assistant (Base MCP)

If you’d rather not run any automation at all but still want to drive ClaimRush from a chat-style interface, ClaimRush ships a Base MCP plugin so compatible AI assistants on Base can read your state and prepare actions on your behalf. You sign every transaction yourself — the assistant produces unsigned calldata and your wallet prompts you once before executing the batch atomically.

See the tutorial: Use with an AI assistant (Base MCP).

The plugin worker never holds keys, never broadcasts transactions, and refuses to emit calldata when the protocol is still in the pre-launch genesis window.

Chat-driven bot (advanced)

The repository ships an OpenClaw / Cursor workspace skill at skills/claimrush/ that wraps the developer SDK with a chat-friendly CLI. It is for power users who already run a chat-based AI agent runner and want one prompt-driven surface for the protocol.

Highlights:

runs from your own wallet and your own RPC; the skill never holds keys
every write is dry-run unless you pass --execute
mainnet writes additionally require --i-understand and an RPC URL listed in CR_SKILL_BASE_RPC_ALLOWLIST
the same CRAL safety pack the developer manual references is loaded at startup, so the chat agent sees the same hard rules a human integrator does

Set up once:


bash skills/claimrush/scripts/setup.sh

Then in chat (or any shell):


RPC_URL=http://127.0.0.1:8545 bash skills/claimrush/scripts/cr.sh status --pretty
RPC_URL=http://127.0.0.1:8545 bash skills/claimrush/scripts/cr.sh agent

For the full walk-through (local Anvil, Base Sepolia, mainnet preflight), see the developer tutorial: Run the ClaimRush OpenClaw skill .

The skill does not give the chat runner custody of your wallet and does not change what permissions a DelegationHub session grants. It is a thinner, chat-shaped front door for the same SDK that powers self-run and delegated bots above.