Copy trading & automation

Jito Block Engine

by Jito Labs

A Solana transaction submission and blockspace auction service used by traders and application developers. It accepts signed transactions and ordered bundles, forwards them toward validators and provides bundle status query methods.

Type
Solana transaction submission and bundle auction infrastructure
Chains
Solana
Platforms
JSON-RPC and gRPC interfaces
Custody
Client-signed transactions; no asset custody
Access
Block Engine endpoints; allowlisting for Direct Bundle Ingest

What Jito Block Engine does

Jito Block Engine is a Solana transaction submission service that accepts signed transactions and ordered bundles through developer-facing endpoints. A bundle groups up to five signed transactions for sequential, atomic processing within a slot, subject to inclusion through the bundle route. Searchers submit transactions through JSON-RPC or gRPC, while the Block Engine coordinates bundle auctions and forwarding toward validators. Its API provides submission identifiers and methods for checking pending and landed bundle status.

Builders use Jito for multi-transaction strategies such as atomic arbitrage, where transactions depend on one another. Unlike ordinary single-transaction submission, bundles compete for blockspace through tip-based auctions, and successful submission does not establish on-chain inclusion. The single-transaction endpoint skips RPC preflight simulation, leaving validation to the submitting application. Jito also documents a separate, allowlisted Direct Bundle Ingest route to BAM nodes. Uncled-block rebroadcasts can bypass bundle atomicity when individual transactions are replayed outside their original bundle.

Best for: Builders who need Solana bundle submission, ordered transaction execution, and programmatic status monitoring for multi-transaction strategies.

Strengths

  • Bundles support sequential, atomic processing of up to five signed Solana transactions.
  • JSON-RPC and gRPC interfaces support integration into trading applications and transaction submission systems.
  • Bundle status methods let applications distinguish pending, failed, and landed submissions.

Limitations

  • The service operates on Solana rather than supporting transactions across unrelated blockchain networks.
  • The single-transaction endpoint skips preflight simulation, and uncled-block rebroadcasts can bypass normal bundle atomicity.
  • Bundle inclusion depends on auction selection, while Direct Bundle Ingest requires separate authorization and serves BAM leaders only.

Where we compare Jito Block Engine

  • MEV Protection and Execution Tools Compared

    Jito supports atomic Solana transaction bundles, tip-based blockspace auctions, and submission status queries, with distinct requirements for Block Engine and Direct Bundle Ingest.

Alternatives to Jito Block Engine

Jito Block Engine questions

Are Jito Block Engine bundles atomic?

Jito processes bundles of up to five transactions sequentially, committing the complete bundle or rejecting it when executed through the bundle mechanism. Its documentation notes that uncled-block rebroadcasts can cause individual transactions to execute outside those atomicity rules.

How does Jito Block Engine differ from Direct Bundle Ingest?

Block Engine accepts bundles for routing toward BAM and non-BAM leaders, with auction handling dependent on authorization. Direct Bundle Ingest requires separate allowlisting and submits directly to BAM nodes, which conduct their own bundle auctions.

Details checked November 16, 2026. Features, chains and availability change, so confirm on the official site before you sign up or trade. Browse all tools.