Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Sending transactions

Send Solana transactions with sendTransaction, /sendtx or the Jet TPU client, with SWQoS, percentile priority fees, Shield MEV protection and trading APIs.

You build and sign a transaction, then submit it so a validator includes it in a block. Landing reliably under load comes down to a few things:

  • Direct delivery. Sending to the current and upcoming leaders from Triton's own sending infrastructure, separate from the RPC nodes that serve your reads.

  • Stake-weighted quality of service (SWQoS). Prioritizing your transactions for higher landing rates under congestion. On by default for mainnet sends at no extra cost, with nothing to request. Devnet sends are not staked.

  • Priority fees. Attaching a fee that reflects the real market rate without overpaying, on any send path.

  • Protection. Optionally restricting which validators can process your transaction, to avoid harmful MEV.

Pick your send path

Every sendTransaction and /sendtx request to a Triton mainnet endpoint is handled by Jet, Triton's SWQoS-powered specialized sending engine: it tracks the leader schedule and forwards your transaction directly to the TPUs of the current and upcoming leaders.

You can submit through two managed routes depending on your use case, or self-host the Jet TPU client for full client-side control.

  • sendTransaction is the standard Solana JSON-RPC method. We route it through Jet and apply SWQoS on mainnet.

  • /sendtx is a direct HTTP submission endpoint that takes the same delivery path as sendTransaction. It takes the transaction as a raw, base58, or base64 body and skips the JSON-RPC envelope, so there is no JSON to build or parse and the payload is smaller. A text/plain body with no custom headers also skips the browser CORS preflight. It needs no RPC client library.

  • Jet TPU client is the open-source Rust crate yellowstone-jet-tpu-client, which you embed in your own application for full client-side control. It sends your transactions straight to validator TPUs over QUIC, with a callback that reports whether each transaction was sent, failed, or dropped, custom destinations and blocklists, and Yellowstone Shield support behind the shield feature flag. It needs an RPC endpoint and a Yellowstone gRPC endpoint.

sendTransaction

/sendtx

Jet TPU client (self-hosted)

Use case

broad compatibility

browsers, HFT backends

bots, custom routers

Interface

Solana JSON-RPC

HTTP POST

Rust library

Ease of use

any Solana SDK

a single HTTP POST, no RPC library

you operate the client

Client to run

none

none

yes

Reaches the TPU via

your endpoint (server-side)

your endpoint (server-side)

your client (direct)

SWQoS by default on mainnet (no extra charge)

✓

✓

✗ (only if your own identity is staked)

skipPreflight option

✓

✗ (always skips preflight)

✗ (direct send, no preflight)

Shield policy

forwardingPolicies parameter

Solana-ForwardingPolicies header

shield feature flag

With skipPreflight: false (the default), Triton simulates the transaction before it forwards it. /sendtx always skips preflight.

Priority fees and protection

Trading APIs

What's next


Contact support by clicking the chat icon in your customer dashboard Sales questions? Contact us AI agent? Read llms.txt Follow updates: Blog · X · YouTube · Telegram · GitHub

Last updated