How warp-id/solana-trading-bot works
Project type and purpose
• This is a single-process, full-stack automation tool—a Solana Trading Bot—that connects to the Solana network via HTTP/WebSocket RPCs (and optionally third-party services like Jito or Warp) to monitor on-chain market events, apply filters/strategies, and execute buy/sell transactions automatically.
File structure
• Top-level entrypoints:
• bot.ts / index.ts – bootstraps the bot, loads config, starts listeners
• Configuration:
• .env-based config loader via helpers/constants.ts
• Modules:
• cache/ – in-memory caches for markets, pools, snipe-lists
• filters/ – individual pool or token filters (burned, mutable, renounced, pool size, etc.)
• helpers/ – RPC wrappers, logging, wallet operations, common constants
• listeners/ – WebSocket subscriptions for new pools or market events
• transactions/ – TransactionExecutor interface + implementations (default RPC, Jito, Warp)
• Other assets:
• snipe-list.txt – optional static watchlist of mint addresses
• readme assets for CLI output
Key insights from README
• Configurable parameters for wallet, RPC endpoints (HTTP & WS), logging, caching, filtering thresholds, buy/sell strategies, slippage, retry logic, and transaction executor choice (default/Jito/Warp).
• Emphasis on real-time WebSocket listeners + filters pipeline + strategy module + pluggable transaction executors.
Components
a. Main components
1. Configuration Loader (reads .env into Constants)
2. Bot Engine (orchestrator)
3. Market Listener (Solana WS)
4. Cache Manager (market.cache, pool.cache, snipe-list.cache)
5. Filter Pipeline (chain of pool/token filters)
6. Snipe List Service (optional watchlist loader)
7. Transaction Executor (Strategy pattern):
– Default RPC executor
– Jito RPC executor
– Warp API executor
8. Helpers & Logger (shared utilities)
9. External Services:
– Solana HTTP RPC endpoint
– Solana WebSocket RPC endpoint
– Jito RPC endpoint
– Warp transactions API
b. Relationships & data flows
• On startup: Config Loader → Bot Engine
• Bot Engine → initializes Market Listener → subscribes to new pool events via Solana WS
• Incoming events → Cache Manager updates caches → Event passed to Filter Pipeline
• Filter Pipeline → if passes N filters → Bot Engine enqueues buy/sell job
• Bot Engine → calls Transaction Executor (selected at runtime)
• Transaction Executor → serializes & sends transaction via Solana HTTP RPC or 3rd-party endpoint
• Helpers/Logger used throughout for retries, fee calculations, error handling
c. Architectural patterns & principles
• Observer pattern – listeners subscribe to on-chain events via WebSocket
• Strategy pattern – interchangeable TransactionExecutor implementations
• Chain-of-responsibility – sequential filters in filters/
• Single responsibility – clear separation: caching, filtering, listening, executing
d. Key technologies & frameworks
• TypeScript + Node.js runtime
• Solana Web3.js (under helpers)
• HTTP & WebSocket RPC protocols
• Optional third-party services: Jito RPC, Warp API
Detail
• Filter modules by name or group them under “Filter Pipeline.”
• TransactionExecutor implementation branching off the interface.
• Snipe List refresh path: Timer → SnipeList Service → Cache Manager.