Skip to content

Solana TPU Sender.

Deliver signed Solana transactions through parallel channels.

[ REQUEST KEY ]Explore delivery

A send path for your application.

For trading systems and DeFi applications that already build and sign Solana transactions. TPU Sender forwards signed transactions through parallel delivery channels, including staked TPU connections with SWQoS to current and upcoming validator leaders.

Keep your regular RPC for blockhashes, reads, simulation and confirmation.

One request. Parallel delivery.

Your application handles the transaction and signature. TPU Sender handles forwarding through multiple delivery channels. SWQoS provides stake-backed access to validator connections.

Your application

Build, add tip, sign locally.
Submit over HTTP JSON-RPC or authorized QUIK.

TPU Sender

Validate the request.
Forward through parallel delivery channels.

Staked TPU + SWQoSCurrent and upcoming leaders
Other enabled channelsParallel forwarding paths
Validators

Delivery architecture: your client connects to TPU Sender, which forwards to validators.

Submission
A signature returned by sendTransaction means the request was submitted.

Confirmation
Check confirmationStatus and err on your regular Solana RPC.

Client connections and limits.

HTTP JSON-RPC works with a signed base64 transaction and an API key. QUIK has its own authorization and setup.

Scroll the table horizontally for connection details.

Documented client access
HTTP JSON-RPCsendTransaction
Bearer API key or X-Api-Key header
QUIKPort 8090
Separate public-key authorization. Keep your private key local.
RegionsAmsterdam, Frankfurt, Washington DC
Connection detailsSupanode provides the key, endpoint and transport-specific setup.

View endpoints and authorization

Choose HTTP JSON-RPC or request QUIK authorization for your client connection.

Price & access.

Solana

TPU Sender

Optional · transaction delivery

Forward signed transactions through parallel delivery channels, including staked TPU connections with SWQoS. Use your RPC for reads, simulation, network confirmation and execution status.

  • 50 requests/s per client profile by default
  • Plus Solana network fees
  • No monthly subscription · trial on request
0.00015 SOL
minimum tip / transaction

API key requested through Supanode on Telegram. Ask our team about a free trial up to 24h; availability and setup are confirmed separately.

[ REQUEST KEY ]Documentation

Add the tip before signing. Solana base fees and any priority fee are additional.

AccessPrivate · Supanode keyPublic route
Minimum tip / transaction0.00015 SOL150,000 lamports0.0002 SOL200,000 lamports
Default request limit50 requests/sPer client profile. Shared across its clients.1 request/sPer source IP.
AuthenticationAPI key + tipTip, no API key
RouteIssued endpoint/public · sendTransaction only
StartRequest key from SupanodeRead public access details

Both paths use paid tip-based access. QUIK authorization and applicable limits are arranged separately with Supanode.

The tip is an on-chain transfer within your signed transaction. If the same transaction lands through another provider, its embedded tip still belongs to that transaction. Accepted accounts and fee handling

Connect, send and confirm.

Add a System Program transfer to an accepted tip account. Sign locally and serialize to base64, then submit to the endpoint issued with your key.

The API key authenticates the request. Keep it on your server.

Illustrative HTTP request. Replace placeholders with your connection details and signed transaction.

Full request examples and errors
HTTP JSON-RPC · cURL
curl "$SENDER_URL" \
  -H 'Content-Type: application/json' \
  -H "Authorization: Bearer $SENDER_API_KEY" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "sendTransaction",
    "params": [
      "SIGNED_TX_BASE64_WITH_TIP",
      {"encoding": "base64", "skipPreflight": true}
    ]
  }'

The signed transaction must include at least 150,000 lamports to an accepted tip account.

Handle the response: inspect JSON-RPC errors even on HTTP 200. On 429, respect Retry-After. Check signature status before retrying an ambiguous submission.

Set up transaction delivery.

  1. Tell Supanode

    Request a TPU Sender key on Telegram. Include your preferred region and expected request rate.

  2. Get your setup

    Supanode provides the API key and connection details. Ask separately for QUIK access if needed.

  3. Prepare & send

    Fetch a blockhash, add your instructions and tip, sign locally and call sendTransaction.

  4. Track the result

    Use getSignatureStatuses on your normal RPC. Check the commitment level and execution error.

Integration guide · Compare Solana pricing

Before you integrate.

Do I need a separate staked RPC plan?

Stake-weighted delivery is part of TPU Sender. You still need your regular RPC for reads, blockhashes, simulation and confirmation. Supanode can advise on the setup you need.

Does a returned signature mean the transaction landed?

Check getSignatureStatuses after submission and inspect both confirmationStatus and err. A null result has no confirmation yet; a non-null err means execution failed.

Is the tip the same as a priority fee?

The tip pays for the sender path. Solana base fees and priority fees pay validators and are additional. A priority fee does not replace the sender tip.

How is the private rate limit shared?

The documented default is 50 requests per second per client profile. Clients sharing that profile share the quota. The counter uses fixed one-second windows. Contact Supanode for different limits.

Can I test without requesting a key?

The paid public route accepts requests without a key, with a minimum tip of 200,000 lamports and a limit of one request per second per source IP. Ask our team about a free trial up to 24 hours; availability and setup are confirmed separately. Read the public route documentation before submitting.