> For the complete documentation index, see [llms.txt](https://docs.bloxroute.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bloxroute.com/solana/optimized-feed-relay.md).

# Optimized Feed Relay (OFR)

The bloXroute Optimized Feed Relay (OFR), pronounced "Offer", delivers shreds with exceptional speed, offering latency improvements of 30-50+ ms when compared to default Turbine propagation . The OFR provides significant benefits to all nodes, including Staked Validators and RPC nodes, Trading Bots, HFTs, Market Makers & DeFi Traders.

Chains supported: SOL

### Benefits of Connecting to the OFR

* **Faster Geyser Notifications for Traders**: Traders using a local node with the Geyser plugin will experience significantly faster notifications, improving decision-making and responsiveness.
* **Increased APY for Validators**: Validators can expect higher APY due to reduced forks and improved voting efficiency.
* **Enhanced Endpoints for RPC Providers**: RPC providers will deliver faster, more reliable endpoints to their users, improving overall service quality.

### How to Connect

Leverage OFR by [connecting](/solana/optimized-feed-relay/shred-stream.md) to bloXroute's Optimized Feed Relay (OFR) through Shred Stream. Once connected, the Stream enables your local client (identified with ip and port) to efficiently receive shreds across the OFR, maximizing performance.

### Stay Updated

For the latest information about the OFR, join our [Discord community](https://discordapp.com/invite/mB95H7s).


---

# 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.bloxroute.com/solana/optimized-feed-relay.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.