> For the complete documentation index, see [llms.txt](https://docs.gravityblocks.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gravityblocks.xyz/gbx-gravity-block-exchange.md).

# GBX: Gravity Block Exchange

> **GBX is an open and neutral marketplace for Solana blockspace.**

Validators supply blockspace. Users, traders, and applications create demand for inclusion and ordering. Block builders compete to allocate that capacity by selecting and ordering transactions. GBX brings them all together in a single market.

#### Why GBX

* **Higher validator rewards** through competitive auctions between independent block builders.
* **Neutral by design:** every builder competes under the same auction rules and scoring, with no preferential treatment.
* **Consistent execution for traders and applications:** shared market rules including maker priority hold on every slot.
* **Efficient block production** by moving simulation and sequencing off the validator’s critical path.
* **Faster innovation** without protocol changes or validator-client release cycles.
* **Validator control:** configurable scheduling constraints, detailed observability, and a native scheduler fallback.

#### Shared market rules

Every auction on GBX runs under the same rules, whichever builder wins.

**Neutral scoring:** Every submission is scored the same way, by the rewards it produces for the validator, with no preferential treatment for any builder.

**Market features:** Features such as maker priority and the [market tick](https://github.com/firedancer-io/market-tick) are applied at the marketplace level. All hold on every connected validator, so execution is consistent for traders and applications.

**Scheduling extensions:** New ordering, atomicity, and execution features, such as ACE, can be integrated into the marketplace and supported by builders without waiting for validator client releases.

#### Validator control

**Configurable scheduling:** Builders determine transaction sequencing, while validators set the parameters and constraints for their own slots, including SFDP-compliant scheduling.

**Observability and reporting:** GBX collects detailed marketplace and execution telemetry. Validators receive dashboards for monitoring performance and operational health, alongside reporting that can support ETF requirements and detailed breakdowns for DATs.

**Native scheduler fallback:** If GBX becomes unavailable, the validator falls back to its native scheduler.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.gravityblocks.xyz/gbx-gravity-block-exchange.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
