If you have only ever used a centralized exchange, terms like "market order" and "limit order" probably feel familiar. If you have only ever swapped tokens on a decentralized exchange, you may never have needed those terms at all, because a normal DEX swap is already a market order. It just doesn't announce itself that way.
Understanding the difference matters because it explains what you are actually agreeing to every time you tap "swap," and it clarifies what options exist if you want more control over the price you get.
What a market order is
A market order is an instruction to execute immediately at whatever price is currently available. You are not naming a price. You are saying "I want this trade done now, at the best price the market can currently give me."
Every standard swap on a Base decentralized exchange works this way. When you swap ETH for USDC using an automated market maker (AMM) style pool, the pool's smart contract calculates the current exchange rate based on the ratio of assets in the pool at that exact moment, then executes your trade against that rate. The only real controls you have are the amount you're trading and your slippage tolerance, which sets how much the price is allowed to move between the moment you confirm and the moment your transaction actually lands on chain.
That is a market order, even though most wallets and swap interfaces never use the term. The trade either executes near the price you saw on screen, or it fails because the price moved outside your slippage tolerance and the pool's math rejected it. For more on why that quoted price can shift by the time your transaction confirms, see our explainer on price impact vs. slippage.
What a limit order is
A limit order is different. Instead of accepting whatever price is available right now, you set a specific price you are willing to accept, and the order only executes if the market reaches that price. A limit order to sell ETH at a certain USDC price will sit unfilled until (and unless) the market gets there. If it never gets there, the order simply never executes.
On centralized exchanges this is straightforward: the exchange runs an order book and matches your order against someone else's when the prices line up. On a decentralized, non-custodial system, it is more complicated, because there is no central party holding your funds and watching the order book on your behalf. Your funds either need to stay in your own wallet until conditions are met, or be placed under a smart contract that only certain, predefined actions can trigger.
Why most Base DEXs default to market orders only
Basic AMM pools, the kind that power most swaps on Base, were not built with limit orders in mind. Their pricing comes from a constant formula based on pool reserves, not from a list of resting buy and sell orders. Executing a trade only when a price target is hit requires additional infrastructure sitting on top of, or alongside, the AMM: something that watches prices and triggers the trade at the right moment, or a separate off-chain order relay that submits the transaction on your behalf once conditions are met.
Building and securing that infrastructure is nontrivial, which is why limit order functionality has rolled out unevenly across the Base ecosystem rather than being a default feature everywhere.
Where limit orders exist on Base today
A few protocols have built dedicated limit order infrastructure that includes Base. The 1inch Limit Order Protocol, for example, has been deployed on Base and lets users set a target price and duration for a trade; the order sits until the market reaches that price or the order expires, and it can be filled by other participants or by 1inch's own aggregation routing. Other aggregators and protocols have shipped or announced similar mechanisms on various networks, though availability and feature depth differ from one product to the next and continue to change over time.
If a limit order feature matters to you, the details worth checking before you use it are:
- Custody during the wait. Does your order require your tokens to be held by a contract while it's open, or can they stay in your own wallet until execution? Understanding what a token approval actually grants is relevant here too.
- Who can fill the order, and how. Some designs rely on third party "fillers" competing to execute your order, which affects how reliably and how quickly it gets filled once your price is hit.
- What happens if it partially fills or expires. Ask whether an order can execute partially, and what happens to the unfilled portion when it expires.
- Fees. A resting order that eventually fills may carry a different fee structure than an instant swap.
A practical way to think about it
Neither order type is inherently better. A market order is simple, transparent, and executes right away, which suits most everyday swapping. A limit order suits a specific goal: you have a price in mind and you are willing to wait, possibly a long time, for the market to reach it, in exchange for not having to watch it yourself.
What matters most is knowing which one you're actually using. If an interface lets you type in an amount and a "swap" button executes right away, you are placing a market order and accepting the current price, adjusted by whatever slippage tolerance you've set. If an interface asks you to name a target price and a duration, you're placing a limit order, and your trade may not execute at all if the market never gets there.
Base's DEX ecosystem is still evolving, and limit order tooling is one of the areas most likely to expand as more protocols build on the network. Whichever type of order you use, the same fundamentals apply: verify the contract you're interacting with, understand what you're approving, and don't commit more than you're comfortable leaving exposed to how the trade actually plays out.