> 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.md).

# PropAMM

### Building a PropAMM? <a href="#propamm-router" id="propamm-router"></a>

The team at LambdaClass have put together a PropAMM Factory, an open-source repo for deploying and operating your own PropAMM. To get up to speed quickly with the contracts, exchange feeds, pricing logic, signing, builder connectivity and monitoring, go [here for the repo](https://github.com/lambdaclass/propamm-factory), and [here for an intro](https://blog.lambdaclass.com/announcing-propamm-factory/).&#x20;

### PropAMM Router <a href="#propamm-router" id="propamm-router"></a>

The PropAMM Router helps traders find and execute trades against the various PropAMMs.&#x20;

`0x4ddf368080cd7946db5b459ad591c350158175e1`

More information on how to interact with it and all PropAMMs, go [here](https://github.com/lambdaclass/propamm-router-contracts).

### Currently live in ETHGas blocks: <a href="#currently-live-in-titan-blocks" id="currently-live-in-titan-blocks"></a>

| Maker    | Contract                                                                                                                                                                                                                                                                                                              |
| -------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Metric   | <p>Compressed Oracle: <code>0xE844701934D9C6085B292e428F41b911cC0b3872</code> </p><p>Pyth Oracle: <code>0x30a88bf894D1b806125a23ebf23D715496fD7102</code></p><p>ChainlinkOracle:<br><code>0x810A649974f21bB6D3b2E781597EdBDAabe82228</code></p><p>Router: <code>0x99Ab7c1C5eab47801F7937075998527a550fbA8a</code></p> |
| Tempest  | <p>Oracle: <code>0xDa7AfEeD021EAFC1c1Af9C362dE477DaD0396B81</code> </p><p>Router: <code>0x00000003f1ec2379e79F58E12EC6C4F51Ee92149</code><br></p>                                                                                                                                                                     |
| TaurusFi | <p>Oracle: <code>0xDa7AfEeD021EAFC1c1Af9C362dE477DaD0396B81</code> <br>Router: <code>0x3ce2672Aa806138585920421406Bf0dEcB8130Cb</code><br></p>                                                                                                                                                                        |

All PropAMMs are required to implement [this](https://github.com/lambdaclass/propamm-router-contracts/blob/main/src/interfaces/IPropAMM.sol) interface.

### Overview <a href="#overview" id="overview"></a>

A Proprietary AMM (PropAMM \[pAMM]) is an onchain pool in which prices are continuously updated by a market maker. Instead of relying on a passive inventory curve, makers stream signed quote updates to the builder ensuring prices are updated in real-time.

The pool is a passive Ethereum contract, enabling anyone to swap against it directly without an offchain layer. Once a maker update is included, taker interactions settle onchain like any other AMM interaction, and can be composed into normal swap paths, solver transactions, arbitrage bundles, and aggregator routes. This is the key difference to current Ethereum RFQ-style institutional liquidity: pAMM liquidity sits directly inside an onchain venue rather than behind a separate offchain layer.

Ethgas enables pAMMs on Ethereum through a mechanism that grants power over transaction sequencing to applications also known as Application-Controlled Execution (ACE). Makers stream quote updates directly to the builder and receive deterministic priority relating to their own pool updates. Takers submit bundles routing through pAMM liquidity, and the builder automatically sequences them against current pAMM state, re-simulating submissions on every quote update to ensure orders are filled at the latest available price.

### What ETHGas offers with ACE <a href="#what-titan-offers-with-ace" id="what-titan-offers-with-ace"></a>

Historically, If a maker posts a quote too early the price may be stale by the time the taker flow lands, allowing takers to benefit from any mispricing. Alternatively, if takers are forced to choose a route before the final block state is known they would have to route against a stale price, leaking value to makers.

ETHGas solves this at the builder layer:

* Makers stream low-latency quote updates to the builder
* Stale quote updates are replaced, so only the latest applicable quote is considered
* When a taker trades against a pAMM, the latest quote update is guaranteed to be ranked before it in the block
* Makers can configure freshness protection so takers are only eligible for inclusion against sufficiently recent quote state
* Takers can submit multiple candidate routes through pAMM and constant-function market makers (CFMM) liquidity
* The builder evaluates candidates against live state at build time and re-evaluates on every pAMM quote update right up until the point of inclusion

This gives pAMMs on Ethereum a new set of advantages. Rather than relying on public propagation and protocol level ordering behaviour, the maker gets an explicit builder-enforced priority rule around its own pool. That priority applies both to rank in the block and to the timing relationship between quote and taker receipts. For takers, the builder becomes the place where pAMM and CFMM pricing can be compared against the latest available state.

The result is a more deterministic execution environment for active liquidity, that has the potential to offer tighter quotes than any CEX or propAMM chain. For this reason, we soon expect Ethereum to offer the industry’s most competitive prices on major pairs.

### Integration paths <a href="#integration-paths" id="integration-paths"></a>

There are three main integration surfaces:

1. Makers stream quote updates to ETHGas through the pAMM quote WebSocket. Quotes can land every block, or only when there is taker flow, depending on the maker session configuration.
2. Takers submit candidate bundles through the normal bundle path. A candidate can route through existing CFMM liquidity, pAMM liquidity, or both. The builder evaluates all candidates against the freshest available pAMM state.
3. Takers can also consume the pAMM state stream when makers opt in. The stream publishes flattened Ethereum state override objects, making it easier for searchers, solvers, and aggregators to simulate pAMM routes locally before submission.

The following pages describe the maker and taker interfaces in more detail.

<br>

<br>

<br>

<br>


---

# 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.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.
