Annual Revenue Overview

Revenue Sources
Direct to validators
Other JITAnnual
outside protocol take
—
—
—
Total Gross RevenueAnnual
—
—
—
Raiku JIT (tips)Annual
—
—
—
AOT Revenue (auctions)Annual
—
—
—
Revenue Distribution
Direct to validators
Validator Other JIT
outside protocol take
—
—
—
Bypasses protocol take
Validator BaseAnnual
(Raiku JIT + AOT)
—
—
—
Raiku Protocol Take
— — —
Annual
Validator BonusAnnual
—
—
—
AOT RebateAnnual
—
—
—
Raiku JIT RebateAnnual
—
—
—
Growth + BuybackAnnual
—
—
—
Remaining TreasuryAnnual
—
—
—

Revenue Flow — Other JIT bypass + Raiku JIT + AOT → Distribution

Other JIT Revenue — bypass → Raiku JIT Revenue — AOT Revenue — Protocol Revenue — Validator Other JIT — Validator Base (Raiku JIT + AOT) — Validator Bonus — AOT Rebate — Raiku JIT Rebate — Growth + Buyback — Remaining Treasury — Total Validator Revenue — Raiku Protocol Revenue Distribution Raiku Protocol Take —

Scenario Comparison

Current Market

—

Last 12 Months

—

Last 24 Months + Congestion

—

Bull Case

—

AOT Protocol Treasury Sensitivity to Stake % and AOT Fees

AOT protocol treasury sensitivity under the current live assumptions. The chart highlights the nearest displayed stake bucket to the active setting, and the table highlights the nearest stake and fee/CU bucket intersection.
AOT-only view: this module isolates AOT protocol treasury, not total protocol revenue. Use the reconciliation line below to compare the current AOT component with JIT and total protocol revenue.
Current Scenario Context
Sensitivity Chart
Sensitivity Table

Data Sources & Methodology

JIT Market Assumption & Methodology
Active JIT market
— data-driven default
Annualized JIT tip market used as model input. Set by the active preset or the JIT Total Market slider.
Other non-Raiku JIT — treatment in this model
The total JIT market includes two distinct flows on covered stake:
• Raiku JIT — tips routed through Raiku's ordering protocol. Subject to protocol take rate, customer rebate, and treasury split.
• Other non-Raiku JIT — tips from competing ordering services (e.g. direct Jito bundles) that bypass Raiku protocol take entirely and flow straight to validators.

Other non-Raiku JIT is automatically derived as max(Raiku Stake % − Raiku JIT Market Share, 0). The logic: Raiku can only route JIT tips from validators it has stake on — so Raiku Stake % is a hard ceiling on JIT capture. Any portion of that covered stake not routed through Raiku's protocol flows directly to validators via competing ordering services (e.g. native Jito bundles). It is included in validator-side revenue but excluded from Raiku gross and protocol treasury. No double-counting is possible by construction.
Scenario mapping — preset → window → market size
Current Marketlast 15 epochs (~30 days), annualized Last 12 Months12-month window, annualized Last 24 Months + Congestion24-month window, annualized — includes higher-activity periods Bull Case5,000,000 SOL/yr — manual, not derived from historical windows
Window detail — anchored to —
Window Date range Epochs Observed (SOL) Avg/epoch Avg/CU
lam/CU · macro		 Days Annualized
~30 days
Current Market		 — — — — — — —
6 months
reference		 — — — — — — —
12 months
Last 12 Months		 — — — — — — —
24 months
Last 24 Months + Congestion		 — — — — — — —

Bull Case (5,000,000 SOL/yr) is a manual high-growth scenario and is not derived from these windows.

Source & methodology
Source Jito Foundation MEV rewards API — kobe.mainnet.jito.network Cross-check Trillium epoch API and Dune Analytics. Jito Foundation API closely matches Trillium epoch data at a 1.000× ratio across 135+ epochs. Dune Analytics reports 3–5% higher totals than Trillium, likely due to a broader fee aggregation scope. Metric Total network MEV tips per epoch (lamports → SOL) Dataset — epochs (epoch — → —) Method Sum tips over window → annualize: (total_sol / days) × 365.25 Includes MEV tip revenue through Jito's block engine, distributed to validators and stakers Excludes Native priority fees, other block engines, private relay channels, off-chain flows. True addressable market is likely larger.
MEV / JIT Rewards — Historical Trend
Full history from epoch —. The highlighted section shows the active preset window. Peaks reflect periods of high MEV activity (e.g., memecoin surges).
Inspect the raw epoch-by-epoch data behind this assumption
AOT Fee/CU Assumption & Methodology
Current Market 30d AOT scope data-driven framework
— lamports per CU
Blended average fee per compute unit across all AOT auction customers. Controlled by the Avg Auction Fee/CU slider in the left panel. This is the second of two core model assumptions (alongside JIT market size).
Metric Definitions
Non-base fee/CU = priority fee/CU + MEV / JIT fee/CU. Default analytical view.
Total fee/CU = base fee/CU + non-base fee/CU. Secondary comparison view.

Weighted mean is CU-weighted. p25 / median / p75 are unweighted program percentiles. Divergence indicates concentration or skew.

Scenario Assumptions (Fee/CU)

Current Market

—

—

Last 12 Months

—

—

Last 24 Months + Congestion

—

—

Bull Case

—

—

Normal Elevated Extreme
Model Constants & Setup
Slots/year (SY): 78,408,000 (~2.5 slots/sec × 86400 × 365.25)
CU/block (CB): 60,000,000 (Solana max compute units per block)
Lamports/SOL (LS): 1,000,000,000
SOL price default: Real average from last 36 epochs (~$109)
Protocol Take Rates: AOT and JIT each use their own slider (default 5%). Validator base = 1 – take rate for that stream. Rebates and validator bonus are funded from the corresponding protocol pool (= gross × stream take rate), never from gross revenue directly.
Two-waterfall model: AOT and JIT streams are calculated independently, then aggregated. Validator bonus applies only to AOT. If either take rate = 0%, redistributions on that stream are forced to 0.