# Routing

> Choose submissions for leader delivery or block engine delivery and understand transaction privacy

Routes at hosted SWQoS edges can change, under the applicable service terms. A response does not identify which path was used.

<span id="leaders" />

## Leader delivery

SWQoS forwards each accepted transaction to upcoming leaders over stake-weighted QUIC. The signed transaction bytes are unchanged.

<span id="engines" />

## Block engine delivery

SWQoS may also submit a transaction to the leader's block engine, which can include placing it in a bundle with a Supanode transaction. Block engine routes include Jito, Harmonic, Everstake, GBX and Jito BAM. Availability depends on upcoming leaders and route configuration. Contact Supanode for the applicable service terms.

Submission does not mean an engine will accept the bundle or that any transaction will land. Confirm the signature through your [Solana RPC provider](https://supanode.xyz/docs/solana/sender/confirmation#confirmation).

<span id="bundles" />

## Explicit bundles

Use `sendBundle` when your application needs to submit one to four transactions in execution order. It goes to block engines only and has no direct leader route. Supanode may add its own transaction to the bundle. See [Bundles](https://supanode.xyz/docs/solana/sender/bundles) for tips and control accounts.

If no block engine can take the bundle right now, the request returns [`not_ready`](https://supanode.xyz/docs/solana/sender/reference/errors#not_ready) with `waiting_for: block_engine`. Do not submit members separately if they must execute together.

<span id="preflight" />

## Preflight and resubmission

Preflight is off by default. When requested, simulation runs on Supanode's RPC infrastructure provider before dispatch. See [preflight options](https://supanode.xyz/docs/solana/sender/send#preflight) and [service terms](https://supanode.xyz/legal).

SWQoS does not resend accepted transactions or bundles. A recently repeated single transaction signature may be accepted without being sent again. Do not rely on this as global idempotency; explicit bundle resubmissions are not suppressed. Your application owns [confirmation and later resubmission](https://supanode.xyz/docs/solana/sender/confirmation).

<span id="privacy" />

## Transaction privacy

SWQoS has no mempool. Delivery is limited to validators scheduled for the next blocks and the block engines described above. Requested preflight also sends the transaction to the RPC infrastructure provider. Contact Supanode for the applicable service terms.
