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

# Inclusion Preconfirmations

<figure><img src="https://1913553586-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FBk99eVkZsNrI6feXAyYs%2Fuploads%2FCahnCT7A1y908qcH5q2c%2Fimage.png?alt=media&amp;token=dc363713-3507-49af-9b84-e7b94f78aa3b" alt=""><figcaption></figcaption></figure>

Inclusion Preconfirmations (or Inclusion Preconfs) are commitments whereby the Proposer guarantees to include your transactions within a specific block N. Bids are for a fixed amount of blockspace (e.g. 200k gas units), may be included anywhere in the block, and do not carry any reversion guarantees.&#x20;

Inclusion Preconf markets are created only when a Validator/Proposer has performed an initial, primary market sale of the Preconfs into the market. That is, it is not possible to ‘short’ an Inclusion Preconf.&#x20;

Transaction Fees: \[ 5% ] on Initial 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/inclusion-preconfirmations.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.