// the find
jito-foundation/jito-solana
Jito Foundation MEV Solana Client
A fork of the Solana validator client that adds MEV infrastructure — specifically block engine integration, bundle processing, and tip distribution. It's for validators who want to participate in Jito's MEV auction system and capture tip revenue rather than leaving it on the table.
The bundle processing pipeline is a real engineering addition on top of upstream Agave, not just config tweaks — it handles packet scheduling changes needed to guarantee bundle atomicity. XDP transmit support (with zero-copy mode) is a meaningful latency improvement that upstream doesn't have. The CI setup is thorough: Buildkite pipelines, nextest, coverage scripts, and frozen ABI tests mean regressions in consensus-critical code get caught. The release process is documented and they track divergence from upstream Agave systematically, which matters for a fork that has to stay current with a fast-moving base.
The README punts almost everything to a Gitbook — you can't understand the MEV-specific architecture without leaving the repo, which is a red flag for a security-sensitive validator. The fork lag from upstream Agave is a real operational risk: mainnet validators running this are always one missed merge away from a consensus bug or missed feature gate. There's no clear documentation on how tip distribution actually works or what the trust assumptions are with the block engine — operators are taking that on faith. The 733-star count relative to the operational footprint suggests most validators running this aren't reading the code, which is uncomfortable for infrastructure that handles economic value.