Detecting the Order

The first step in the solver workflow is highlighted with a green background in the diagram below.

Solver's steps - Detecting the Order

Solvers monitor the DlnSource contract for the CreatedOrder event:

event CreatedOrder(
    Order order,
    bytes32 orderId,
    bytes affiliateFee,
    uint256 nativeFixFee,
    uint256 percentFee,
    uint32 referralCode
);

This event emits an Order struct, which provides the information necessary to either fulfill or cancel the order. Further details about the Order structure can be found here.

Solvers evaluate whether an order is worth fulfilling based on its profitability. To ensure orders are attractive to solvers, integrators must configure them so that the spread between input and wanted assets covers all associated costs, including operating expenses and all of the fees. Additional considerations around profitability are discussed in the following section.