> For the complete documentation index, see [llms.txt](https://elite-node.gitbook.io/elite-node-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elite-node.gitbook.io/elite-node-docs/signal-acquisition-geyser-vs.-shredstream.md).
# Signal Acquisition: Geyser vs. Shredstream
Back-running is a commodity. Front-running is an art.
The quality of an MEV strategy is defined by the quality of its signal. There are two primary methods for real-time data ingestion on Solana:
1. **Geyser gRPC (transactionsSubscribe):** This provides a stream of **fully-formed blocks** as they are propagated by the leader. While fast, it delivers a post-facto view of the slot. The transaction order is already determined. This is effective for **back-running** strategies (landing in the same block, after the target) and serves as the baseline for our MVP.
2. **Jito Shredstream:** This provides a stream of **raw shreds** as the leader is actively building the block. This is a **pre-finalization** data source. It allows visibility into transactions before the block is sealed, creating the necessary, albeit brief, window for competitive **front-running**.
Our framework is architected to be source-agnostic, but our entire alpha model is predicated on the low-latency, pre-finalization data that only Shredstream can provide.
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://elite-node.gitbook.io/elite-node-docs/signal-acquisition-geyser-vs.-shredstream.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.