The Solana route imbalance, explained

A focused breakdown of the route imbalance strategy, what it triggers on, and where the gates apply.

what is the route imbalance?

The route imbalance is one of the strategies the MicroEdge scanner runs against every observation in real time. Different markets and conditions favor different strategies — running all of them in parallel surfaces opportunities that any single strategy would miss.

when does it fire?

The route imbalance requires multiple supporting signals to align. False positives are expensive; missing real opportunities is forgivable. The gate is set such that ≥70% of raw firings get rejected before reaching subscribers.

code-level breakdown

// observation → score → reject → classify → alert
const score = routeimbalanceScore(obs, baseline);
const rej = evaluateRejections({ obs, ageMs, baselinePriceChange1m, ... });
if (isHardRejected(rej)) return null;
if (!costDominancePasses(strategy, score, size)) return null;
if (!payoffViabilityPasses(strategy, tp, sl)) return null;
return { classification: classify(score), suggestedSize: sizeFor(...) };

common edge cases

• Liquidity drops while the pattern fires — gate refuses
• Move already vertical when detected — late-chase penalty drops score
• Fake volume from wash trading — unique buyer floor refuses
• Pool too new (<5 min old) — new-pool age filter refuses
• Cost-dominance fail at $1 trade size — refuses regardless of score

live signal feed

The last 24 hours of fired alerts (across all strategies) is public at /signals.html. route imbalance alerts will be tagged by strategy in that feed.