Cowswap

Cowswap lets you choose between a quoted swap and a limit order.

Last updated -

Cowswap lets you exchange tokens through a quoted swap or set an acceptable price with a limit order. Both use CoW Protocol, where competing solvers find ways to execute signed trading instructions. A swap suits a trade whose displayed terms you accept now. A limit order can wait for suitable conditions until its expiry. Neither a quote nor an accepted order confirms that tokens have changed hands. The choice also involves partial fills, execution costs, and the destination network. Scheduled trading and cross-chain swaps address different needs, with additional requirements that affect when the trade counts as complete.

Swaps, Limit Orders, and Scheduled Trading

A swap and a limit order differ mainly in how you choose the acceptable execution price. Market conditions can change while either order awaits settlement. A quoted swap must fill in full in one settlement, while a limit order can fill across several settlements if partial fills are enabled.

Quoted Swaps and Target Prices

A quoted swap presents an expected exchange outcome for the selected tokens and amount. Its slippage tolerance defines how much adverse movement the order permits. Signing authorizes execution within those terms; it doesn’t reserve the displayed quote indefinitely. The expected amount is an estimate; the minimum received amount sets the lowest acceptable output for the specified sell amount.

A limit order expresses a price boundary directly. A buy limit sets the maximum acceptable purchase price; a sell limit sets the minimum acceptable sale price. Its validity period determines how long the instruction remains available for execution. A stricter price can mean a longer wait or no fill before expiry.

Trading in Scheduled Parts

Time-weighted average price, or TWAP, orders divide a trade into parts over time. This can reduce the price impact of executing the entire amount together, while exposing later parts to later market conditions. The TWAP interface requires a Safe wallet with the required fallback handler. Its settings include the number of parts, total duration, and price protection. Each part must satisfy the applicable execution conditions; scheduling doesn’t promise a better final average price.

What Does Signing an Order Authorize?

Signing a standard token order authorizes execution under its specified terms, while token approval separately permits the designated contract to spend the sell token. These permissions have different jobs. An approval alone doesn’t select the purchase token or complete a trade. Before signing, review the token amounts, recipient, expiry, and price boundary. The spender address belongs to the approval check; the recipient belongs to the order check.

For standard ERC-20 orders, the settlement contract checks the signature and execution conditions before the vault relayer pulls tokens. A broad allowance can remain available beyond one trade. Its size therefore deserves a separate decision from whether the particular order looks acceptable.

Why Can a Limit Order Stay Open at Its Target Price?

A limit order can remain open because executable liquidity must cover its price requirement and execution costs. A market chart touching the target doesn’t establish that the specific order can settle. The interface’s execution-price estimate reflects changing network fees, order size, and market conditions. Your signed limit remains the order’s boundary, while that estimate can move. A brief price touch may also disappear before execution becomes possible.

Why Can a Limit Order Stay Open at Its Target Price?: A limit order can remain open because executable liquidity must cover its price requirement and execution costs.; A market chart touching the target doesn’t establish that the specific order can settle. The interface’s execution-price estimate reflects changing network fees, order size, and market conditions.; Your signed limit remains the order’s boundary, while that estimate can move. A brief price touch may also disappear before execution becomes possible.
Why Can a Limit Order Stay Open at Its Target Price? - diagram.

View image file

Batch Auctions and Execution Costs

Solvers search for ways to satisfy orders through available liquidity and compatible trades. CoW Protocol uses batch auctions in which solvers compete to settle trades. Matching opposing trading needs can reduce reliance on liquidity pools. Orders that don’t find such a match can still use external liquidity. This structure provides protection against certain forms of maximal extractable value, or MEV, without making an unfavorable market price favorable.

Execution costs also affect the choice between order types. Protocol fees can include volume-based charges and charges linked to surplus or quote improvement. The applicable policies determine how much improvement reaches the trader. Fees can appear within the executed token amounts rather than as separate wallet transfers. Compare the net exchange outcome for the same tokens and amount; a gasless signature doesn’t establish a cost-free trade.

Delivery Across Networks

Cross-chain swaps add a destination-network transfer after the source-network swap. Their completion therefore requires more than a successful source transaction.

Destination Availability

The selected source token affects which destination networks the interface offers. On a different destination network, the bridge provider determines the available output tokens. A familiar token symbol doesn’t establish that every network combination works. The documented cross-chain interface supports swap orders between different tokens on different networks. It excludes limit orders, smart contract wallets, and same-token bridging.

