> 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/navigating-network-mechanics.md).
# Navigating Network Mechanics
Performance requires a deep understanding of the protocol's constraints.
Effective execution on Solana is a game of physical and protocol-level constraints. Our architecture is engineered to operate within these realities.
\
\
\- Geographical Latency: We address Round-Trip Time (RTT) by co-locating our Firedancer infrastructure in Frankfurt, proximate to the core European validator stake. For global coverage, we utilize multi-region submission to all key Jito Block Engines (FRA, NY, TOK), which is the industry standard for mitigating geographical risk.\
\
\- Throughput Limits (TPS): We are aware of the standard submission rate limits. Our system utilizes a pool of unique Keypairs for different strategies to effectively manage transaction flow. For scenarios requiring higher frequency, we will engage with infrastructure providers to secure dedicated, high-throughput channels.
Screen from:
---
# 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/navigating-network-mechanics.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.
