# Send a bundle

> Submit one to four signed transactions in order with tips and bundle controls

<Note>
Supanode issues keys through [Telegram](https://telegram.me/supanode_tgs). Default minimum tip: 0.001 SOL; default rate: 15 sends/s per key per metro. Your key settings can differ. Declared tips are off by default and require enablement and a payment arrangement with Supanode. If your key returns `partner_declared_tips`, use an on-chain transfer instead.
</Note>

Build one to four signed transactions in execution order, with a distinct first signature for every member. Check each member's [size limit](https://supanode.xyz/docs/solana/sender/limits#sizes), then submit through [`sendBundle`](https://supanode.xyz/docs/solana/sender/reference/json-rpc/send-bundle), [raw HTTP](https://supanode.xyz/docs/solana/sender/reference/http) or [QUIC](https://supanode.xyz/docs/solana/sender/reference/quic).

Bundles use [block engine routes](https://supanode.xyz/docs/solana/sender/routing#bundles). Do not send members independently if your application requires ordered execution where all members succeed or none execute: a separately submitted transaction can land outside the bundle.

<span id="engine-eligibility" />

## Engine availability

SWQoS supports Jito, Harmonic, Everstake, GBX and Jito BAM routes. Availability depends on upcoming leaders and route configuration. 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`. Wait and retry without changing the signed transactions while their lifetimes remain valid.

Your tip must meet both your key's minimum and the available engine's minimum:

| Engine | Minimum tip |
| --- | --- |
| Jito | 1,000 lamports |
| Jito BAM | 1,000 lamports |
| Harmonic | 10,000 lamports |
| Everstake | 1 lamport |
| GBX | 5,000 lamports |

Tips from 1 to 999 lamports meet Everstake's engine minimum. Your key may require more; [`missing_tip.minimum`](https://supanode.xyz/docs/solana/sender/reference/errors#missing_tip) reports the minimum that applies.

<span id="tips" />

## Add a tip

Add one or more System transfers to the [Supanode tip accounts](https://supanode.xyz/docs/solana/sender/tips#tip-accounts). Qualifying transfers across all members add together. If enabled for your key, you can instead set one [declared tip](https://supanode.xyz/docs/solana/sender/tips#declared-tips) for the whole bundle.

The full covered tip goes to the engine. Supanode pays the closing transaction's 5,000-lamport base fee separately.

<span id="control-accounts" />

## Use bundle controls

If a transaction carries a recognized `jitodontfront`, `dontfront` or `dontbund1e` control, put it first. At most one member may carry controls. With `dontbund1e`, later members may call only the System, Compute Budget and Memo programs.

See [`sendBundle`](https://supanode.xyz/docs/solana/sender/reference/json-rpc/send-bundle) for exact control account recognition rules. Controls can narrow which engines can take the bundle and raise the minimum tip. SWQoS checks them at admission only; they do not govern transactions submitted outside your bundle.

A control violation returns [`bundle_control`](https://supanode.xyz/docs/solana/sender/reference/errors#bundle_control). Use its `index` and `problem` fields to correct the affected member. A repeated member signature returns [`malformed`](https://supanode.xyz/docs/solana/sender/reference/errors#malformed) with `problem: duplicate_signature`.

<span id="rates" />

## Rates and preflight

Bundles have their own rate for your key at each metro, separate from its transaction [send rate](https://supanode.xyz/docs/solana/sender/limits#send-rate). The rate adjusts automatically between 1 and 20 bundles per second. A fixed rate configured for your key takes precedence.

For [`rate_limited`](https://supanode.xyz/docs/solana/sender/reference/errors#rate_limited) with `limit: bundles`, wait for `retry_after_ms` when supplied. A refusal without `per_second` or `retry_after_ms` means the edge cannot take another bundle at that moment. If bundles are turned off for your key, the request returns [`unsupported`](https://supanode.xyz/docs/solana/sender/reference/errors#unsupported) with `feature: bundles`.

Bundles are not simulated before sending. `skipPreflight: false` does not enable simulation; `sendBundle` reads only its `encoding` and `tip` options. Validate members with your own Solana RPC when your flow needs simulation.

<span id="bundle-id" />

## Bundle id and outcome

Keep the returned bundle id with the members' signatures. The id identifies the signed members and their order. It is neither a landing outcome nor a block engine's status id. Repeating the same bundle returns the same id but can submit it again.

Confirm every member's signature through your Solana RPC provider. SWQoS has no bundle status method. See [Confirmation](https://supanode.xyz/docs/solana/sender/confirmation) and the [`sendBundle` reference](https://supanode.xyz/docs/solana/sender/reference/json-rpc/send-bundle).