The quote separates the swap outcome from bridge costs and estimated delivery time. Those estimates depend on the selected route and provider. The destination minimum received amount is the relevant boundary when the task requires funds on another network.

Swap Settlement and Destination Receipt

Bridging starts after a successful swap. Once the bridge deposit has been submitted, the transfer can’t be canceled through the swap interface. It completes or follows the provider’s refund policy. If a refund arrives in your Account Proxy, the helper contract used for bridging, recover it to your wallet before retrying with those funds. A completed source swap can therefore coexist with delivery still in progress. The destination receipt establishes arrival; a source settlement alone doesn’t.

How Do You Decide Whether to Retry?

Retry only after the existing order’s status and executed amount show what remains unfinished. Suppose a signed token order hasn’t delivered the full intended amount. Judge a quoted swap and a limit order by the same measure: the amount that actually settled under the authorized terms. A refreshed quote or changed execution estimate describes a new opportunity, not the outcome of the earlier order.

  • If the order remains open, account for its ability to execute before submitting an overlapping replacement.
  • If a partially fillable limit order executed in part, reconcile the completed fills and remaining sell amount.
  • If the order expired, inspect its execution record before treating the full original amount as available for retry.
  • If you requested cancellation, confirm the resulting status because settlement can win the race.
  • If the intended amount settled, confirm receipt by the intended recipient before continuing. For a cross-chain swap, confirm receipt on the destination network.

CoW Explorer combines order-book information with settlement data, so an order record and a transaction answer different questions. After confirming an unfinished amount, the next choice is whether to accept a fresh swap quote or retain a target price. Network costs and executable prices may have changed; the replacement still needs terms that match the remaining task.

Native Tokens and Wrapped Balances

Selling a network’s native token adds a different authorization path because standard CoW Protocol orders sell ERC-20 tokens. Wrapping requires an on-chain transaction and gas, and creates an ERC-20-compatible balance that can use the ordinary approval and order flow. The alternative Eth-flow contract combines wrapping with order placement through an on-chain transaction. That path requires upfront gas, which doesn’t return if the trade fails. The interface offers Eth-flow for swaps rather than limit orders, and doesn’t offer it for smart contract wallets.

A native-token deposit into Eth-flow establishes order placement before the purchased tokens arrive. Failed orders can refund the deposited native tokens, while transaction gas remains spent. The next decision therefore starts with the balance you hold and the order type you need: a wrapped balance for a limit order, or an available native-token swap path with its transaction requirements.

Still have questions?

Are Orders Private Because Signing Happens off-chain?

Off-chain signing doesn’t make an order anonymous. CoW Explorer exposes order information and lets users search by wallet address, order identifier, or settlement transaction. The protocol’s protection against trading exploitation addresses a different concern from hiding wallet activity. An order that avoids direct submission to the public transaction mempool can still leave publicly inspectable order and settlement records.

Do I Need Gas for Every Token Approval?

Some supported tokens allow approval through a signature rather than a separate approval transaction. Availability depends on the token and wallet path. The interface identifies eligible gasless approvals for swap and limit orders, while its documented gasless-approval flow excludes smart contract wallets. A regular approval transaction still requires network gas. Approval costs and the costs included in trade execution are separate.

Does Canceling a Limit Order Require a Transaction?

A limit order supports off-chain cancellation without a network transaction, or on-chain cancellation that costs gas. Off-chain cancellation relies on the order service processing the request. On-chain cancellation records invalidation through a transaction. Neither request takes effect instantly, and the order may settle before cancellation becomes effective. The cancellation method therefore changes the mechanism and cost, rather than guaranteeing that a pending trade will stop.

Why Does a TWAP Order Remain in the Signing State?

A TWAP order can remain in the signing state because its Safe wallet still requires additional owner signatures. Initial submission doesn’t complete the wallet’s authorization requirement. After the required signatures and on-chain submission, the order can become active. That active state concerns the scheduled order; individual parts have their own execution records and may remain unfilled when their conditions aren’t met.

Can cross-chain Output Go to a Different Recipient?

Cross-chain swaps support a custom recipient address on the destination network. The connected wallet is the default recipient, and the custom-recipient setting accepts a full wallet address rather than an ENS name. The destination address belongs in the trade review because it determines who receives the output. Choosing another recipient doesn’t expand the networks or tokens available for the selected source asset.