Documentation

Send a bundle

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

// updated 2026-11-17

NOTE

Supanode issues keys through Telegram. 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.

Build one to four signed transactions in execution order, with a distinct first signature for every member. Check each member's size limit, then submit through sendBundle, raw HTTP or QUIC.

Bundles use block engine routes. 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.

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 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:

EngineMinimum tip
Jito1,000 lamports
Jito BAM1,000 lamports
Harmonic10,000 lamports
Everstake1 lamport
GBX5,000 lamports

Tips from 1 to 999 lamports meet Everstake's engine minimum. Your key may require more; missing_tip.minimum reports the minimum that applies.

Add a tip

Add one or more System transfers to the Supanode tip accounts. Qualifying transfers across all members add together. If enabled for your key, you can instead set one declared tip for the whole bundle.

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

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 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. Use its index and problem fields to correct the affected member. A repeated member signature returns malformed with problem: duplicate_signature.

Rates and preflight

Bundles have their own rate for your key at each metro, separate from its transaction 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 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 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.

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 and the sendBundle reference.