Terracore Automation

Overview

Terrabot Cloud automates claiming, battling, and intelligent stat-upgrading across multiple accounts for the Terracore game on the Hive blockchain — then presents everything in a real-time management dashboard accessible from any browser. Private keys are AES-256 encrypted at rest and never exposed in memory.

The Problem

Managing multiple Terracore accounts by hand is unsustainable at scale. Optimal claiming requires constant attention — a missed claim is lost SCRAP. Upgrade decisions (Defense vs. Engineering vs. Damage) depend on live game state across all accounts at once, there's no single place to see every account's status, and poor timing or silently skipping low-RC accounts wastes resources on failed transactions.

The Solution

Terrabot Cloud fully automates the routine Terracore loop and surfaces all account intelligence in one dashboard. The bot runs 24/7 in the cloud — claiming at optimal thresholds, battling weaker targets, and applying AI-assisted upgrade recommendations — all while keeping private keys encrypted. The dashboard streams live terminal output, stats analytics, health monitoring, RC tracking, and one-click manual operations over a persistent socket connection.

Key Features

• Automatic claiming, battling, and smart stat upgrades
• Manages multiple accounts from one dashboard
• Real-time terminal and live bot log over WebSockets
• AES-256 encrypted keys, never exposed in memory

Tech Stack & Why

• Node.js — Great for long-running, event-driven automation and talking to blockchain APIs.
• Socket.IO — Pushes live logs and bot state to the dashboard the instant things happen.
• Hive API — The game runs on Hive — direct chain calls are how the bot acts on accounts.
• AES-256 encryption — Private keys are sensitive; encrypting at rest was non-negotiable for user trust.

Biggest Challenge

Coordinating many accounts against one rate-limited blockchain without failed transactions. Running the loop across every account naively meant overlapping RC drain, race conditions on shared state, and Hive nodes throttling bursts of requests. The fix was a coordinator layer that serializes and paces on-chain calls, plus RC-monitoring that skips any account under 20% RC before attempting a broadcast — turning silent failures into deterministic, observable skips.

Results & Impact

• Runs 24/7 in production on Render
• Manages 50+ accounts across multiple players from one dashboard
• 50M+ SCRAP claimed and optimized via automated routines
• 40+ automated contract tests guard the socket layer (currently v11.14)

What I Learned

Handling private keys made security the headline, not a footnote — I learned to encrypt at rest, keep secrets out of memory, and think like an attacker. Building the real-time dashboard also deepened my grasp of WebSockets and stateful background workers.