Get started with Sender
Send your first transaction through Supanode Sender in 5 minutes: pick a regional endpoint, attach a tip, and submit via JSON-RPC.
// updated 2026-06-04
From zero to first landed transaction in 5 minutes.
What you'll need
- A funded Solana wallet with enough SOL to cover the tip - minimum 1,000,000 lamports (0.001 SOL) per transaction. See Tips.
- A signed transaction, base64-encoded.
- An HTTP client -
curlworks, any language with HTTP support works.
Send your first transaction
- 1Pick the closest endpoint
Connect to the region nearest your servers for lowest latency.
For most workloads in EU:
http://fra.landing.fast(Frankfurt).See Endpoints for Amsterdam and Tokyo.
- 2Construct your transaction with a tip
Every transaction sent through Sender must include a System Program transfer to one of Supanode's tip accounts. Without a tip, the transaction is rejected at the gateway.
Minimum tip is 1,000,000 lamports (0.001 SOL). See Tips for tip addresses and code samples.
Submit
Pick the submission method matching your latency requirement.
| Method | Latency | Best for |
|---|---|---|
| JSON-RPC | Low | Drop-in replacement for existing RPC clients |
| HTTP Plaintext | Lower | Quick scripts, prototyping |
| HTTP Binary | Lowest | Microsecond-critical workloads |
Quick test using JSON-RPC:
curl -sS 'http://fra.landing.fast' \
-H 'Content-Type: application/json' \
--data '{
"jsonrpc": "2.0",
"id": 1,
"method": "sendTransaction",
"params": [
"YOUR_BASE64_ENCODED_TX",
{
"encoding": "base64",
"skipPreflight": true
}
]
}'
For Plaintext and Binary methods, see Submission methods.
Verify landing
A 200 response means forwarded, not landed on-chain. Always verify with RPC getSignatureStatuses.
curl http://fra.supanode.xyz:8899 \
-H "Content-Type: application/json" \
-d '{
"jsonrpc": "2.0",
"id": 1,
"method": "getSignatureStatuses",
"params": [["YOUR_SIGNATURE"]]
}'
Check that confirmationStatus is confirmed or finalized.
Best practices
- Simulate before sending. Sender never runs preflight. Run
simulateTransactionagainst RPC first. - Single endpoint per app instance. Pick the region closest to your servers, stick with it.
- Track landing rate. Compare submitted transactions vs confirmed signatures.
- Exponential backoff on
429/500. Start at 1 second, cap at 30.
Response codes
| Code | Meaning |
|---|---|
200 | Transaction accepted and forwarded |
429 | Rate limited - back off and retry |
500 | Server error - retry with backoff |
Where to next
JSON-RPC, Plaintext, Binary.
Minimum tip and tip addresses.
Regional endpoints.
What it is and how it works.