# Technical Architecture

### System Components

| Component                   | Role                                                                            |
| --------------------------- | ------------------------------------------------------------------------------- |
| **Flowra Validator Client** | Jito-Solana fork, transaction observation and forwarding via Banking Stage Hook |
| **Tx Stream Sidecar**       | Deduplication, timestamp / CU / account metadata attachment                     |
| **Open Orderflow Gateway**  | gRPC streaming of filtered transactions broadcast to searchers                  |
| **Bundle Ingress API**      | Key-based searcher onboarding, bundle reception and validation                  |
| **Auctioneer**              | 200ms mini-auction cycle, selects highest-tip bundle                            |
| **Flowra Builder**          | Conflict detection, atomic bundle execution, block assembly                     |

***

### Transaction Flow

```
① Validator runs Flowra Client
         ↓
② Pending transactions forwarded to Tx Stream Sidecar
         ↓
③ Open Orderflow Gateway streams to searchers via gRPC
         ↓
④ Searcher detects MEV opportunity, submits bundle with tip
         ↓
⑤ Auctioneer selects highest-tip bundle every 200ms
         ↓
⑥ Flowra Builder guarantees atomic execution
         ↓
⑦ Winning bundle included first in block
```

***

### Core Technical Features

#### Mini-Auction (200ms cycle)

Splits each slot into micro-windows aligned with Solana's continuous block production. Maximizes the number of competitive cycles within the 400ms block time to maximize tip revenue.

#### Atomic Bundle Execution

All transactions in a bundle must succeed to be included in the block. Prevents partial execution, guaranteeing searchers' MEV strategies execute in full.

#### Conflict-Aware Selection

Automatically detects conflicting bundles that modify the same account state, then selects the optimal combination of non-conflicting bundles to maximize block revenue.

#### Leader Injection

Winning bundles are included first at the front of the block; remaining block space is filled using standard fee/priority rules. Validators capture both MEV revenue and standard transaction fees.

***

### Security & Anti-Spam

Flowra maintains the benefits of an open structure while implementing a multi-layer security system to prevent abuse.

| Security Feature                 | Description                                                      |
| -------------------------------- | ---------------------------------------------------------------- |
| **Minimum Tip Requirement**      | Economic deterrent against bundle submission spam                |
| **Rate Limiting**                | IP/ASN-based speed limits, concurrent stream cap                 |
| **Dual-Signature Deduplication** | Signature-based deduplication prevents amplification attacks     |
| **Forced Filter Subscription**   | Searchers must specify CU range, account, and Program ID filters |


---

# 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://flowra.gitbook.io/flowra/solution/technical-architecture.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.