Skip to content
For the complete documentation index, see llms.txt. This page is also available as Markdown.

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.

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.

Last updated