Aptos has activated its Encrypted Mempool on mainnet, introducing an optional transaction path that keeps transaction instructions hidden while validators determine their position inside a block. The feature encrypts transaction payloads on the user’s device before submission and reveals them only after consensus has finalized the block ordering.
According to Aptos’ official mainnet announcement, the system went live on October 12 and is integrated directly with AptosBFT rather than relying on a separate private builder or external decryption committee. Validators still order encrypted transactions, but they cannot individually inspect the function calls and arguments contained inside them before consensus completes.
The feature is specified through AIP-144, which was accepted as a core protocol proposal. It targets forms of maximal extractable value such as frontrunning and sandwich attacks by reducing the information available before execution. Encrypted Mempool changes pre-execution visibility rather than making Aptos transactions permanently confidential.
Validators Order Transactions Before Seeing Their Payloads
The mechanism uses threshold encryption tied to Aptos’ validator set. At the beginning of each epoch, validators jointly generate an encryption key that clients can retrieve before submitting a transaction. The TypeScript SDK from version 7.0.0 onward can fetch that key, encrypt the payload locally and submit the resulting ciphertext without requiring changes to existing Move contracts.
Consensus then determines which encrypted transactions enter the block. Only after the block is finalized do validators release enough decryption shares to reconstruct the required key and reveal the payload immediately before execution. No single validator can decrypt a pending transaction on its own, and the system is designed around the same stake-weighted trust assumptions already used by the network’s consensus.
The privacy boundary remains deliberately limited. The sender account and gas-related fields remain visible, while the encrypted portion covers the executable function and its arguments. After execution, normal blockchain transparency returns. The feature therefore protects transaction intent during the economically sensitive ordering window rather than hiding transaction history permanently.
That design differs from approaches used elsewhere. Arbitrum, for example, already keeps transactions away from a conventional public mempool through its private sequencer architecture, reducing exposure to conventional public-mempool frontrunning through a different trust model. Aptos instead embeds threshold decryption directly into its validator consensus process.
Adoption Depends on Wallets and Applications
Encrypted Mempool is available on mainnet but remains optional for individual transactions. Petra is the first wallet to expose encryption directly in the signing process, allowing users to select the protected submission path before approving a transaction. Network-level availability therefore does not mean every Aptos transaction is currently encrypted.
Aptos also says Decibel, its ecosystem’s perpetual-futures venue, plans to use the system so orders can remain hidden until execution. That use case is particularly relevant to trading applications, where advance knowledge of direction, size or contract calls can create opportunities for adverse ordering. However, Aptos describes Decibel’s integration prospectively, so it should not yet be treated as evidence of production usage at scale.
Performance remains another operational constraint. Aptos reports that its batched threshold-encryption design added roughly 20 milliseconds of block latency in 50-node benchmarks against the production AptosBFT implementation. An independent zkSecurity review of the encrypted mempool examined the cryptography, distributed key generation and consensus integration before mainnet deployment. Those results demonstrate engineering validation under test conditions, not the volume of encrypted transactions users are currently submitting in production.
The launch adds another infrastructure layer as Aptos expands markets and settlement activity, including an ecosystem where stablecoin liquidity has previously exceeded $2 billion. The meaningful next metric is adoption: how many wallets and applications actually choose encrypted submission, and whether the mechanism measurably reduces harmful transaction-ordering behavior without materially degrading performance.