Routing

This page describes routing at hosted SWQoS edges. Routes can change, as described in Terms 5.1. A response does not identify which path was used.

Leader deliveryCopy Anchor Link

The leader route writes a single transaction once to the TPUs of the leaders of the next 8 slots over stake-weighted QUIC. The edge forwards the signed transaction bytes unchanged.

A single transaction may also qualify for a block-engine copy. If it does not qualify, it uses leader delivery only.

Block-engine eligibilityCopy Anchor Link

The block-engine routes are Jito, Harmonic and Jito BAM. A single transaction also goes to an available engine for an upcoming leader only when the key's recent landing record qualifies and the transaction meets the following requirements:

• Its blockhash is recent, or it uses a durable nonce.
• Its tip meets the engine minimum as well as the key minimum.

The engine copy is a bundle with ZeroCopy's closing tip transaction appended after the customer's transaction. The closing transaction pays the engine out of the tips sent to ZeroCopy's tip accounts. When an upcoming leader runs Jito BAM, the edge sends the same Jito bundle directly to that leader's BAM node.

Eligibility does not mean an engine will accept the bundle or that any transaction will land. Confirm the signature through your Solana RPC provider.

Explicit bundlesCopy Anchor Link

sendBundle goes to block engines only; it has no direct leader route. It accepts one to four customer transactions in execution order, followed by ZeroCopy's closing tip transaction in the engine copy. See Send a bundle for tips, control accounts and bundle limits.

If no eligible engine is available, the request returns not_ready with waiting_for: block_engine. Do not submit members separately if they must execute together.

Preflight and resubmissionCopy Anchor Link

Preflight is off by default. When requested, simulation runs on ZeroCopy's RPC infrastructure provider before dispatch. See preflight options and Terms 5.2.

SWQoS does not resend accepted transactions or bundles. maxRetries is ignored. An edge suppresses repeated single-transaction signatures for about two seconds; this is not global idempotency and does not suppress explicit bundle resubmissions. Your application owns confirmation and later resubmission.

Transaction privacyCopy Anchor Link

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. See Terms 5.5.