# Performance & Relays

This page explains why Dark Entry Bot is so fast and how it maximizes your chances of landing in block 0.

***

## 11 Relays in parallel

On every buy, the bot sends your transaction simultaneously to **11 different relays**. The first one to confirm block inclusion wins the race — the other attempts stop.

This approach multiplies your chances of being in block 0 or block 1.

| #  | Relay      |
| -- | ---------- |
| 1  | Falcon     |
| 2  | bloXroute  |
| 3  | Astralane  |
| 4  | 0Slot      |
| 5  | NextBlock  |
| 6  | BlockRazor |
| 7  | Node1      |
| 8  | FlashBlock |
| 9  | Stellium   |
| 10 | AllenHark  |
| 11 | Nozomi     |

***

## Multiple detection sources

The bot receives new token creation signals through several channels at the same time. The first signal received triggers the buy — duplicates are automatically ignored.

***

## Why the bot is so fast

Dark Entry Bot's speed is extreme thanks to a combination of optimizations at every level:

* **Real-time data** — the bot receives information directly from sources as close as possible to Solana validators, with no middleman. When a token is created, the bot knows about it within microseconds.
* **Everything is prepared in advance** — by the time a signal is detected, the transaction is already mostly built. The bot does not start working after the signal — it was already ready before.
* **11 relays simultaneously** — by sending to all relays at the same time, the bot does not depend on a single path. The fastest one wins.
* **High-performance dedicated server** — the bot runs on a server configured specifically for speed, located geographically as close as possible to Solana validators.

***

## Your data is saved

All your configuration and positions are stored in a local database on the server. In the event of a restart, everything is restored automatically.


---

# Agent Instructions: 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:

```
GET https://dark-entry.gitbook.io/dark-entry-docs/bonus/infrastructure.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.