Aptos Launches Encrypted Mempool to Curb MEV and Protect Transactions

Aptos has launched an encrypted mempool on its mainnet to reduce maximal extractable value (MEV), which allows bots to profit by exploiting pending blockchain transactions. Announced on October 12, the optional feature hides transaction instructions and inputs until block finalization while keeping sender addresses and fees visible.

How Aptos Encryption Protects Transactions

Users encrypt transaction details on their devices before submission. Validators can order transactions without seeing their contents, which are decrypted collectively after a block is finalized. Aptos says the system uses existing validators without requiring outside parties or changes to existing Move smart contracts.

Related: $XRP Ledger Confirms No New $XRP Created After Critical Vulnerability

Tests involving 50 nodes found that encryption adds about 20 milliseconds of delay per block. The implementation has also undergone independent security reviews by ZKSecurity.

Wallet and Developer Support

Petra Wallet supports the feature through an optional signing setting, while Decibel plans to use encrypted orders for perpetual futures traders.

Developers can submit encrypted transactions through Aptos’ TypeScript SDK version 7.0.0 and later without modifying existing Move contracts. The feature follows Aptos Improvement Proposal 144 (AIP-144) and aims to make pending transactions harder for bots to exploit through front-running and other MEV strategies.

The feature remains optional, allowing users and applications to adopt encrypted transactions where needed.

Related: Ledger Wallet Security Scare Spreads to Europe as User Reports Suspicious Hardware