Pammswap: a frontend for propAMMs
Published 2026-11-10 · quotes sampled
tl;dr
Pammswap (pammswap.com) is an experimental swap app for propAMMs on Ethereum mainnet.
What is it?
A couple of months ago I dug into the evolving landscape of proprietary AMMs (propAMMs), which at the time were seeing rapid growth. That has since stabilised, with propAMMs accounting for
The primary "go-to-market" for propAMMs is via aggregators who can tap into their price feed and route swaps accordingly. But what if I, as a user, want to trade with one of these mythical things?
Introducing Pammswap, a frontend for Ethereum's propAMMs.
Pammswap is a preview and has not been audited. Use small sizes, and please send feedback or bug reports: adam@azfuller.com
Here is one illustrative trade, buying about 0.45 ETH with 1,000 USDC:
Buying ETH with 1,000 USDC on
The same trade as the app's market table
Route is where the output comes from: a pAMM fills directly, the AMM fallback is Fynd's route across the onchain pools it names. The router sweep is listed as the app shows it: priced at the best streamed pAMM quote, with the gas of quoting three venues onchain, and never ranked.
How does it work?
Trading on propAMMs is a bit more involved than trading on an onchain AMM. Firstly, you need access to their offchain pricing. Thankfully, Titan aggregates pricing from multiple propAMMs in one standardised and easy-to-consume stream. Secondly, you need to be able to execute trades. While there has been some standardisation of propAMMs, encouraged by the Lambda team's standard interface, there is still some variability, and that interface itself is optimised for other contracts, rather than end-users. Finally, you need a fallback. Most of the largest block builders do support propAMMs (by ensuring that their price update goes in before any user trades), but a meaningful share of blocks won't have a price update, so you need to work out what happens in that case.
These nuances mean we can't just build a simple frontend. The first requirement is a router contract. The Pammswap router lets you pass in one or several propAMMs for a swap (with the best price at swap-time determining the chosen venue). If pricing is unavailable or if it doesn't achieve the user's minimum output, a swap can optionally include a fallback route, which uses Fynd's routing (PropellerHeads' aggregator, restricted here to onchain pools, which the app attaches to every swap when it is available). Passing in the fallback, rather than using an AMM (such as Uniswap V3 in the Lambda router) gives us a bit more flexibility as well as better fallback pricing for users.
We also need a server. The server streams propAMM pricing updates from Titan, and fetches quotes from Fynd based on a user's request. Quotes from both propAMMs and Fynd can be simulated to check for correctness and gas usage. The app could theoretically do these kind of things on the frontend, but given the amount of streaming data, it is simpler to do it on a server.
Finally, the application. The app has a swap UI which is familiar to users of meta-aggregators, just with exotic-sounding propAMM names to choose from. We make some opinionated choices, for example ranking potential swaps by output net of the gas they will burn rather than by headline quote, and integrating ERC-5792 so that approval and swap go through in a single wallet request if a user's wallet supports it. We include a 60-second pricing chart to see how things are tracking over time.
Offchain, one Node server holds the Titan socket, asks Fynd for the best onchain route, simulates each candidate on the next block for gas, and streams the ranked market to the browser. Onchain, a normal wallet transaction goes to the Pammswap router, which fills at the best listed pAMM or runs the Fynd route through TychoRouterV3 in the same transaction.
Pammswap in practice
The biggest speedbump with Pammswap is the fact that not all block builders are able to provide propAMM pricing. It is frustrating to try a propAMM app if you can't seem to land a trade with one. But it's certainly the case that an aggregator fallback is more satisfactory than the Uniswap V3 I started with (both from a router-complexity and trade outcome perspective).
The Fynd fallback is included in the venue list to illustrate the best route available based on onchain pricing, which will often split across venues for larger trades (which can be very competitive with the propAMMs). That highlights how rudimentary Pammswap's "pick a provider" approach is, even if the simplicity is the point. Fynd does actually support routing via propAMMs, though Pammswap's Fynd quote request excludes them to make for a cleaner fallback option.
It is nice to avoid the separate "approve then swap" UX via ERC-5792, though you do bump into some rough edges. Some wallets don't trigger as expected or time out in a flakey way (my hypothesis is failed simulations), and MetaMask defaults to a healthy
Finally, the app sorts by an estimated output that includes gas costs, which I like in principle, but I am not sure how legible that is in practice, particularly with Ethereum's transaction costs at their current lows (despite a spike today).
A few swaps through the live router
The most recent swap filled by each venue, drawn from the
What's next?
Pammswap is live and ready to use, but it's very much a starting point. The housekeeping is non-trivial, ensuring that we keep up to date with Titan's feed and the range of propAMMs, whose addresses and interfaces are a moving feast. I have been experimenting with a gasless path which ensures delivery to a compatible builder, and there might be more interesting ways to route or fallback, beyond the simple picker. It is tempting to extend to other chains, despite their very different propAMM architectures. And there are always ways to polish and streamline the user experience.
Pammswap is just a science experiment today, but it gives us end-users a way to trade via propAMMs. Try it out now!
Method
Method and data files
Quotes come from pammswap.com's public stream endpoint. The sampler opened 18 trades at once (six pairs at roughly $1k, $10k and $100k), held each stream until the market was live and every ranked quote had measured gas, and kept the last event. It ran six rounds. The animation and its table show one trade from the first round, 1,000 USDC to ETH, as an illustration. Nothing was signed or executed.
Net value is quoted output minus swap gas, using the server's simulated gas for that venue priced at the stream's gas price. This is the same arithmetic the app uses to rank. Fynd's row is the app's AMM fallback, Fynd's best route through onchain pools alone, with pAMM and RFQ legs excluded from the quote request. The router sweep row in the table is modeled, not quoted. Quotes more than 3% below the best are flagged as collapsed and left out of the ranking.
The share of DEX volume uses the propAMMs memo's method: pamm.wtf's daily volume by venue over DefiLlama's Ethereum DEX daily volume, full weeks and months only. DefiLlama lists FermiSwap, so the denominator already contains part of the numerator.
Router history is read from the event logs of the two Pammswap routers on mainnet. The retired first router filled one swap. The live router records the quoted output in each Swapped event; realised against quoted is computed from that. Each swap's priority fee is its receipt's effective gas price less the block base fee. A swap sent to the payer's own address rather than the router is counted as going through an account contract.
Data files:
Pipeline and QA checks: pipelines/pammswap/ in the memos repository.