> For the complete documentation index, see [llms.txt](https://docs.rpcfast.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rpcfast.com/solana-dedicated-nodes/low-latency-solana-playbook-for-hft.md).

# Low-Latency Solana Playbook for HFT

High-frequency trading (HFT) on Solana demands **sub-millisecond reaction times** and **guaranteed transaction landing**. Below is the recommended setup for traders, bots, and protocols that want the lowest possible latency.

It is possible to optimise Solana latency by combining services (ShredStream, Yellowstone, TxStream + Beam transaction sending service) plus infra tuning and colocation – but the gains, costs, and trade-offs (centralization/MEV exposure, complexity) vary.

#### 1. Infrastructure foundation: bare-metal + tuning by RPC Fast <a href="#id-1.-infrastructure-foundation-bare-metal--tuning-by-rpc-fast" id="id-1.-infrastructure-foundation-bare-metal--tuning-by-rpc-fast"></a>

* **Hardware:** RPC Fast provisions the most efficient bare-metal servers with 512GB-1.5TB RAM, tuned for Solana.
* **Location:** Servers colocated in proximity to Solana leader nodes constellations. Optimized regions for using SWQoS and shreds are FRA, AMS, NY (Equinix, TeraSwitch datacenters).
* **Tuning & Maintenance:**
  * **Performance optimization:** node configuration for high throughput and low latency. Our engineers reduce base network latency and variance before layering Solana-specific optimizations.
  * **Recommended methods** for efficient event monitoring: [TxStream](https://docs.rpcfast.com/txstream), [ShredStream gRPC](https://docs.rpcfast.com/rpc-fast-saas-solana/data-streaming/data-access-options), [Yellowstone gRPC](https://docs.rpcfast.com/rpc-fast-saas-solana/data-streaming/yellowstone-grpc).
  * **Proactive monitoring & alerts.**
  * **Sync and network health,** full managed service – RPC Fast keeps infra always at peak.

#### 2. Market data ingestion – get shreds faster <a href="#id-2.-market-data-ingestion-get-shreds-faster" id="id-2.-market-data-ingestion-get-shreds-faster"></a>

{% hint style="info" %}
Read more about the data streaming options included in our RPC subscriptions [here](https://docs.rpcfast.com/rpc-fast-saas-solana/data-streaming).
{% endhint %}

* **ShredStream** **gRPC** (shreds from DoubleZero, Orbit, Raiden, or other partner providers) → direct feed of leader-produced shreds. Traders see block data hundreds of ms earlier than waiting on Turbine/gossip.
* [**TxStream**](https://docs.rpcfast.com/txstream) → purpose-built for low-latency **decoded transaction streaming**, with server-side filters and optional real-time simulation.
* **Yellowstone gRPC** (Geyser plugin) → structured, filtered, and low-latency streams for accounts, slots, and transactions. Perfect for strategy logic, dashboards, and monitoring.

{% hint style="success" %}
RPC Fast integrates the feeds requested by the client, based on most efficient performance and client’s specific requirements.
{% endhint %}

**Note:** A smart routing for whichever feed delivers first happens automatically – all data feeders push shreds to the Solana node in addition to p2p (Turbine in Solana). The node uses the data that arrived the fastest. However, there has been a trend to replace the "Solana node + Yellowstone gRPC" pair with ShredStream gRPC, so as not to wait for the Solana node.

#### 3. Transaction submission – land first, not last <a href="#id-3.-transaction-submission-land-first-not-last" id="id-3.-transaction-submission-land-first-not-last"></a>

* [RPC Fast Beam](https://docs.rpcfast.com/rpc-fast-saas-solana/sending-transactions/rpc-fast-beam-beta) transaction sending service (SWQoS via the partners' network).
* **Colocation Peering** → servers are placed in the right spots to minimize latency to leaders.

{% hint style="success" %}
**Result:** transactions arrive earlier at the leader and get a better shot at first-slot inclusion.
{% endhint %}

#### 4. Trade-offs to keep in mind <a href="#id-4.-trade-offs-to-keep-in-mind" id="id-4.-trade-offs-to-keep-in-mind"></a>

* **Centralization & MEV:** Relying on providers means aligning with their relay ecosystems.
* **Cost:** Bare-metal, colocation, and premium feeds are not cheap – but for HFT, speed is profit.
* **Complexity:** RPC Fast abstracts this away with full DevOps + infrastructure management.

### Recommended Setup (Step-by-Step) <a href="#recommended-setup-step-by-step" id="recommended-setup-step-by-step"></a>

1. Provision bare-metal high-performance server in leader-adjacent DCs (handled by RPC Fast).
2. Use ShredStream or TxStream gRPC for low-latency transaction data.
3. Use Yellowstone gRPC for structured feeds.
4. Route transactions via [Beam](https://docs.rpcfast.com/rpc-fast-saas-solana/sending-transactions/rpc-fast-beam-beta) sender. Try different available providers/routes.
5. RPC Fast engineers will assist in continuous benchmarking & performance tuning via dedicated communication channels.
6. Scale horizontally with multi-region redundancy, if needed.

With RPC Fast handling infra + optimization, HFT teams can focus entirely on strategy and execution, knowing their Solana connection is as fast, stable, and tuned as physics allows.

### Parallel Submission <a href="#parallel-submission" id="parallel-submission"></a>

Broadcasting a single signed transaction to **multiple RPC/relay endpoints in parallel** increases the probability that (a) at least one path delivers it quickly to the current leader and (b) it avoids single-path congestion or transient RPC failures – as long as you handle blockhash expiry, deduplication, and monitoring correctly.

{% hint style="success" %}
RPC Fast provides several options for sending transactions and we recommend combining various approaches for more efficient performance.
{% endhint %}

#### Why parallel submission helps <a href="#why-parallel-submission-helps" id="why-parallel-submission-helps"></a>

* **Multiple network paths → lower tail latency.** Different RPC providers and relays have different peering, geographic placement, and routing to validators/leaders. Sending to several reduces p95/p99 propagation time to the leader (race-to-leader effect). The transaction will only go through using one path (and fail/reverse in others) and will be free of charge. Yet, be aware of RPC rate limits regardless of success.
* **Different relayer ecosystems catch different leaders.** Some relays have direct/private routes to leaders or trader-focused routing; sending to them in parallel exploits whichever has the fastest path to the current leader.
* **Race improves inclusion odds vs. queueing/MEV competition.** If there’s contention for a slot, the node that reaches the leader first (or the relay that hands higher-priority tx to a block-builder) has the advantage. Broadcasting broadly turns latency into a competitive edge.

#### Quick checklist to try this today <a href="#quick-checklist-to-try-this-today" id="quick-checklist-to-try-this-today"></a>

1. Pick 3–5 endpoints
2. Implement parallel fan-out of the same signed ttransaction to all endpoints.
3. Listen for `sendTransaction` acceptance + `getSignatureStatuses`. Stop after first accepted and track finalization.
4. Repeat under different network conditions and collect p50/p95/p99.
5. Add durable nonce if you require multi-minute retry windows.

#### Risks & trade-offs <a href="#risks-and-trade-offs" id="risks-and-trade-offs"></a>

* **Cost & rate limits:** Broadcasting to many paid endpoints increases usage & cost and may hit RPC rate limits. Budget accordingly.
* **Increased attack surface / centralization:** Over-reliance on a single relay provider undoes redundancy goals; diversify relays. Also be explicit about MEV exposure – some relayers may reorder or insert MEV-enabled behavior. [DEV Community](https://dev.to/btcmiles/types-of-quantitative-trading-on-solana-iah)
* **False positives on “accepted”:** Some RPCs report accepted locally but may drop the tx before it reaches the leader (always follow up with network status checks). [Medium](https://medium.com/%40yhl125/solana-transaction-c277de3cd6ec)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.rpcfast.com/solana-dedicated-nodes/low-latency-solana-playbook-for-hft.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
