Running Crypto Trading Bots on Hyperliquid 24/7 — Tech Stack, Architecture & Lessons Learned

Introduction I run three types of trading bots on Hyperliquid, an on-chain order book DEX, 24/7 on a VPS: Grid Bots across 5 pairs, a Funding Rate arbitrage bot, and a Liquidation Cascade detector. This is a technical deep dive into the stack, architecture decisions, and real operational challenges. No trading advice — just engineering. Why Hyperliquid Unlike AMM-based DEXes, Hyperliquid runs a full order book on its own L1 chain. For bot developers, this means: Limit orders (not just market orders like AMMs) Real-time order book data via WebSocket Maker fee: 0.01% (with VIP rebates) Taker fee: 0.035% Near-zero gas costs REST + WebSocket APIs, ccxt support REST: https://api.hyperliquid.xyz WebSocket: wss://api.hyperliquid.xyz/ws Tech Stack Runtime : Node.js Exchange API : ccxt (Hyperliquid supported) Tx Signing : ethers.js v5 Database : SQLite (WAL mode) Process Manager : PM2 Server : Ubuntu 22.04 VPS ccxt Integration ccxt provides a unified API across 100+ exchanges. Switching between