How Do Decentralized Perpetual Futures Exchanges Address Front-Running without Commit-Reveal?

Many perpetual futures DEXs use an off-chain order book with on-chain settlement. Orders are matched quickly and privately off-chain by a centralized relayer or sequencer, hiding them from the public mempool and eliminating MEV front-running based on transaction order.

They also use oracle-based pricing and sometimes batching to ensure fair execution. This sacrifices full decentralization of the matching process for speed and MEV resistance.

Is There a Theoretical “Optimal” Block Time to Minimize MEV without Sacrificing Security?
How Does a Commit-Reveal Scheme Protect a Trade from Being Front-Run?
What Technical Solutions Are Used to Mitigate MEV and Front-Running in DeFi?
How Does an Off-Chain Order Book Prevent Front-Running on a Centralized Exchange?
How Do Commit-Reveal Schemes Affect the User Experience on a Decentralized Exchange (DEX)?
How Do Commit-Reveal Schemes on DEXs Specifically Prevent Front-Running?
How Does the Use of Layer 2 Solutions Affect the Feasibility of Commit-Reveal for HFT?
In a Commit-Reveal System, What Is the Minimum Time Delay between the Commit and the Reveal?

Glossar