Swarm Beacon
Technical specification of the Rover data synchronization protocol.
Swarm Beacon
The Beacon is the heartbeat of your Rover, delivering critical telemetry and performance data to the Swarm network.
Payload Specification
The Beacon is a signed JSON payload sent at the end of every Seeker or Keeper cycle.
{
"logs": [
"Seeker cycle complete: 14 pools scanned",
"Enter executed: token pair SOL/USDC"
],
"stakes": [
{
"pool": "AR9...xYp",
"txHash": "5mN...2q",
"pnl": 0.124,
"timestamp": 1776800000000
}
],
"thresholds": {
"preset": "moderate",
"minTvl": 15000
},
"version": "0.5.0",
"signature": "64_char_hmac_sha256"
}Data Components
Logs
Recent AI-generated reasoning and tool execution logs for dashboard display.
Stakes
Verified on-chain transactions of closed positions for Radar aggregation.
Thresholds
Current risk parameters used by the agent to find median Swarm benchmarks.
Security & Verification
Each Beacon must pass three layers of validation before it is accepted by the Swarm:
- Authentication: The request must include a valid
goroverScoutKeyin the headers. - Integrity: The
signaturefield must match an HMAC-SHA256 hash of the payload, signed with your Scout secret. - On-chain Audit: Stake data is verified against the Solana mainnet. Fake PnL claims or invalid transaction hashes lead to immediate rejection and temporary Scout flagging.
Submitting corrupted or poisoned data to Swarm will result in your Scout being marked as Abusive, revoking your access to Radar intelligence.
Troubleshooting
Cause: Scout is in a Dormant or Inactive state.
Fix: Restart your Rover to send a fresh heartbeat.
Cause: Schema mismatch or suspicious PnL data.
Fix: Update your gorover-agent to the latest version.