Comment on page
The Batch Auction Optimization Problem
In this section, we describe all the different components of the optimization problem that needs to be solved within each batch.
Suppose that there are
tokens. From a high-level perspective, we can define a user order as an acceptance set
specifying the trades a user is willing to accept (where negative entries of a vector represent tokens sold, while positive entries represent tokens bought). So, for example, if
then a user is happy to receive x units of token 1 in exchange for y units of token 2 (note: this is all from the user's perspective and is therefore net of fees).
, that is, a user is always willing to accept an order in which they receive a positive amount of tokens without paying anything. Similarly,
because no user would accept to pay tokens without receiving anything. The interesting elements of the acceptance set are, therefore, those with at least one positive entry and at least one negative entry. We also assume that
, that is, when submitting an order a user accepts that the order may not be filled.
To each order
we may assign a utility function
specifying a numerical value to each trade in the acceptance set, to be interpreted as "how good" a trade is from the point of view of the user who submitted order S. By definition
Practically speaking, CoW Protocol allows only some types of orders, which we can think of as constraints on the set S that a user can submit. One such constraint is that only pairwise swaps are allowed, that is, all vectors in
have zeros in
dimensions. Furthermore, each order must fit within one of the categories we now discuss. To simplify notation, when discussing these categories we assume that
A limit sell order specifies a maximum sell amount of a given token Y > 0, a buy token, and a limit price
, that corresponds to the worst-case exchange rate that the user is willing to settle for. They can be fill-or-kill whenever the executed sell amount must be Y (or nothing). They can be partially fillable if the executed sell amount can be smaller or equal to Y. Formally, if x denotes the (proposed) buy amount and y denotes the (proposed) sell amount of the order, a fill-or-kill limit sell order has the form
and a partially-fillable sell order has the form
In both cases, the utility function is defined as
is the additional amount of buy tokens received by the user relative to the case in which they trade at the limit price, and
is the price of the buy token relative to a numéraire (in our case ETH) and is externally provided (i.e., by an oracle). The function
is therefore expressed in units of the numéraire and is always non-negative.
A final observation is that orders can be valid over multiple batches. For a fill-or-kill, this means that an order that is not filled remains valid for a certain period (specified by the user). For a partially-fillable order, this also means that only a fraction of it may be executed in any given batch.
Limit Buy Orders
A limit buy order is specified by a maximum buy amount X > 0 and a limit price
corresponding to the worst-case exchange rate the user is willing to settle for. With x denoting the buy amount and y denoting the sell amount of the order, fill-or-kill limit buy orders have the form
while partially-fillable limit buy orders have the form
Again, the utility function is defined as
is the price of the sell token relative to a numéraire and is externally provided. Also here, orders can be executed over multiple batches.
Liquidity orders are orders not submitted by users. They represent sources of liquidity that are available to a solver, for example, automated market makers or private liquidity pools. They look identical to user orders, in the sense that each liquidity order can be represented by an acceptance set
. The main difference to user orders is that the utility function of a liquidity order is always zero.
Each user order has an associated fee paid to the protocol. At a high level, these fees can be represented by a function that, for a given order
maps all possible trades to a positive vector of tokens, that is
From the practical viewpoint, for market fill-or-kill orders, the fee is always in the sell token and is pre-specified: it is an estimate of the cost of executing an order and is explicitly shown to the user before the order is submitted. Instead, (long-standing) limit orders are "feeless" from the user's perspective: users are guaranteed a limit price without specifying how fees will be calculated. For fill-or-kill limit orders, the protocol computes a fee each time such an order enters a batch auction, while for partially-fillable limit orders, solvers are the ones that need to propose a fee. In this latter case, the expectation is that this fee should equal the cost of execution of this trade in isolation. The fee of limit orders is again in the sell token.
Solvers propose solutions to the protocol, where a solution is a set of trades to execute. Formally, suppose that there are
users and J liquidity sources. A solution is a list of trades
one per user and one per liquidity source such that
- Maximum size of solution: The total number of executed orders and AMMs does not exceed a certain number within each batch due to limitations regarding the size of a block on the blockchain.
- Incentive compatibility and feasibility: the trades respect the user and liquidity orders, that is,and.
- Uniform clearing prices: all users must face the same prices. Importantly, this constraint is defined at the moment when the swap occurs. So, for example, suppose user i receives x units of token 1 in exchange for y units of token 2 and that the protocol takes a fee in the sell token. Defineas the price at which the swap occurs. Uniform clearing prices means thatis the same for all users swapping token 1 and token 2. Furthermore, prices must be consistent, in the sense that for any three tokens 1, 2, and 3, ifare well-defined, then it must be that. Note that this implies that prices can be expressed with respect to a common numéraire, giving rise to a uniform price clearing vector.
- Token conservation per token: No token amounts can be created or destroyed. In other words, for every token, the total amount sold must be equal to the total amount bought of this token.
- Social consensus rules: These are a set of principles that solvers should follow, which were voted by CIPs. They are specified on the page Social Consensus Rules.
Note that systematic violation of these rules might lead to penalizing or even slashing (if the DAO decides so).
From the protocol viewpoint, each solution that satisfies the above constraints has a quality given by the sum of the utility generated, and the fees paid to the protocol:
where p is a vector of externally-determined prices used to express all fees in terms of the common numéraire.
Finally, solvers compete for the right to settle a batch by participating in an auction, aiming to implement the solution with the highest quality at the lowest possible cost to the protocol. For more details, see the page Solver Auction and Rewards.