Parallax

Problem Statement

In this, the users only send intents to a Dispatcher contract in EIP2162 fashion. That dispatcher is then called by a keeper (some EOA) in a cron job to dispatch them to BatchSolver contract. There, the multiprocessor processes the intents parallelly, one for each pair. They solve coincidence of wants, and do a single transaction to UniSwap V2 to get the remaining tokens. Then, these outputs are sent back to users and 0.5% fees to the keeper.

Solution

This project uses Arcology's Concurrent Library and Hardhat 3 for development environment and scripts. Since the PS required no frontend, only scripts from Arcology's part, Hardhat was the excellent choice for this project. Second, due to the low complexity of Arcology's concurrent contracts, I easily wrote my custom data type (IntentStruct Array) for this project.