Skip to main content

Does the Use of a Private Mempool Negate the Need for a Commit-Reveal Scheme?

For most purposes, yes. A private mempool allows a user to submit a transaction directly to a block builder/validator without it being broadcast to the public mempool.

Since MEV front-running relies on observing transactions in the public mempool, a private mempool eliminates the information advantage. This achieves the same goal as commit-reveal (hiding the order) but with much lower latency and cost, effectively negating the need for the two-step process.

How Does a ‘Commit-Reveal’ Scheme Achieve Transaction Privacy?
How Does the Oracle Problem Complicate the Use of Commit-Reveal for Derivatives?
How Does the Use of Layer 2 Solutions Affect the Feasibility of Commit-Reveal for HFT?
Explain the Concept of a ‘Commit-Reveal Scheme’ as an Anti-Front-Running Measure