Jito

• Name: Jito
• URL: https://docs.jito.wtf/
• Category: Solana transaction-delivery / low-latency data / MEV infrastructure
• Tags: solana-ecosystem
• Summary: Jito is Solana MEV and low-latency transaction infrastructure with a real operating surface: Block Engine routing, tip-based bundle auctions, shred streaming, and a validator-client fork. It is not just a faster RPC brand; it bundles transaction delivery, validator software, and MEV capture into one market structure.
• What it does:
  • Provides low-latency transaction submission endpoints for Solana users who care about fast landing, MEV protection, and revert protection
  • Supports atomic bundles of up to five transactions, with tip-based auctions and sequential all-or-nothing execution inside a slot
  • Operates Shredstream, a low-latency feed for Solana shreds intended to reduce data-delivery latency for RPCs, validators, and trading systems
  • Maintains Jito-Solana, a fork of the Solana/Agave validator client that connects validators into Jito’s Block Engine workflow
  • Publishes SDKs, protobufs, and searcher example repos that make the technical integration surface much more concrete than the marketing framing alone
• Key claims:
  • The docs home describes Jito as a “Turbocharged Solana trading experience” aimed at validators, Telegram bots, high-frequency traders/searchers, and dapps
  • The docs say Jito offers low-latency transaction sending, low-latency blockchain/shred data, and around-the-clock developer support
  • The low-latency transaction-send docs state that Jito provides superior Solana transaction execution through fast landing, MEV protection, and revert protection for both single transactions and bundles via gRPC and JSON-RPC services
  • The system overview explains that validators run Jito-Solana, connect to the Jito Block Engine, and receive profitable bundles, while searchers and apps connect to the Block Engine to submit transactions and bundles
  • The docs define bundles as up to five transactions executed sequentially and atomically, with tip bids competing in a priority auction that runs at 50ms ticks
  • The public GitHub org and repos show that Jito exposes real operator and developer surfaces, including searcher examples, TypeScript and Python SDKs, protobuf definitions, a shredstream proxy, and documentation sources
• Whitepaper: No classic standalone whitepaper or litepaper was found during this pass. The strongest primary materials were Jito’s docs portal plus the Jito-Labs and Jito Foundation repositories, which function as the real source of truth for the product and operator surface; see ../whitepapers/jito-primary-sources-2026-04-26.md.
• Sources:
  • https://docs.jito.wtf/
  • https://docs.jito.wtf/lowlatencytxnsend/
  • https://github.com/jito-labs
  • https://raw.githubusercontent.com/jito-labs/searcher-examples/master/README.md
  • https://raw.githubusercontent.com/jito-foundation/jito-solana/master/README.md
  • https://raw.githubusercontent.com/jito-labs/shredstream-proxy/master/README.md

Internal linkages

• Strongest cross-chain comparison: flashbots-auction.

• Validator-side topology contrast: mev-boost.

• Best sold ordering advantage contrast: timeboost.

• Last reviewed: 2026-06-02 UTC