On this page
The RealValidator Team Editorial team

Jito on Solana refers to three distinct components that stakers commonly conflate: the Jito client (a validator software fork), the Jito Block Engine (an off-chain MEV auction service), and the Jito Stake Pool (an on-chain stake distribution program that issues the jitoSOL liquid staking token). Each plays a different role in MEV economics; statements about "Jito" without qualifying which component is meant are ambiguous and frequently wrong.

MEV (maximal extractable value) on Solana is the value searchers extract by ordering or inserting transactions advantageously — primarily DEX arbitrage, liquidations, and sandwich opportunities. Jito Labs built the dominant infrastructure for capturing this value through priority bundles and distributing the resulting tips to validators and their stakers.

The three Jito components

1. Jito client (Jito-Solana)

The Jito client, also called Jito-Solana, is an Agave-derived validator software fork with MEV-aware block-building hooks. A validator running this client receives priority transaction bundles from the Jito Block Engine and includes them in its produced blocks during its leader slots. Running the Jito client is what makes a validator "MEV-enabled" — the client is software, not a service or an account.

As of epoch 971, approximately 85-90% of staked SOL runs the Jito client (per BlockEden and yellow.com Jito MEV explainer, May 2026). This share has declined from a peak above 90% as Frankendancer adoption has grown; Frankendancer currently runs ~26% of stake and is incompatible with the Jito client today.

2. Jito Block Engine

The Jito Block Engine is the off-chain MEV auction service Jito Labs operates. Searchers submit priority transaction bundles to the Block Engine alongside a tip payment; the Block Engine selects winning bundles via auction and routes them to the current leader validator running the Jito client. Tip payments flow from searchers through the Block Engine to validators, which then distribute the tips to stakers net of Jito MEV commission.

This is the service that produces the "Jito MEV rewards" cited alongside staking APY on Stakewiz. A validator must run the Jito client and be configured against the Block Engine to earn this revenue stream. A validator can opt out of MEV by disabling the Block Engine connection (and therefore earns 0 MEV income).

3. Jito Stake Pool

The Jito Stake Pool is Jito Foundation's on-chain stake distribution program; it issues the jitoSOL liquid staking token and distributes pooled SOL across selected validators based on its own scoring criteria (which include MEV performance, decentralization, and uptime). Jito Stake Pool is structurally similar to Marinade and SolBlaze — it is a stake pool protocol, not a service or a client.

Critically, the three components are independent:

  • A validator can be in the Jito Stake Pool without running the Jito client (rare, but possible — the pool can select validators based on broader criteria).
  • A validator can run the Jito client without ever receiving Jito Stake Pool delegation.
  • The Jito Block Engine serves all Jito-client validators, not only those in the Jito Stake Pool.

Tip distribution mechanics

A typical priority bundle flow at epoch 971:

  1. A searcher identifies an arbitrage opportunity, constructs a bundle of transactions, and submits it to the Jito Block Engine along with a tip (typically tens of thousands of lamports to multiple SOL, depending on the opportunity).
  2. The Block Engine auctions the bundle against competing bundles for the same leader slot. The winning bundle is forwarded to the current leader validator running the Jito client.
  3. The leader includes the bundle in its produced block. The tip is paid to the leader's tip-receiver account at block production.
  4. Across the epoch, accumulated tips are reduced by the validator's Jito MEV commission and the remainder is distributed pro-rata to that validator's stakers as part of the epoch reward distribution.

Gross MEV revenue at the network level was approximately 0.13% annualized at epoch 971 (per Stakewiz cluster_stats), but per-validator MEV income varies materially with leader-slot timing, network MEV activity at the time of those slots, and Block Engine bundle inclusion success. High-stake validators in MEV-busy time windows can earn substantially more.

MEV commission is separate from base commission

A validator advertises base commission and Jito MEV commission as two independent percentages. Both must be read together to understand realized staker yield. A 0% base / 100% Jito MEV operator passes all inflation rewards but retains all MEV. A 5% base / 8% Jito MEV operator passes 95% of inflation and 92% of MEV. Stakewiz exposes Jito MEV commission as jito_commission_bps (basis points); 800 = 8%.

Terminology traps

  • "Jito" alone is ambiguous. The styleguide forbids unqualified use. Specify Jito client (software), Jito Block Engine (auction service), or Jito Stake Pool (stake program).
  • "jitoSOL" is the LST issued by the Jito Stake Pool, not a Jito Block Engine product. Holding jitoSOL exposes the staker to the Jito Stake Pool's validator selection, not directly to Block Engine MEV income from all Jito-client validators.
  • "Jito MEV" income is realized via the Block Engine, not via the Jito Stake Pool. A staker delegated directly to a Jito-client validator earns the validator's Block Engine-routed MEV income; the Stake Pool is one of many delegation paths to such validators.
  • MEV revenue is not guaranteed. A validator running the Jito client during a low-activity epoch can earn near-zero MEV; the income stream is variable, not contractual.

Sources

Jito component shares cited reference Stakewiz and BlockEden cluster data at epoch 971, 2026-05-15. Client adoption shifts each epoch as Frankendancer continues to displace Jito-Solana on some operators; verify on a fresh snapshot when citing for current decisions.