How It Works

A deep dive into Farmtardio's automation technology and architecture.

System Architecture

Farmtardio is built on a modern, scalable architecture designed for reliable automation:

Core Components

  • Next.js Frontend - Server-side rendered React application for the dashboard and docs
  • Prisma + PostgreSQL - Database layer for user data, runs, and execution history
  • Worker Queue System - Background job processing for trade execution
  • Exchange Connectors - Modular adapters for each exchange (Pacifica, Lighter)

Automation Engine

Session-Based Trading

Unlike traditional bots that run 24/7, Farmtardio uses session-based trading to mimic human behavior:

  • 3 Sessions Per Day - Trading happens in discrete sessions, not continuously
  • Random Timing - Session start times vary by ±30 minutes
  • Variable Length - Sessions last 60-105 minutes depending on risk level
  • Occasional Skips - Sometimes a session is skipped entirely to look natural

Trade Execution

Each trade follows a sophisticated execution pattern:

  1. Market Selection - Rotate through approved pairs based on risk level
  2. Position Sizing - Randomized within configured bounds (e.g., $20-$50)
  3. Order Placement - Market or limit orders with natural-looking slippage
  4. Risk Management - Automatic stop-loss and take-profit on every position
  5. Exit Strategy - Close positions after 5-15 minutes or on stop/target hit

Budget Enforcement

Multiple layers ensure you never exceed your limits:

  • Daily Volume Cap - Stops trading when daily notional limit is reached
  • Position Size Limits - Each trade is capped at configured max size
  • Leverage Limits - Maximum leverage enforced per risk level
  • Balance Checks - Verify sufficient collateral before each trade

Human-Like Patterns

The automation includes several techniques to avoid detection:

Randomization

  • Trade sizes vary randomly within bounds
  • Time between trades is randomized (8-20 min depending on risk)
  • Market rotation differs per wallet
  • Session timing has ±30 minute jitter

Natural Behavior

  • Not every trade is profitable (stop-losses hit naturally)
  • Sometimes positions are held longer due to market conditions
  • Occasional "mistakes" (slightly off entry/exit prices)
  • Session breaks mimic meal times and sleep

Exchange Integration

Pacifica.fi

  • Connection: Direct account linking via OAuth
  • Execution: WebSocket for real-time order updates
  • Settlement: Instant on-chain Solana transactions
  • Points: Tracked via Pacifica's API

Lighter.xyz (Coming Soon)

  • Connection: API key authentication
  • Execution: REST API for order placement
  • Settlement: Ethereum L2 (Arbitrum)
  • Points: Tracked via Lighter's dashboard

Monitoring & Logging

Every action is logged for transparency and debugging:

  • Execution Logs - Every trade attempt, success, and failure
  • Balance Tracking - Real-time collateral and PnL updates
  • Error Handling - Automatic retries with exponential backoff
  • Audit Trail - Complete history of all automation decisions

IP Diversity

Each wallet routes through unique proxy IPs to enhance privacy:

  • Residential proxies from diverse geographic locations
  • Sticky sessions (same IP per wallet for session duration)
  • IP rotation between sessions
  • No shared IPs between different wallets

Open Source?

While the frontend is closed-source to protect automation strategies, we're committed to transparency. We may open-source certain components (like exchange connectors) if there's community interest.