> For the complete documentation index, see [llms.txt](https://docs.triton.one/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.triton.one/solana/faq/sending-transactions.md).

# Sending transactions FAQ

Questions about transaction landing, staked connections, and processed-vs-confirmed transaction lifecycle on Solana.

<details>

<summary>My transactions aren't landing successfully. What should I do?</summary>

Triton ensures reliable transaction delivery to the network, but for optimal transaction finalisation, we recommend configuring appropriate priority fees. See our [Priority Fees API](/solana/sending-transactions/priority-fees-api.md) for how to set them.

</details>

<details>

<summary>What is the advantage of sending transactions over a staked connection?</summary>

Validators reserve most of their transaction-ingest (TPU) capacity for connections from staked identities, shared out by stake, while unstaked senders compete for the rest. During congestion, that's a significant advantage. We provide stake-weighted QoS routing for free on every Triton subscription; it's applied by default on your mainnet endpoint.

</details>

<details>

<summary>Can a <code>processed</code> transaction on Solana still be dropped?</summary>

Yes. A transaction is only final once it reaches `confirmed` or `finalized` commitment. Slots containing `processed` transactions can still be dropped during minority forks or network congestion.

</details>

<details>

<summary>What's the difference between <code>sendtx</code> and <code>sendTransaction</code>?</summary>

Both route through our specialised transaction-sending Jet engine, with SWQoS on by default for mainnet, so the difference is entirely in the request format. `sendTransaction` is the standard JSON-RPC method, which requires the server to parse a JSON-RPC envelope before submitting it. `/sendtx` is a direct HTTP endpoint: you POST the raw transaction bytes (or a base58/base64 string), which skips the envelope and the server-side JSON parsing, for lower latency. In a browser, only a `text/plain` body (base58, or base64 with `encoding=base64`) avoids the CORS preflight; raw bytes and the Shield header both trigger one. The one tradeoff is that `/sendtx` always submits without a preflight simulation, so it does not support `skipPreflight: false`.

</details>

<details>

<summary>Do I need to set up stake-weighted QoS (SWQoS)?</summary>

No. SWQoS routing applies by default to standard `sendTransaction` and `/sendtx` calls on your existing Solana mainnet endpoint, so there’s nothing to configure client-side.

</details>

<details>

<summary>Is Cascade still available?</summary>

Cascade's staked sending is now the default: SWQoS applies to every mainnet `sendTransaction` and `/sendtx` request through Jet, at no extra cost. There's nothing to request or pay for separately. See [SWQoS for everyone](https://blog.triton.one/swqos-for-everyone-why-we-retired-cascade-marketplace/).

</details>

<details>

<summary>Is there a minimum priority fee?</summary>

No. Solana's default `getRecentPrioritizationFees` returns the recent minimum, which is often zero, so use Triton's `percentile` parameter to set a fee that is competitive during congestion. See [Priority Fees API](/solana/sending-transactions/priority-fees-api.md).

</details>

<details>

<summary>Do you support sponsored transactions or gas sponsorship?</summary>

No. For transaction sending, Triton offers SWQoS delivery, [Yellowstone Shield](/solana/sending-transactions/shield-mev-protection.md) validator policies, and priority-fee tooling.

</details>

***

<i class="fa-life-ring">:life-ring:</i> Contact support by clicking the chat icon in your [customer dashboard](https://customers.triton.one)\ <i class="fa-briefcase">:briefcase:</i> Sales questions? [Contact us](https://triton.one/contact)\ <i class="fa-sparkles">:sparkles:</i> AI agent? Read [llms.txt](https://docs.triton.one/llms.txt)\ <i class="fa-rss">:rss:</i> Follow updates: [Blog](https://blog.triton.one) · [X](https://x.com/triton_one) · [YouTube](https://www.youtube.com/@triton_one_ltd) · [Telegram](https://t.me/tritonone) · [GitHub](https://github.com/rpcpool)