Jupiter announced Metis V8 on May 20, 2026, through its official X post, “Metis V8: Solving The QE Drift”. The update was described as a new version of Jupiter’s Metis routing engine, focused on reducing Quotation-Execution Drift, the gap between the price shown at quote time and the final execution received by the user. A Reddit repost by Jupiter co-founder Meow repeated the same announcement and linked back to the official Jupiter post.
Metis V8 targets quotation-execution drift
Jupiter said Metis V8 addresses QE Drift through four areas: slippage penalties, JIT on-chain finalization, sub-2-slot latency and Rapid Quotation Mode. The slippage-penalty system is described by Jupiter as a mechanism that tracks historical execution slippage by market and penalizes AMMs that quote tightly but fail to deliver similar execution. That is Jupiter’s routing claim; the public material reviewed does not include third-party execution benchmarks showing user-level improvement after launch.
Metis V8: Solving The QE Drift
Metis, the top router in DeFi with more than $2T+ in lifetime volume, has always been focused on the hardest problems in routing. And these days, it is not just about finding the best quote, it is about making sure what lands is as close to the… pic.twitter.com/sTYi867DUx
— Jupiter (@JupiterExchange) May 20, 2026
The second and third changes are execution-design and infrastructure claims. Jupiter said V8 carries multiple route candidates into execution and finalizes splits on-chain at the last possible moment, rather than locking the route earlier. Jupiter also said gRPC streaming, validator shreds and its Beam transaction infrastructure provide sub-2-slot state freshness and p95 0-1 slot landing. These are Jupiter’s technical descriptions of the routing stack, not independently verified latency data in the reviewed material.
Rapid Quotation Mode is an optional mode, not the default description for all swaps. Jupiter framed it as a choice for users or integrators who prefer a quote in less than 100 milliseconds by skipping marginal optimization when fast landing is more important than extracting a few extra basis points. The core Metis V8 update is presented as live, while Rapid Quotation Mode is described as a selectable execution preference.
Jupiter documentation and confirmed functionality
Jupiter’s developer documentation identifies Metis as Jupiter’s on-chain routing engine for multi-hop and multi-split swaps across Solana DEXes. The Swap API documentation also separates two paths: the Meta-Aggregator, where routers such as Metis, JupiterZ, Dflow and OKX compete for best execution, and the Router path, where Metis is used directly and developers receive raw swap instructions with more transaction control.
The Metis technical documentation describes Metis as the “Solana Liquidity Engine,” with more than 60 liquidity venues and more than $2 trillion in routed volume. It also documents the self-hosted Metis API Binary, which requires a Binary Key, and states that access requires at least 10,000 JUP staked. These documents confirm the broader Metis integration and developer access model, but they do not independently document every V8-specific feature in the announcement.
The release comes as Solana dApps continue refining infrastructure to manage congestion and state contention. Jupiter’s focus on backend routing efficiency reflects a broader push to stabilize DeFi execution, similar to other protocol-level efforts such as Polygon’s scheduled Giugliano hardfork to address fee-data and block-propagation issues.
The confirmed status is narrow: Jupiter launched Metis V8 on May 20, 2026, and says the release introduces routing changes designed to reduce quotation-execution drift. The update includes active routing changes around slippage penalties, JIT on-chain finalization and latency infrastructure, while Rapid Quotation Mode is presented as an optional mode for speed-sensitive quoting. Claims about better user outcomes remain Jupiter’s stated objective unless supported by post-launch execution data, slippage studies or third-party benchmarks.