Bots and automation (optional)
ClaimRush is permissionless:
- EOAs and smart contracts can play.
- Anyone can build automation.
Note: Before config freeze, the admin can re-wire contract addresses (to apply audit fixes). Gameplay is permissionless from day one, but contract wiring is not yet permanent. See Safety and risk — Protocol phases.
If you want a trusted bot to do actions for your address, you can grant Bot access (a delegation session) using the onchain DelegationHub.
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.
Where to manage bot access
In the app footer → Security → Bot access.
You can:
- add a delegate address
- choose permissions
- set an expiry
- Grant / Revoke
Audit and alerts
The Bot access screen also helps you audit automation “like approvals”:
- shows each session’s delegate, expiry, and permissions
- highlights high-risk permissions with clear warnings
- shows last used time + last action type (takeover / claim / furnace enter / lock maintenance / settings)
- links to the transaction hash for recent activity
- includes an emergency stop: Revoke all sessions
For extra safety, enable Radar notifications for security events:
- bot session used
- bot session granted/updated/revoked
- reign recipients changed mid-reign
Common uses
- Crown automation: a bot pays ETH and takes over the Crown for you at a schedule (ex: when cost is low).
- Look for bots that read the current reign id + price right before sending, and avoid leaving transactions pending for long.
- Collect automation: a bot runs Collect / 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/allowlisted tokens.
- Lock maintenance: a bot keeps your veCLAIM position tidy (extend lock, merge locks, unlock expired locks).
- Config automation: a bot updates your auto-lock / auto-compound settings.
What a bot can and cannot do
A bot session:
- does not give custody of your wallet
- does not approve spending your ERC20 tokens
- only enables specific protocol functions (permissioned per-session)
A bot may still spend its own funds when acting (example: ETH to take over).
Not included in Bot access sessions (v1.0.0):
- Market management (listing/selling locks, managing escrow orders) is intentionally not delegated.
- There are no Market delegation permissions in v1.0.0.
- If you want automation here, do it from a bot-owned wallet address, not via delegation.
- Spending your ERC20 balances is not delegated.
- There are no permissions that let a bot transfer your CLAIM (or other tokens) out of your wallet.
- A bot can still create or add to veCLAIM locks only when it pays (via Furnace
...Forentrypoints).
- Lock maintenance is delegated and non-custodial:
- extend lock, merge locks, unlock expired locks (CLAIM always returns to you)
Permissions (what they mean)
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; useful if you became King without a bot). |
| 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 if it was changed (for example after routing CLAIM to the bot). |
| 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)
| Permission | Meaning |
|---|---|
| Withdraw King bucket | Bot can withdraw your fallback King ETH bucket (ETH always goes to you). |
| Claim shareholder rewards | Bot can run your Baron claim (Collect ETH or Collect & Lock). |
| Claim all | Bot can run a bundled “claim all” for you (Baron claim + King bucket withdraw). |
Furnace
| Permission | Meaning |
|---|---|
| Enter with bot-paid ETH | Bot pays ETH, you receive the veCLAIM lock. |
| Enter with bot-paid CLAIM | Bot pays CLAIM, you receive the veCLAIM lock. |
| Enter with bot-paid token | Bot pays an allowlisted token, you receive the veCLAIM lock. |
Locks (veCLAIM maintenance)
| Permission | Meaning |
|---|---|
| Extend veCLAIM lock | Bot can extend your existing veCLAIM lock duration (can only increase, cannot shorten). |
| Merge veCLAIM locks | Bot can merge two of your veCLAIM locks into one (irreversible). |
| Unlock expired veCLAIM lock | Bot can unlock an expired veCLAIM 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). |
Crown bot payout routing (important)
When a bot takes over for you:
- You become the King identity.
- By default:
- the bot receives the 75% dethroned-King ETH payout (so it can keep looping)
- your mined CLAIM stays with you
Optional:
- If you grant Route reign CLAIM to bot, the CLAIM mined during your reign is minted to the bot.
Mid-reign changes (advanced):
- These controls grant permission only; they do not change routing by themselves.
- In the Bot access UI, recipient controls live under Advanced routing controls (collapsed by default).
- A bot can only change routing mid-reign if you grant the matching reign … recipient permission (restore-only or any-address).
- Prefer the scoped restore options (“restore to bot only” / “restore to you only”) when possible.
- If the bot always takes over for you, ETH routing already defaults to the bot, so most users can leave the ETH recipient control on “No mid-reign changes”.
You can revoke the bot session at any time.
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 Inbox (and optional push notifications) to notice bot session activity.
- Verify contract addresses in the app footer → Security.
Developers
If you want to build a bot that plays from its own wallet (no delegation), see the developer manual: developers.claimru.sh → Agents and automation.