Documentation

Solana TPU Sender

Send signed Solana transactions through parallel channels with SWQoS. Get your API key from Supanode on Telegram. Transaction tips, no monthly subscription.

// updated 2026-10-23

The Solana TPU Sender forwards signed transactions through multiple delivery channels. These include staked TPU connections to current and upcoming validator leaders using Stake-Weighted Quality of Service (SWQoS).

Request your API key from Supanode on Telegram. We provide your key and connection details. There is no monthly subscription. Request a free trial up to 24 hours from Supanode on Telegram; our team confirms availability and setup. Each transaction must include a sufficient tip; Solana network fees also apply.

Client access and TPU delivery

The client connects to TPU Sender using HTTP JSON-RPC or the separately authorized QUIK transport on port 8090. The connection guide uses the spelling QUIK. Request the endpoint and transport-specific setup from Supanode.

Client access and validator delivery are separate parts of the route. Staked TPU connections with SWQoS carry transactions from the sender to validator leaders.

Submission flow

Your application signs a transaction with a tip
  -> HTTP JSON-RPC / authorized QUIK endpoint
  -> TPU Sender parallel delivery channels
  -> staked TPU connections with SWQoS
  -> current and upcoming validator leaders

SWQoS improves access to stake-backed validator connections. It does not guarantee inclusion, ordering, execution success or a particular landing slot.

NOTE

A returned signature means the transaction was submitted. Check confirmation and execution separately with your regular Solana RPC.

Get started
Request a key and prepare your integration.
Sending transactions
Headers, JSON-RPC requests and error handling.
Tips and limits
Tip accounts, fees and request limits.
Endpoints
HTTPS and regional connection details.