Openclaw-crypto-army

Demo

About

OpenClaw Crypto Army: A Docker-based bot management platform that deploys AI-powered blockchain agents. Each bot runs OpenClaw with Foundry toolkit, has its own HD wallet, and communicates via web chat. Monitor multiple bots through a sleek dashboard, manage ENS subdomains, and execute on-chain operations on Sepolia testnet. Built with TypeScript, Express, React, and Ethers.js.

How it's made

## Technical Architecture **Core Stack:** - **Backend:** TypeScript + Express.js with Dockerode for container orchestration - **Frontend:** React + Vite with Tailwind CSS for the dashboard UI - **Blockchain:** Ethers.js v6 for web3 interactions, Foundry toolkit (Cast/Anvil/Forge) for smart contract operations - **AI Framework:** OpenClaw agent system running in Docker containers - **Database:** Simple JSON file storage for bot configs and chat history ## What i did 1. **Custom Docker Image Fusion**: Combined OpenClaw (Node.js AI agent) with Foundry (Rust-based Ethereum toolkit) in a single container. This required installing Foundry as root, copying binaries to system-wide paths, then switching to the 'node' user to avoid permission issues with OpenClaw's file operations. 2. **HD Wallet Army**: Used BIP39/BIP44 derivation to generate deterministic wallets from a single mnemonic. Each bot gets wallet at `m/44'/60'/0'/0/{index}`, making it easy to recover all bot wallets from one seed phrase. 3. **Gateway API Workaround**: OpenClaw doesn't have a standard "webchat" channel, so I bypassed it entirely. Each bot runs in gateway mode with `--allow-unconfigured` flag, exposing an HTTP endpoint on unique ports (18800+). The backend acts as a proxy, forwarding chat messages from the web UI to each bot's gateway and streaming responses back. 4. **Port Collision Prevention**: Generated unique gateway ports by adding the wallet index to base port 18800. Simple but effective for avoiding conflicts when scaling to multiple bots. 5. **ENS Integration**: Implemented on-chain subdomain creation using ethers.js Interface encoding. The system calculates namehashes, encodes `setSubnodeRecord` and `setAddr` transactions, and submits them to Sepolia ENS contracts - all from the master wallet. 6. **Volume Mount Strategy**: Shared `~/.openclaw/workflow` across all bots for common workflows, but isolated per-bot `/app/data` and `/workspace` directories. This balances resource sharing with bot independence. **Technologies:** - **Anthropic Claude API**: Powers the AI responses. **Architecture Flow:** Frontend → Express API → Dockerode → Individual Bot Containers → OpenClaw Gateway → Claude API → Ethereum RPC Each bot is fully isolated with its own container, wallet, and data directory, but shares the workflow patterns and communicates through standardized HTTP endpoints.