> 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/core-infrastructure/our-technology-stack.md). # Our Technology Stack **1. Infrastructure: Bare-metal & Co-location**\ We do not rely on cloud providers or public RPCs. Our foundation is built on **proprietary bare-metal servers** deployed in strategically chosen datacenters (primarily Frankfurt). This gives us full control over the network stack and eliminates the "noisy neighbor" problem inherent to cloud environments. **2. Solana Client: Firedancer**\ We utilize **Firedancer** as our primary validator client. Its modern architecture, optimized for maximum parallelism, allows us to process and deserialize incoming data (shreds) with significantly lower latency than the standard Agave client. This is our first and one of our most critical advantages. **3. Execution Core: Rust & Low-Level Optimization**\ All of our logic is written in **asynchronous Rust** on the tokio runtime. We avoid heavy dependencies and focus on zero-copy parsing and memory allocation optimization (including mimalloc/jemalloc). Our goal is a signal-to-signature pipeline that executes in microseconds, not milliseconds. Our execution framework is not a monolithic bot. It is a collection of independent, high-performance services that communicate over low-latency, in-memory channels. This modularity allows for rapid development, testing, and deployment of new strategies. * **Signal Acquisition Service (The Watcher):** Connects to data sources (Geyser/Shredstream) and produces a stream of decoded, relevant on-chain events. * **Strategy Engine (The Brain):** Subscribes to events from the Watcher. Contains the core alpha logic that decides if and how to act. * **Execution Service (The Engine):** Receives action commands from the Strategy Engine. Manages leader analysis, risk checks, transaction/bundle construction, and submission. * **State & Cache Service:** An in-memory database (RwLock, LruCache) that provides all services with sub-microsecond access to critical data like blockhashes, validator lists, and account states. --- # 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/core-infrastructure/our-technology-stack.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.