When your team swaps on cowswap, it signs an order stating what it will sell and the least it will accept. CoW Protocol groups that order with others, then solvers compete to settle it on-chain. For a treasury conversion before payouts, the useful result is the amount that actually arrives, not the initial quote.
Three points guide the trade:
- The signed minimum protects the team if the price moves before settlement.
- Solvers may match orders directly or draw liquidity from exchanges.
- The swap converts assets; the team still has to make and reconcile its payouts.
What does your team submit?
Your team submits a signed trade intent: the asset to sell, the asset to receive, an amount, a minimum acceptable return and an expiry. The signature authorizes settlement under those conditions; it does not itself move the tokens. The team needs the sell asset in its wallet on the chosen chain and, for an ERC-20 token, sufficient spending allowance for settlement.
Suppose a treasury holds ETH but needs USDC for supplier payouts. CoW Swap gives the team a way to seek that conversion without choosing a liquidity pool or trade route itself. At that point, cowswap.dev lets the team route the swap through CoW Protocol’s solver auction, where solvers seek liquidity across DEXs and reduce exposure to MEV, or value extracted by manipulating transaction order. Before signing, the team should check the chain, token contract addresses, sell amount and minimum USDC it will receive.
The minimum matters more than a displayed exchange rate. Say a quote estimates 50,000 USDC for 25 ETH and the team accepts up to 0.5% less: a signed minimum of about 49,750 USDC sets the floor for that order. The figures are illustrative; the team should calculate its floor from the current quote and its actual payout requirement.
How does the solver auction settle the swap?
The auction asks solvers to find a valid way to fill orders in a batch. A solver might find a Coincidence of Wants: another order wants to sell USDC for ETH, allowing the two sides to trade without sending the full amount through a liquidity pool. Otherwise, solvers can use available exchange liquidity and combine routes to meet the signed terms.
Solvers compete on the value their solutions deliver to users, subject to the protocol’s auction rules. A winning solution is submitted as an on-chain settlement transaction. The treasury’s order executes only if that solution respects its limit price and other signed conditions; a quote alone does not reserve a rate.
Batch settlement also changes the team’s MEV exposure. With cowswap, the team signs an off-chain order instead of broadcasting its own swap transaction to a public mempool, where a bot could try to trade around it. Orders for the same token pair and direction within a solution use a consistent clearing price, so their order within that settlement cannot be used to give one of them a worse price.
Matching another trader is an opportunity, not a condition for execution. If no suitable opposite order appears, a solver can still fill through outside liquidity. If no solution can meet the signed minimum before expiry, the order remains unfilled rather than settling at a worse rate.
What will it cost, and why might an order remain open?
The cost that matters to a treasury is the net amount received after execution costs and any applicable protocol fee. The solver pays to submit settlement on-chain and accounts for that cost in the trade’s economics; an ERC-20 approval, if needed, is a separate on-chain transaction that the team pays for in the chain’s native token. Fees vary with the network, gas conditions, token pair and trade size, so compare the current net quote with the amount required for payouts.
Basis points help make a fee comparable across trades: 10 basis points is 0.10%, or $50 on an illustrative $50,000 trade. That percentage says nothing about the exchange rate or price impact. A large order against thin liquidity can lose more value through its execution price than through a stated fee.
An order may stay open because the market moved beyond its minimum, liquidity is too thin, or the remaining amount is uneconomic to settle. CoW Swap market swaps and limit orders also serve different needs: a market swap seeks execution around a current quote, while a limit order waits for a chosen price and may allow partial fills. For a payout deadline, decide in advance how long the treasury can wait before reviewing an unfilled or expired order.
How should the team finish a treasury conversion?
Run the conversion against the payout obligation, then record what settled. If the team owes 49,800 USDC, the illustrative 49,750 USDC minimum above is too low even though it limits slippage to 0.5%. The team would need a higher minimum, more ETH to sell, or another source for the shortfall.
For a routine cowswap run, the treasury record should contain:
- The chain, sell and buy token contract addresses, and wallet that will receive the proceeds.
- The signed sell amount, minimum received and order expiry.
- The settled token amounts, execution fee and on-chain transaction reference.
- The USDC balance available for payouts after settlement.
Only the settled balance should enter the payout schedule. A successful swap puts the purchased token in the receiving wallet; it does not send individual supplier or payroll transfers. Start by setting the USDC amount the team must have after fees, then assess a live quote and sign only an order whose minimum still covers that amount.
Top comments (0)