PropAMMs: pushing Ethereum to the next level of finance
At LambdaClass we're pushing Ethereum to become the world's financial hub, and we think PropAMMs are key to getting there. Titan Builder introduced the features that made PropAMMs possible on Ethereum in May 2026, and since then the ecosystem has been building around them to foster adoption of this new DeFi primitive. We're building open source tools to make integrating and accessing them effortless: an SDK that quotes against the live liquidity makers are streaming rather than stale onchain state, and a Router that gives you a single point of access to every PropAMM, with onchain requoting and fallbacks that make each swap better.
The model is already working at scale. So far, $546M+ has traded across 68k+ swaps, and on the major pairs (BTC, ETH, and stables) PropAMMs are quoting tighter than Binance and major DEX venues on several pairs and price ranges.
How do PropAMMs work on Ethereum?
Ethereum's state is updated every 12 seconds, when a new block is proposed. The idea behind PropAMMs is to let market makers update their quotes far more frequently than that. Makers stream fresh quotes hundreds of times per block, adjusting to external conditions such as a crash or a price spike. Block builders read this stream and only write a quote update onchain when there's a transaction that wants to swap with the PropAMM, including the most recent update for that block. Because makers no longer carry the risk of stale prices, they can tighten spreads and improve their quotes.
This is where block builders come in: by reading maker streams and including fresh quotes at build time, they've made PropAMMs viable on Ethereum in the first place. Our goal is to build on top of that work and make it easy for anyone to integrate and access PropAMMs.
PropAMMRouter
Introducing PropAMMRouter, a single point of access to every PropAMM on Ethereum. Instead of integrating each venue separately and maintaining connections to all of them, you target one contract and reach the whole set of PropAMMs through it. On top of that single entry point, the router adds features that make the experience better for the user.
The first is onchain requoting. The user sets the minimum output they're willing to accept, and the router requotes all available PropAMMs at inclusion time and selects the best option, so they secure the best possible price rather than a quote that may have gone stale between simulation and inclusion. The second is a fallback mechanism that triggers when no PropAMM can fill the trade: in that case the router routes the swap through a regular AMM (e.g. Uniswap V3) while still honoring the minimum requirement, so a swap doesn't simply revert when PropAMMs are unavailable.
The PropAMMRouter is already deployed and operational on mainnet at 0x4DdF368080CD7946db5b459aD591c350158175e1. It's open source and built to be a public good, available to every user and DEX aggregator. The router doesn't take any fees from the swap, though there are options to charge one if an integration requires it.
You can read the full router documentation here.
The SDK
Contracts are only half the story. To make integration effortless, we shipped the propamm SDK in three languages: Rust, TypeScript and Python. All three expose the same surface, so you can quote and swap through the router in whatever stack you already work in. Each is built on tooling devs already trust: TypeScript on viem, Rust on our own rex/ethrex, and Python on web3.py.
It covers the full swap lifecycle (quote, approve, swap and waitForSwap), so going from a price to a settled trade is a few calls, not a custom integration per venue.
Its most important job is handing you an updated quote. A plain eth_call against the router only sees stale onchain state and misses the fresh liquidity makers are streaming. The SDK applies up-to-date PropAMM state overrides to every quote automatically, so the price you see reflects what makers are actually willing to fill. That's what makes swaps cheaper: you quote against real liquidity, then lock it in with the router's onchain requoting at inclusion time.
The docs have getting-started guides and examples for all three languages.
Both the contracts and the SDKs live in the public repo at github.com/lambdaclass/propamm-router-contracts.
If you want to launch your own PropAMM or integrate these tools, please fill out this form and we'll reach out.