Parameters
The parameters required for an intent can be broken down into three categories:- Batch auction parameters - those required to solve the batch-optimization problem
- Co-ordination / Settlement parameters - those required for co-ordination and settlement purposes
- Metadata parameters - those required for metadata purposes
Batch auction
- tokens to swap (i.e.
sellTokenandbuyToken) - amounts to swap (i.e.
sellAmountandbuyAmount) - kind of swap (i.e.
sellorbuy) - partial fillability (i.e.
trueorfalse) - fees payable to the protocol (i.e.
feeAmount)
Co-ordination / Settlement
- address to send the tokens to (i.e.
receiverof thebuyToken) - validity of the order (i.e.
validTo) - source of the
sellToken(i.e.sellTokenBalance) - destination of the
buyToken(i.e.buyTokenBalance)
Metadata
- application specific data (i.e.
appData)
Some parameters that are of primary consideration for co-ordination / settlement may be of secondary consideration for the batch auction. For example, the
receiver of the buyToken may be set to another address which requires storage slot to be initialized from zero, increasing the gas cost of the transaction and impacting the solution to the batch-optimization problem.