Aptos Introduces Encrypted Mempool to Block Front-Running and Sandwich Attacks

How Encrypted Mempool Works on Aptos

Aptos has launched an optional encrypted mempool feature designed to prevent frontrunning and sandwich attacks by concealing transaction details until their order is finalized on the blockchain. The update, announced on October 13, 2026, aims to protect users from bots that exploit pending trades in decentralized finance applications. By encrypting transaction data in the mempool, the network ensures that only validators can see the contents during processing, while keeping them hidden from external observers. This mechanism reduces the opportunity for malicious actors to reorder or insert trades for profit.

The encrypted mempool operates by requiring users to opt in when submitting transactions, which are then encrypted using a threshold cryptography scheme. Validators collectively decrypt and order the transactions only after consensus is reached on their inclusion in a block. This prevents bots from observing pending trades in real time, a common tactic used in frontrunning where attackers copy and execute trades ahead of users to capture price slippage. Sandwich attacks, which involve placing trades both before and after a target transaction to manipulate asset prices, are also mitigated since the target trade remains hidden until execution. Aptos developers emphasized that the feature does not alter transaction finality or gas costs, maintaining compatibility with existing smart contracts and d Apps.

What Safeguards Prevent Misuse of the Encrypted System?

To prevent abuse such as spam or invalid transactions, the encrypted mempool includes validation checks that occur before decryption, ensuring only properly formatted transactions proceed to the consensus stage. Validators must jointly participate in the decryption process, which requires a supermajority agreement, reducing the risk of collusion or censorship. The system also incorporates time-bound decryption keys, meaning transactions that fail to be ordered within a set window are automatically discarded. These design choices aim to balance security with network efficiency, though Aptos noted that adoption will be voluntary to allow developers and users to assess performance impacts in real-world conditions.

How does the encrypted mempool affect transaction speed? Transaction processing time remains largely unchanged, as encryption and decryption occur during standard validation phases without adding significant delay.

Frequently Asked Questions

Can users still cancel or replace transactions after submission? Yes, users retain the ability to submit replacement transactions with higher fees, which follow the same encryption and ordering process as original transactions.

Is the encrypted mempool compatible with all Aptos-based applications? The feature is compatible with existing applications, but developers must ensure their contracts do not rely on reading mempool state, which is now inaccessible due to encryption.