Mempool

The mempool receives transaction requests and stores them such that they are available for the execution engines. The mempool triggers the execution of transaction candidates for all transaction candidates received by any validator. Finally, it also provides partial ordering information to shards, and contributes to the dissemination of future lock requests to the state. In V1, the mempool is roughly a FIFO queue that takes transaction requests and passes them on to execution.

Components

• Workers receive transaction requests from users or solvers and keep transaction data available for executors, which they spawn for the purpose of executing transactions (in cooperation with shards). After successful execution, workers keep execution logs available.¹

• Execution Supervisors are the engines that are in charge of spawning new executor processes that workers then use to execute transaction requests.

(Wiki) links on this page

• Worker Engine
• Execution Supervisor

---

1. In V2, this will be only for a limited period of time. ↩