> 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/get-started/traders/propamm/with-realtime-markets.md).

# With Realtime Markets

The ETHGas Realtime Market is designed to support propAMM trading through Flashblocks: sub-blocks that incrementally extend an Ethereum block.

Makers and takers receive execution preconfirmations at sub-block boundaries, before the complete block is published.

### Execution and confirmation

For each sub-block, the builder evaluates applicable maker updates and taker transactions against the current execution state. Required maker updates execute before the taker transactions that use them.

Once a sub-block is committed, its included transactions, ordering and execution results are fixed within the realtime commitment. Subsequent sub-blocks build on that resulting state.

```
Sub-block 1 (Slot 1): Maker update A → Taker trade A
Sub-block 2 (Slot 1): Maker update B → Taker trade B
Sub-block 3 (Slot 1): Additional updates and trades
```

In this example, committing Flashblock 1 fixes the execution of update A and trade A. Cancelling after the trades were preconfirmed cannot remove them from the committed sequence. Update B can change prices for subsequent trades, but it cannot retroactively change trade A’s execution.

### Maker updates and cancellations

Before commitment, pending maker updates may be replaced or cancelled. The builder applies these changes when evaluating transactions for an upcoming sub-block.

After commitment, an included update cannot be withdrawn from the committed sequence. Makers can submit a new update for a later sub-block, subject to transaction validity and the applicable inclusion rules.

Commitment preserves execution history; it does not freeze the pool’s state permanently. Later updates and trades will continually change that state.

#### **Updating quotes multiple times within a realtime slot**

Makers can submit multiple price updates within the same 12-second Ethereum slot. This approach apply when the target slot is listed by the [Realtime Markets API](https://prod-mainnet.ethgas.com/api/v1/p/realtime/markets).

Connect to the Flashblocks feed at `wss://mainnet.flashblocks.ethgas.com/ws` and monitor your submitted quote transactions in each sub-block. Flashblocks target approximately [200ms intervals](https://docs.ethgas.com/overview/which-blocks-are-realtime).

1. Submit a signed quote transaction with Ethereum nonce `n`, targeting block `B`.
2. Until a transaction using nonce `n` is included, keep using the same nonce when replacing the outstanding quote. Track all submitted transaction hashes, since an earlier version may land.
3. Once one of those transactions appears in a committed Flashblock for block `B`, sign and submit the next quote using nonce `n + 1`, targeting the same block.
4. Repeat while the slot’s submission window remains open. You do not need to wait for the Ethereum block to become canonical.

### State feeds and execution status

A streamed quote or state override provides routing information. It does not, by itself, confirm that a maker update or taker trade has executed. Likewise, a submission acknowledgement confirms receipt, not inclusion.

Execution is preconfirmed when the transaction is included in a committed Flashblock. Consumers should distinguish pending quote data from committed execution results.

### Scope of confirmation

Flashblock commitment prevents the builder from removing or reordering previously committed transactions within the realtime sequence.

This is a realtime preconfirmation. Ethereum block inclusion and consensus finality remain as separate stages, with their associated failed-inclusion and reorganization risks.


---

# 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/get-started/traders/propamm/with-realtime-markets.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.
