Getting Started

Security Checklist

Mandatory safety protocols for GoRover operators.

Security Checklist

GoRover executes real transactions. Failure to follow these protocols may lead to permanent loss of funds.

CRITICAL: GoRover is an autonomous agent. It will spend your funds based on your configuration and LLM reasoning. Never fund more than you are willing to lose.

Protocol Hierarchy

1. Key Management

Cold Storage: Never store your wallet seed phrase in a digital format.
Config Isolation: Ensure rover.config.ts is added to .gitignore.
Scout Privacy: Treat your sc_xxx key as a password. If leaked, revoke it immediately in the dashboard.

2. Operational Safety

Simulation First: Run with dryRun: true for at least 24 hours.
Small Capital: Start with 0.1 - 0.5 SOL to verify execution logic.
Telegram Alerts: Connect your Telegram in Dashboard → Settings to receive real-time Drift and Exit alerts.

3. Identity Verification

Wallet Match: Ensure the walletKey in your config matches the address connected to your GoRover dashboard.

Sensitive Assets

Private

`walletKey`

Full access to your funds. Extreme Risk.

Secret

`goroverScoutKey`

Identity in Swarm. Compromise leads to data poisoning.

Emergency Protocol

If you detect anomalous Rover behavior or unexpected trades:

TERMINATE: Force stop the agent process immediately.
```
# Kill the agent
gorover-agent stop
```
AUDIT: Inspect registry.json for open Stakes and manually exit via Meteora UI if necessary.
ROTATE: If keys were exposed, transfer remaining funds to a new wallet and revoke the Scout key.

Next Steps

Config Reference

Learn how to tune your Rover.

Cycles Explained

Understand the inner workings.

Quickstart

Get your Rover online in under 5 minutes.

Configuration Reference

Technical specification for all `rover.config.ts` parameters.

On this page

Protocol Hierarchy 1. Key Management 2. Operational Safety 3. Identity Verification Sensitive Assets Emergency Protocol Next Steps