> 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/architecture.md).

# Architecture

Validators connect to GBX through the [Gravity Connector](https://github.com/gravityblocks/gravity-connector), an open-source sidecar that runs alongside Agave or Jito-Solana with no custom fork. The Connector links the validator’s scheduler to the marketplace. It sends transaction flow and slot lifecycle updates to GBX, and GBX returns the winning sequences for execution. Because every builder competes through the same marketplace, new builders reach a connected validator’s blockspace without any further integration.

<figure><img src="https://3298602599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtcszVjT2KHu0e67o2bot%2Fuploads%2FssQizDDuyklo1WdCJYCN%2Fgbx-architecture.png?alt=media&amp;token=d4f05ac2-3cc3-4101-9ec3-4db9b64a3f3a" alt=""><figcaption></figcaption></figure>

The validator retains full responsibility for verifying and executing transactions, voting, and broadcasting shreds. The Connector does not participate in consensus or replace the validator’s execution engine. If the external sequencing path becomes unavailable, the validator falls back to its native scheduler.

## Auction dynamics

Each leader slot on GBX is split into auction rounds. Transaction flow streams to every connected builder throughout the slot, and each round follows the same process:

1. GBX opens an auction round.
2. Each builder submits a candidate sequence built from the latest flow.
3. At the round deadline, GBX selects the submission with the highest validator reward and forwards it to the validator.
4. The validator executes the winning sequence, and every builder receives the executed sequence and updates its own state.

A block is built from the winners of many rounds, with builders competing separately for each one. With multiple builders connected, the auction continues even if an individual builder is slow or unavailable.

<figure><img src="https://3298602599-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FtcszVjT2KHu0e67o2bot%2Fuploads%2FesjrptNAjrX8o0QYicKb%2Fgbx-auction-infographic.png?alt=media&amp;token=7e99d0ce-6339-4a40-9784-98d564a3ed43" alt=""><figcaption></figcaption></figure>


---

# 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/architecture.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.
