# Problem Definition

### Three Structural Problems on Solana

***

### 3.1 User Over-Payment — Information Asymmetry

Despite Solana blocks often running below 50% utilization, users are overpaying Priority Fees and Jito tips to improve their landing probability.

This stems from **information asymmetry** in the fee market. Users can't see real-time block congestion or competing transactions' fee levels, so they defensively set fees too high.

```
User: "I don't know what's needed to land — I'll just go high."
                      ↓
         Overpayment → validator & infrastructure provider revenue
```

{% hint style="danger" %} Structural user overpayment is happening systematically — and it's entirely due to a lack of fee market transparency. {% endhint %}

***

### 3.2 Single Infrastructure Dependency — Jito Monopoly

Jito holds a de facto monopoly over Solana validator infrastructure at **94%+** of stake.

Validators have no real choice: skip Jito and forfeit MEV and tip revenue entirely. This creates two serious risks.

| Risk                        | Description                                              |
| --------------------------- | -------------------------------------------------------- |
| **Single point of failure** | A Jito outage paralyzes the entire MEV infrastructure    |
| **Power imbalance**         | Jito can unilaterally change fee structures and policies |

**Real example:** When Jito discontinued its mempool service in 2024, validators were forced to accept a core infrastructure change with no prior notice and no alternative.

***

### 3.3 Opaque Transaction Order Markets

MEV searchers manipulate transaction ordering through private channels with validators — a process that cannot be verified from the outside.

* No way to quantify how many sandwich attacks are occurring
* No way to measure how much worse execution users receive due to backruns
* Only the handful operating private mempools can access MEV opportunities

Because Solana has no public mempool by design, orderflow moves through private channels. This makes the opacity problem far more severe than on Ethereum.

**The DeezNode case:** A private mempool that emerged after Jito's closure, earning **65,880 SOL ($13.43M)** over 30 days. MEV didn't disappear — it just concentrated further among the privileged few.

***

### 3.4 BAM's Limitations

Jito's proposed solution — BAM (Block Assembly Marketplace) — creates new problems for validators rather than solving existing ones.

#### Validator Authority Weakened

* Block building authority transferred to BAM nodes, reducing validators to **executors only**
* MEV revenue distribution shifts against validators

#### App-Centric Design — Validators Marginalized

* ACE (Application-Controlled Execution) favors apps and protocols over validators
* Risk of MEV revenue being redirected to the app layer, eroding long-term validator income

| Issue               | BAM                      | Flowra                             |
| ------------------- | ------------------------ | ---------------------------------- |
| Validator authority | ❌ Delegated to BAM nodes | ✅ Bundle selection rights retained |
| MEV beneficiary     | ❌ Apps/protocols         | ✅ Validators + users               |
| Transparency        | ❌ TEE                    | ✅ Fully on-chain                   |
| Dependency          | ❌ Still Jito-dependent   | ✅ Validator Sovereignty            |


---

# 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/overview/problem-definition.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.