Atomic bundles on Solana

A bundle is a group of signed transactions that execute together and in order, or not at all. Bundles let you place a transaction right behind another one, which is the basis of backrunning, and they protect you from a strategy that runs only halfway.

Why use a bundle

• Order. Your backrun runs right after its target, never before it.
• Atomicity. If one transaction in the bundle fails, none of them land.

Without a bundle, two transactions sent one after the other can land in any order, in different slots, or one without the other.

Bundles through Jito

• You send the bundle to Jito's block engine, which runs an auction among bundles that touch the same accounts. The bundle with the highest tip per compute unit wins.
• One of the transactions must pay the tip: a SOL transfer to one of Jito's tip accounts.
• A bundle holds up to five transactions and lands only in the slots of leaders running Jito's validator client.

Bundles through Private TPU Send

• Private TPU Send delivers the bundle straight to the TPU of validators in our network, and it lands in their leader slots, executed as a whole and in order, or not at all.
• It does not go through Jito's auction, so it does not need a Jito tip.
• The typical use is a backrun: the target transaction from the Private Orderflow stream first, your transaction right after it.
• The method and format for submitting bundles come with your access details from our support.

The target also reaches the leader on its own, because our relayer never holds it. If the leader executes the target before your bundle arrives, the bundle fails as a whole. Build and send it as early as you can.

Side by side

You can also combine both: use Private Orderflow as the signal and submit through Jito, BAM or Harmonic under their own rules. Whichever path you choose, confirm the outcome through your RPC or Shreds.

Next steps

• How to backrun a transaction on Solana
• Placing your backrun
• What is SWQoS on Solana