Send transactions straight to the leader.
Prepaid, stake-weighted sending from cubestech. One price per send, refunded in full when it does not land.
Price per send
0.0002SOL
Funded in SOL. No subscription, no minimum commitment, nothing to cancel.
From your signer to the slot leader.
You post a signed transaction to a send address that belongs to cubestech. It is forwarded without being touched.
Your signed transaction
Built and signed on your side. We never see a private key.
This store's send address
send-
cubestech. site. nodeshop. app Stake-weighted connection
Held open and kept warm, with nothing in the path that waits on an RPC.
The current slot leader
Your exact bytes arrive unchanged.
What does not change
- Your bytes stay yours
- No tip instruction is added, no priority fee is adjusted and nothing is re-signed. The signature in your receipt matches the transaction you built.
- No detour through an RPC
- There is no simulation and no blockhash round trip in the forwarding path. Your client already holds a blockhash, and that is all it needs.
- A receipt is not a landing guarantee
- An accepted receipt means your bytes were forwarded. Whether they landed on chain is reported separately in your dashboard.
Pricing
One price per send. Prepay in SOL.
Add as much balance as you like and spend it down one send at a time. Choose a deposit to see what it buys.
sends for a 0.1000 SOL deposit, at 0.0002 SOL each.
- Deposit
- Sends
- 0.0500 SOL
- 250
- 0.1000 SOL
- 500
- 0.5000 SOL
- 2,500
- 1.0000 SOL
- 5,000
You pay only for what lands.
Prepaid sends that do not land are fully refunded. Every other outcome is listed here, so there is nothing to discover on an invoice.
- Accepted with prepaid balanceOne send (0.0002 SOL) reserved
- Transaction landsOne send (0.0002 SOL) settled
- Transaction does not landFully refunded
- Forwarding failed upstreamCharged, then reversed
- Duplicate signature within 90 secondsFree
- Invalid transaction envelopeFree
- Unknown or invalid API keyFree
- Account disabledFree
- Insufficient balanceFree
Quickstart
Your first send is one request.
Fund
Open your dashboard and send SOL to the deposit address with your personal memo. Balance appears once the deposit finalizes.
Copy
Copy your API key from the same page. Treat it like a password and keep it out of logs.
Send
Post the signed, base64 transaction to send-
cubestech. site. nodeshop. app .
curl -sS https://send-cubestech.site.nodeshop.app/v1/transactions \ -H "Authorization: Bearer $SWQOS_API_KEY" \ -H 'Content-Type: application/json' \ -d "{\"transaction\":\"$TRANSACTION_BASE64\"}"Every refusal comes with a code.
Errors are JSON with a stable code and a message. None of these outcomes charge your balance.
Malformed requests
- 400INVALID_BASE64The transaction field is not valid base64. Base64-encode the serialized transaction, not JSON or hex.
- 400INVALID_TRANSACTIONThe serialized envelope is malformed or out of bounds. Send a fully signed legacy or versioned transaction under 1232 bytes.
- 400INVALID_REQUESTA request field is missing or malformed. Check the JSON body against the example above.
- 409SUBMISSION_IN_PROGRESSThe same signature is already in flight. Wait for the first submission to return instead of retrying at once.
Key and balance
- 401UNAUTHORIZEDNo Bearer credential was supplied. Send an Authorization header of the form Bearer <key>.
- 401INVALID_API_KEYThe key could not be decoded. Check the key is intact. Keys are secrets, so never log them.
- 402INSUFFICIENT_BALANCEThe account has no prepaid balance left. Deposit SOL from your dashboard. Balance appears once the deposit finalizes.
- 403ACCOUNT_DISABLEDThe account exists but is switched off. Contact support. This is usually a billing or abuse review.
Service availability
- 503BILLING_UNAVAILABLEBilling persistence is unhealthy. Retry with backoff. Nothing was charged.
- 503AUDIT_UNAVAILABLEAudit persistence is unhealthy. Retry with backoff. Nothing was charged.
- 503UPSTREAM_UNAVAILABLEThe transaction could not be forwarded. Retry. Any charge for this submission is reversed automatically.
Questions people ask first.
What is SWQoS?
SWQoS forwards already-signed Solana transactions over stake-weighted connections. A landed send costs 0.0002 SOL here, with no subscription. Prepaid sends that do not land are fully refunded.
Does SWQoS change my transaction?
No. The exact bytes you submit are forwarded unchanged. Nothing adds a tip instruction, adjusts a priority fee, re-signs or reorders anything, so the signature in your receipt always matches the transaction you built.
What does an accepted receipt mean?
An accepted receipt means your bytes were forwarded and the connection acknowledged them. It is not a guarantee that the transaction lands. Check getSignatureStatuses or getTransaction with the signature from your receipt when you need to know.
How much does a send cost?
A landed send costs 0.0002 SOL. Sends that do not land are fully refunded, and duplicate signatures inside 90 seconds, invalid envelopes and rejected requests are free.
How do I add balance?
Open your dashboard and send native SOL to the deposit address shown there, with your personal memo attached. The minimum deposit is 0.0100 SOL. Balance is credited once the deposit finalizes on chain. A deposit without your memo cannot be matched to your account.
Where do I send transactions?
Post to https://send-cubestech.site.nodeshop.app/v1/transactions with your API key as a Bearer token. The address is specific to this store.
Who holds my keys?
You do. You sign locally and submit the signed bytes. Your API key identifies your billing account only. It cannot sign or move funds.
What happens when my balance runs out?
New submissions are refused with INSUFFICIENT_BALANCE and you are not charged. Nothing is queued or silently dropped. Add balance from your dashboard and sending resumes once the deposit finalizes.