SKN | Aptos Launches Encrypted Mempool to Reduce Frontrunning and Sandwich Attacks in DeFi

Key Takeaways

• Aptos has introduced an Encrypted Mempool designed to conceal transaction details before ordering is finalized, targeting frontrunning and sandwich attacks.
• The opt-in feature uses threshold encryption coordinated by validators, aiming to reduce harmful maximal extractable value (MEV) without relying on a separate trusted intermediary.
• Adoption by decentralized exchanges, additional transaction costs and real-world execution performance will determine whether the feature materially improves trading fairness.

Aptos is expanding its blockchain security toolkit with an Encrypted Mempool designed to limit the exploitation of pending transactions. As decentralized finance (DeFi) competes for traders and institutional participation, reducing hidden execution costs has become an important consideration alongside transaction speed, liquidity and network fees.

How Encrypted Mempool Targets MEV

In a conventional public mempool, pending transactions can expose details that automated traders use to anticipate market-moving orders. Frontrunners may submit transactions ahead of a targeted trade, while sandwich bots place orders before and after it to profit from the resulting price movement. These strategies can increase slippage and leave ordinary users with worse execution prices.

Aptos’ approach encrypts eligible transaction payloads before they enter the network’s ordering process. Validators can still see certain metadata, including sender information and transaction fees, but the transaction contents remain concealed until ordering has been finalized. This is intended to reduce the window in which bots can exploit advance knowledge of a trade.

The feature is opt-in, so its impact will depend on whether wallets, decentralized exchanges and other applications integrate the encrypted transaction pathway. Its availability alone does not mean all Aptos transactions will receive the same protection.

Threshold Encryption and Network Trade-Offs

The system uses threshold cryptography, allowing validators to cooperate in decrypting transaction contents after ordering. This design seeks to preserve the network’s existing consensus structure while avoiding dependence on a separate operator that controls access to private transactions.

However, encryption introduces operational considerations. The published design specifies a minimum gas price of 200 octas per gas unit for encrypted transactions, compared with the standard base minimum of 100 octas. That represents a 100% increase in the minimum gas-price threshold, although actual transaction costs depend on gas consumption and network conditions.

For high-value trades, the added expense may be justified if protection meaningfully reduces adverse execution. For smaller transactions, the additional cost could discourage usage. Performance, reliability and the handling of failed or delayed transactions will also influence adoption.

Implications for Traders and DeFi Applications

Reducing harmful MEV could help improve execution quality and user confidence, but encrypted transaction submission does not eliminate every form of arbitrage, slippage or market manipulation. Transaction details eventually become visible, and market participants can still respond to finalized activity.

For Aptos, the initiative offers a way to differentiate its infrastructure through transaction-level protections rather than throughput alone. Developers and institutional users will need measurable evidence that the system reduces harmful extraction without creating material delays or weakening operational transparency.

What to Watch as Adoption Develops

The next indicators are integration by major DeFi applications, the proportion of transactions using encryption and evidence of lower sandwich-attack activity. Aptos has introduced a technical mechanism for limiting certain MEV strategies, but sustained adoption will depend on whether its benefits outweigh added costs and implementation complexity. Its longer-term significance will be measured by improved execution outcomes, not simply the launch of the feature.