- autopilot, which will be configured to point, for example, to the production orderbook and to send the auctions to a local driver.
- driver, which will receive auctions from the autopilot and forward them to the solver engine
- the solver engine that is meant to be tested, run as a local http server able to receive
/solverequests from the driver and respond to them.
Locally testing a solver with the CoW Protocol orderflow
CoW Protocol infrastructure is a lot of services running together in herd harmony, which is a bit intimidating at the beginning. Before proceeding, it would be advisable to read the architectural overview to get a better understanding of how CoW Protocol works and its entities.
In order to test a solver against CoW Protocol’s orderflow, one needs to locally run the following components
where one needs to set the NODE_URL appropriately (e.g., a free Infura endpoint).
For the driver, we run
where one needs to configure driver.config.toml to point to their solver engine. A sample such file can be found here.
Once the above are set up and running, one can then start testing their solver engine against one of the following orderbooks:
Last modified on March 17, 2026