> 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/solutions-for-you/traders-and-searchers.md).

# Traders & Searchers

Trade blockspace as an asset, buy preconfirmations for guaranteed inclusion and hedge gas volatility.

**The Solution: The Blockspace & Preconf Marketplace**

Trade the core components of Ethereum execution itself, unlocking new opportunities for alpha and risk management.

* **Precision execution:** Buy *inclusion preconfirmations* to secure guaranteed placement with absolute certainty, the ultimate edge for latency-sensitive and searcher strategies.
* **Guaranteed inclusion:** Lock in that your transaction lands, settling in **50–100ms**, instead of competing blindly in every block auction.
* **Hedge volatility:** Use upcoming *Base Fee Futures* to hedge gas-price volatility, turning an unpredictable cost into a manageable variable.
* **A new liquid asset class:** Blockspace is deeply correlated with onchain activity — opening sophisticated arbitrage and hedging strategies against the broader market.

**Get started**

* ETHGas trading is available on Mainnet and for testing on the Hoodi network.
* Monitor the markets in the App UI (read only): <https://app.ethgas.com/>
* Testing is available via API: see [developer docs](https://developers.ethgas.com/#change-log).
* Product detail: [Blockspace & Preconf Marketplace](/overview/preconf-marketplace.md)


---

# 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/solutions-for-you/traders-and-searchers.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.