> For the complete documentation index, see [llms.txt](https://docs.ethgas.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.ethgas.com/overview/blockspace-and-preconf-marketplace/whole-block-commitments.md).
# Whole Block Commitments
A Whole Block purchased in the primary market reserves the entire block, \~ 36mm gas units (remark: gas limit can be dynamically adjusted by validators), for the buyer. Buyers may decide to **strip apart** and sell a mix of Inclusion Preconfirmations or Execution Guarantees. At such point, the Whole Block instrument now comprises a mix of other commitments whereupon subsequent secondary market sales of the Whole Block will be defined to be contingent upon including those other commitments.
**Sequencing Rights** are also conferred to the Block Buyer making a whole block buyer a synthetic Block Builder as articulated in [The Design Process](/overview/our-technology/the-design-process.md). Should a block buyer looking to retain key positions/guarantees in a block be unable to [Sequence a block accordingly](/get-started/builders-and-sequencers.md), they may include their own Execution Guarantees or Inclusion Preconfirmations, and either:
* Not sequence the Block, following which ETHGas will be the fallback Builder,
* Sell the Block, or
* Delegate the Sequencing to a specific Builder
Market Details:
* Transaction Fees: \[ 5% ] on Primary sale, \[ 30 ]bps on secondary market trading TBC
---
# 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.ethgas.com/overview/blockspace-and-preconf-marketplace/whole-block-commitments.md?ask=&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.
