Jupiter's Solana Order Path Reveals Complex Router Selection Dynamics

A recent seven-day probe of Jupiter's managed order path on Solana has revealed an interesting dynamic. The study measured selected-router incidence in a fixed production /order probe, not transaction volume, notional share, or landed fills. It found that while the large leave-one-out gaps sit in a few pair×size×state corners-not across the router layer as a whole-Jupiter's managed Meta-Aggregator /order path runs a selection layer containing Metis, JupiterZ, DFlow, and OKX.

The study also highlighted that who gets selected is not what matters most. Across successful all-router responses (A1 and A2 pooled; n = 2014), OKX was selected in 36.8% of tested intents, JupiterZ 31.7%, Metis 23.6%, DFlow 7.8%. Aggregate leave-one-out medians sit near that resolution: Metis and DFlow about 0 bps, OKX about 0.1, JupiterZ about 0.3.

The large exclude-JupiterZ effects are concentrated by pair. The AAPLX cell is the maximum of 24 pair×router medians; it was identified post hoc. The 21.5 bp AAPLX median sits far above its 0.05 bp local drift median-roughly six times the pair-specific P95 full-bracket drift (3.39 bps).

The study found that hard coverage and replacement quality are different objects. Among stable sets where JupiterZ won A1, Metis and OKX fallbacks typically preserve the all-router reference.