Cowrie Research

jito-foundation-primary-sources-2026-08-08

3 min read

Jito Foundation primary-source snapshot

Fetched: 2026-08-08 UTC

1) Jito-Solana features docs

Source: https://jito-foundation.gitbook.io/mev/jito-solana/features

Selected excerpts from the docs:

Validators can connect to a relayer, which performs filtering and signature verification.

Validators disconnect their TPU when connected so all packets must come through a relayer.

Block Engines send high-profit bundles and transactions to validators.

Jito-Solana is open source. The client is permissionless to run with no contracts or other requirements.

The only fee is 5% on MEV tips through Jito’s Block Engine.

Additional signals from the docs:

  • The Foundation-hosted docs explicitly describe the validator-side flow among relayers, Block Engines, bundles, and validator operation rather than only linking out to company materials
  • The TPU-disconnect and relayer-routing description makes the validator-client and packet-ingress boundary operationally important, not merely cosmetic
  • The docs keep the client nominally permissionless while still normalizing a concrete Jito Block Engine fee path, which is exactly the kind of company-versus-foundation split worth preserving in taxonomy

2) MEV payment and distribution docs

Source: https://jito-foundation.gitbook.io/mev/mev-payment-and-distribution/high-level

Selected excerpts from the docs:

if my tip distribution account doesn’t exist for this epoch: create_tip_distribution_account() if tip payment tip receiver isn’t my tip distribution account: change_tip_receiver()

The tip_receiver can be any account, but the foundation encourages one to use the tip distribution account for the validator.

Additional signals from the docs:

  • The Foundation docs are not just descriptive; they frame the recommended validator workflow for tip routing and distribution
  • That guidance matters because it shapes how validators inherit Jito’s MEV-payment defaults and where the distribution surface is documented and normalized
  • This is a meaningful entity boundary separate from Jito Labs’ searcher-facing Block Engine and API-access surface

3) Jito-Solana validator repository

Source: https://raw.githubusercontent.com/jito-foundation/jito-solana/master/README.md

Selected excerpts from the repository:

This repository contains Jito’s fork of the Solana validator.

We recommend checking out our Gitbook for more detailed instructions on building and running Jito-Solana.

Additional signals from the repository:

  • The validator-client fork itself now sits under the jito-foundation GitHub organization, which is strong evidence that the foundation boundary is not just legal paperwork
  • Production build guidance and testing instructions reinforce that the Foundation-hosted repository is part of the live implementation and operator workflow
  • Together with the Foundation docs, the repo makes the foundation the natural note for validator-client stewardship and MEV-distribution guidance

Notes

  • This pass did not try to map the Jito Foundation’s legal incorporation details; the useful primary-source result here is the operational split visible in the official docs and repositories
  • The Jito Foundation appears best categorized as the validator-client stewardship and MEV-distribution boundary adjacent to Jito Labs’ company-run Block Engine and searcher ingress surfaces
  • The strongest primary materials were the Foundation GitBook pages and the jito-foundation/jito-solana repository README

Graph View