Frequently asked questions
The questions that come up most about swqos.com: what it is, what it costs, what an accepted receipt means, and who holds your keys.
What is swqos.com?#
swqos.com forwards already-signed Solana transactions over stake-weighted QoS connections. A default landed send costs 0.00015 SOL, with no subscription or minimum. Balance-funded sends that do not land are fully refunded.
Does swqos.com change my transaction?#
swqos.com forwards the exact bytes you submit and never modifies them. It does not add a tip instruction, adjust a priority fee, re-sign, or reorder anything. The signature in your receipt is derived from the bytes you sent, so it will always match the transaction you built.
What does an accepted receipt actually mean?#
An accepted receipt means swqos.com forwarded your bytes and the upstream connection acknowledged the stream. A receipt means the signed bytes were accepted for forwarding. The transaction register separately reports whether they landed on chain. Use getSignatureStatuses or getTransaction with the signature from your receipt when you need to know it landed.
How much does it cost to send a transaction?#
A default landed submission costs 0.00015 SOL. Balance-funded sends are fully refunded when they do not land. An in-transaction SOL payment has no separate refund because the transfer only executes when the transaction executes. Duplicate signatures inside the 90 second dedupe window and forwarding failures are free.
Do I need to hold a token or sign a contract?#
No. Balances are prepaid in native SOL. There is no card, no invoice and no subscription. You deposit native SOL from any wallet, the balance is credited once the deposit finalizes on chain, and you spend it down one send at a time. Stop whenever you like; there is nothing to cancel.
Should I use QUIC or HTTPS?#
Use QUIC if you care about latency, and HTTPS if you care about simplicity. QUIC at send.swqos.com:11000 lets you hold one connection open and open a single stream per submission, which removes the handshake from every send. HTTPS at https://send.swqos.com is a plain JSON POST and is easier to drop into an existing service.
Who holds my keys?#
You do. swqos.com never sees a private key, because you sign locally and submit the already-signed bytes. Your API key is a separate credential that identifies your billing account, and it cannot move funds or sign anything on your behalf.
What happens if my balance runs out?#
Submissions are refused with an INSUFFICIENT_BALANCE error and you are not charged for them. Nothing is queued and nothing is silently dropped, so your client sees the failure immediately and can decide what to do. Top up from the dashboard and sending resumes as soon as the deposit finalizes.
Something else?#
The rest of the documentation covers the detail: quickstart to get running, billing for the exact charge boundary, errors for every failure mode, and limits for the numbers to design around.
If it is not there, email support@swqos.com. A real person reads it.