Understanding OpenMEV

Hi there, I am just delving deeper into this project to generate a better understanding here and from what I can see transactions that are liable to be the victim of sandwich attacks will get run through the OpenMEV ‘virtual mempool’ which is essentially just a private mempool? Is this private/less transparent mempool helpful (if I am understanding this right)? And with regards to the use of kdb+, I am assuming that it is being used to analyze the sushi data and mempool there in order to identify the at risk trades? Again this may be completely off base but Im trying to understand this better so any replies would be appreciated :slight_smile:

Hi. Thanks for your interest. Apologies for the delayed response.

All swaps can be routed through manifold’s private mempool via Sushiswap. Users benefit because their transactions are faster (< 1 minute), more reliable (no reverts) and cost less (lower fees and / or rewards). These features are partially enabled by manifold’s kdb+ engine, which is able to bundle the swaps in the most optimal way for users, miners and FOLD holders in realtime.