Protocol Architecture: Infrastructure + Contracts
LiquidBots is built to be modular, gas-optimized, and upgradable - with clear separation between strategy logic, capital flows, and protocol governance.
Key Components:
Strategy Config Storage
Core logic for GridBot, DCA+, Arbitrage modules. Store parameters for each bot.
N/A
Vault Factory
Permissionless contract to deploy new strategy vaults with unique logic templates and fee structure.
N/A
Performance Router
Routes PnL, strategy yield, and protocol fees into treasury allocation.
N/A
Governance Module
$esLBOT stakers vote on protocol parameters: vault caps, strategy whitelisting, emissions.
N/A
Frontend Interface
Built with Next.js + wagmi for multi-wallet, multi-chain compatibility.
N/A
Bot Control API (Phase 2)
Optional backend for Telegram power-users and strategist integrations.
N/A
Subgraph Indexing
Strategy execution, vault stats, and APYs are indexed via The Graph or custom off-chain indexing.
N/A
Execution Agents
Off-chain bots that read config and route trades via API.
N/A
Deployment Stack:
First deployments on HyperEVM (for speed, EVM compatibility, and user base) & integration with Hyperliquid API
Expansion targets: Base Chain (Flex Perps), Aevo AppChain, Hyperliquid (via SDK/API bridge), and more to come
LiquidBots operates as a hybrid system - with on-chain capital custody, parameter storage, and fee routing; and off-chain deterministic bots executing strategy logic via API-integrated agents. This separation allows for gas-efficiency, faster iteration, and compatibility with high-performance perps venues like Hyperliquid and Flex DEX
Security:
Strategy modules are individually audited and parameter-limited
Vaults run on upgradable proxy templates with multisig pausing ability
Execution pricing is sourced directly from connected trading platforms (e.g., Hyperliquid, Aevo), using their native price feeds and trade APIs. LiquidBots does not rely on external oracles (e.g., Pyth or Chainlink) for strategy execution
Bug bounty program planned pre-TGE
LiquidBots is infrastructure. And the architecture reflects it - flexible enough to scale, strict enough to survive.
Last updated