Big crypto orders don’t just hit a pool and hope. They hunt for liquidity across AMMs, RFQ market makers, and sometimes private lanes most people never see. If you’ve ever tried to move size onchain and watched price wiggle away from you, this is for you.
We’ll break down how onchain RFQ actually works, how it stacks up against AMMs, where aggregators source fills, and the traps that clip big orders. I’ll also point to fresh datasets that trace the exact path your swap took, so you can verify where size really came from.
Why now? Onchain liquidity is maturing fast. Tokenized Treasuries and money market funds are now a huge footprint on public chains, a sign that bigger players are comfortable parking size onchain — and they expect pro-grade execution when they trade.
Large traders increasingly use onchain RFQ (request-for-quote) to get firm quotes from market makers and minimize price impact, while AMMs remain the default for smaller or long-tail tokens. Aggregators route between the two based on size, depth, and slippage settings, often splitting the order. In short: AMMs price continuously, RFQ quotes discretely; whales blend both.
- AMMs shine for instant fills and long-tail assets; slippage rises with size.
- RFQ gets you firm quotes from PMMs/solvers, often with better net price for big tickets.
- Aggregators decide route in real time and may split across AMMs and RFQ makers.
- MEV, gas, and expiry windows matter; private lanes can protect large orders.
- Use orderflow tools to confirm if your fill was AMM or RFQ-sourced.
How does onchain RFQ actually work?
RFQ is simple in spirit: you ask a network of market makers for a quote; they answer with prices; you pick the best and settle onchain. The wrinkle is coordination. Quotes might be computed offchain by PMMs (professional market makers) or solvers, then committed onchain via a small contract call. That’s why you’ll hear people say RFQ is hybrid. Discovery offchain, settlement onchain.
For a large trade, you or an aggregator package the order context: token pair, size, side, max slippage, and sometimes hints about hedging venues. Makers respond with a price that factors in their inventory, hedging routes (CEX, perps, correlated pairs), and the gas they’ll pay. If you accept, the maker executes the settlement transaction or signs a message you can settle yourself.
Good RFQ flows also include protections: quote expiry (seconds), match-ahead rules to prevent sandwiching, and sometimes private relay submission so the quote isn’t broadcast to searchers before it lands in a block.
What really separates RFQ from AMMs for size?
AMMs price along a curve. Push size through and you slide down that curve. RFQ makers don’t reprice on a curve; they price your exact order, then try to hedge it. That difference matters when you’re trading size in thin markets.
Here’s a tight comparison that captures the main trade-offs:
Topic AMM Onchain RFQ Price formation Continuous curve from pool reserves Discrete quotes from makers/solvers Slippage on large orders Rises nonlinearly with size Embedded in quote; often lower for big tickets MEV exposure Higher if public mempool Often reduced via private lanes or committed quotes Settlement Direct pool swap Maker or solver contract executes onchain Counterparty Pool LPs, permissionless Named or whitelisted PMMs/solvers Long-tail tokens Often the only route May be unavailable or wide spreads Privacy Public unless using private RPC Negotiation offchain; onchain settlement visible Operational overhead Low, click-and-swap Quotes, expiries, signatures, and routing logic
In practice, aggregators blend both. They’ll test a small “warm-up” amount on AMMs to probe depth and price, ping RFQ makers for firm size, then split the order. You get a composite fill that hides a lot of moving parts.
When should I split a large order?
Not every big trade needs to be chopped up. If the pool is deep and the pair is blue-chip, a single bite might be fine. But most of the time, splitting helps reduce impact, smooth execution through volatility, and keep your intent less obvious.
Here’s a quick checklist I use before slicing an order:
- Depth vs size: If your order is over 1–2 percent of visible AMM depth at target slippage, consider RFQ or splitting.
- Volatility: Fast markets favor staggered fills or RFQ with short expiries.
- Routing options: If aggregators show multiple viable paths, splitting usually pays.
- Gas math: Several small fills can cost more gas than one RFQ. Compare net price, not just spot.
- Privacy: Use private submission for the bigger chunks to cut MEV leak.
Time-weighted strategies (TWAP) still matter onchain. Many solvers can schedule chunks across blocks while monitoring quotes. Just set your max duration so you’re not chasing a moving target for hours.
How do aggregators and solvers pick between AMM and RFQ?
Aggregators watch two streams: public AMM quotes and private RFQ responses from makers. They simulate fills with gas, route risk, and slippage. If an RFQ quote beats the best simulated AMM path after costs, they’ll take it. If the RFQ is stale or too wide, back to pools they go.
We can actually see this distinction now in public data. Allium’s DEX Analytics schema surfaces separate views for dex.trades (AMM pool fills) and dex.aggregator_trades (fills routed via aggregators, intent systems, and RFQ/PMM liquidity), which lets researchers tell how a swap was really executed (DEX Analytics (Allium)). Their Orderflow Explorer maps the full path of a swap across EVM chains — frontends, meta-aggregators, solvers or PMMs, then the final AMM pools if used — a clean way to trace where large trades actually sourced liquidity (DEX Analytics (Orderflow Explorer)).
It’s not just execution nerds looking. Allium was also cited as the primary on-chain data source in Bitwise’s inaugural Q3 2026 Staking Report, a small but telling sign that mainstream research is leaning on this type of orderflow clarity (Allium (Press & News listing / The Onchain Query)).
Pro tip: If an aggregator lets you, log or export the route. Later, compare it to Allium’s path view to verify whether your price came from AMM depth, a solver’s RFQ quote, or both. It’s the easiest way to sanity-check execution quality.
What about MEV, gas, and settlement risk?
For AMMs, the main pain is MEV if you’re broadcasting a juicy swap. Sandwiching can widen your effective cost. Private RPCs and protected builders help, and many frontends now default to them for bigger trades. RFQ paths often push settlement via private lanes by design, which takes a lot of the sting out.
Gas is more straightforward. A single RFQ fill can be cheaper than multiple hops across pools, but not always. Hops and approvals add up. On volatile days, a maker might factor gas into their quote, so it’s reflected in the price you see. Always compare net-out, not just the headline spot.
Settlement risk is rare but real. With AMMs, you face smart contract risk and pool price movement between submission and inclusion. With RFQ, you add quote expiry and counterparty behavior. If a maker’s hedge slips, they can cancel or requote. Tight expiries and clear failure rules help, and good aggregators enforce them automatically.