From intake to memory without leaving the same operating shell.
- Launch filters trigger without waiting on an LLM
- Strategic model feedback updates every 10 seconds
- Execution routes through Jupiter, pump.fun, and Jito lanes
RUNTIME
Two decision engines, one execution shell, hard walls around automation.
WhiteOwl separates immediate launch-time filtering from slower strategic control. Fast Path hits the first decision window. Smart Path re-evaluates posture, exits, thresholds, and blacklists on a continuing loop.
First-pass decisioning for launch-time asymmetry.
Commander loop recalibrates thresholds and posture.
Jupiter, bonding curve, and Jito bundle routing.
Trades, patterns, outcomes, positions, and learning state.
DUAL ENGINE
Fast Path acts first. Smart Path decides what should keep happening next.
Fast Path
The launch filter chain is built for speed. It checks scam patterns, naming signal, quick score, dev behavior, holder structure, and entry conditions before broader strategic context even finishes loading.
- Sub-200ms target envelope
- No LLM dependency for first-pass filtering
- Built around launch curves and memecoin timing pressure
Smart Path
The Commander layer watches market state, trade posture, risk, and learning memory on a recurring loop. It can tighten thresholds, push exits, blacklist bad actors, and alter portfolio stance without turning the system into a blind script.
- Strategic feedback every 10 seconds
- Portfolio-wide threshold and exit pressure management
- Adaptive posture instead of static rule sets
STACK
Intelligence, execution, and safety are separate layers by design.
Intelligence stack
Read the market from contract shape to narrative pressure.
- Composite token scoring with on-chain and social context
- Cluster checks, holder spread, dev wallet reputation, clone detection
- InsightX and GMGN enrichment with RPC fallback
- Trend and velocity context via market activity feeds
Execution stack
Move through the best route the market still allows.
- Jupiter v6, pump.fun curve, and Jito bundle lanes
- DCA, grid, trailing stop, scaling, and graduation sniping modes
- MEV-aware configuration and route posture
- Exit optimizer watches time decay, reversal, and holder exodus
Safety stack
Automation never outruns operator-defined walls.
- Limits on size, exposure, loss, and emergency stopping
- Wallet simulation and AI-assisted drainer inspection
- Replayable local SQLite state for positions and outcomes
- Health, metrics, and alert surfaces across web and Telegram
ARCHITECTURE
One runtime, multiple routes, isolated responsibilities.
Inputs
pump.fun, socials, dashboard, extension, Telegram, API
Runtime
Scanner, Risk, Sentiment, Commander
Skills
token-analyzer, advanced-trader, exit-optimizer, insightx, social-monitor
Execution
Jupiter, pump.fun curve, Jito, vault wallet flow
Memory
SQLite tables for tokens, trades, positions, learning, outcomes
NEXT
See how the runtime surfaces out into the dashboard, extension, Telegram, and API.
The engine is only half the story. Operator entry points determine how fast the system can actually be used.