sendBundle: Jito bundles on Solana, private forwarders on Ethereum

Last updated: November 1, 2026

Why bundles

A bundle is an ordered group of transactions that is atomic if it lands— all or nothing, in sequence, invisible to frontrunners until inclusion. That is not a guarantee of inclusion.

On Solana the bundle enters a Jito block-engine auction with tip accounts, and the block engine decides whether it makes the block; on Ethereum it goes to a private forwarder that bypasses the public mempool and may simply not include it. Normally each rail needs its own integration, endpoints and auth. Through Triport both are one JSON-RPC call away.

Submit a bundle

curl https://triport.io/sol \
  -X POST -H 'Content-Type: application/json' \
  -H "x-token: $TRIPORT_API_KEY" \
  -d '{"jsonrpc":"2.0","id":1,"method":"sendBundle","params":[["<base64-tx-1>","<base64-tx-2>"]]}'
# the response carries the relay's bundle id — a receipt for an accepted
# submission, not an on-chain result. Verify the outcome afterwards.
# Ethereum: eth_sendBundle is not accepted on https://triport.io/eth.
# POST it to https://triport.io/rpc/eth-private/<forwarder-id> instead.

Jito's rules your bundle must meet

The block engine applies these, not Triport, so check them against Jito's documentation (read 2026-11-01) before you build around them.

• Size: a maximum of 5 transactions.
• Tip: Jito states a minimum of 1,000 lamports for bundles, and warns that this may not be enough in busy periods. With bundles, only the tip counts: see what a tip buys compared with a priority fee.
• Where the tip goes: in the same transaction as your strategy, so it is not paid if the work fails. Jito warns that a standalone tip transaction adds exposure to uncle bandit scenarios.
• Tip account: keep it out of address lookup tables.
• Encoding: base64 strings. Jito marks base58 as slow and deprecated.

Check whether it landed

The response is a receipt, so verify by signature. Call getTransaction or getSignatureStatuses for the signatures in your bundle. Jito's bundle status methods, such as getBundleStatuses, are not in our method catalog, so do not build on them through Triport. Because a bundle is atomic, one transaction landing means all of them did.

Dry-run first with simulateBundle: it is on the same endpoint from Pro, and catches reverts before you spend your send budget.

When a bundle is the wrong tool

A single transaction does not need a bundle. Use sendTransaction, which is on every plan and has a direct lane and parallel paths. Bundles earn their cost when transactions depend on each other, or must not be separated. If your account is on Free or Basic, sendBundle answers 403 tier_insufficient.

Pairs well with

Bundle strategies are timing games: the Shred stream shows order flow before execution, so your bundle is built on a recent picture of the chain.