Skip to main content
Uruguay Can

News from across crypto

Aptos puts encrypted mempool live on mainnet

Aptos says its opt-in encrypted mempool is live on mainnet, hiding transaction payloads until blocks finalize to limit frontrunning and sandwich attacks.

Uruguay Can Editorial

Aptos puts encrypted mempool live on mainnet

On public blockchains, pending transactions can expose a trader’s move before execution; Aptos says its encrypted mempool went live on mainnet on Oct. 12, hiding transaction details until blocks finalize to make frontrunning and sandwich attacks harder. In its mainnet launch announcement, Aptos says encryption is optional for each transaction and uses the chain’s own validators, so users do not add a separate committee or builder to the trust model.

How does Aptos keep a transaction hidden?

The feature encrypts a transaction’s payload on the user’s device, so the block leader orders it without seeing the function call or its arguments. The process works in three steps:

  1. Your wallet or application encrypts the transaction payload using a key generated jointly by validators for the current epoch.
  2. The encrypted transaction enters the mempool and is ordered into a block while its contents remain hidden.
  3. After consensus finalizes the block, validators collectively reconstruct the payload, and the transaction executes.

Aptos says no single validator can decrypt a pending transaction, and decryption requires the same two-thirds honest-stake threshold used to produce blocks. The sender’s address and gas fee remain visible, and transaction data is recorded on-chain after finalization.

What does using it require?

Encryption is opt-in, so transactions remain public unless a user or application chooses it. Aptos says Petra is the first wallet to offer encryption in its signing flow, while the TypeScript SDK supports it from version 7.0.0; existing Move contracts need no changes. The company says Decibel, a perpetual-futures exchange on Aptos, will use the feature to keep orders private until execution.

The launch addresses a specific exposure: bots can use visible transaction details to trade against or copy a user’s move. Aptos reports roughly 20 milliseconds of added latency per block in 50-node benchmarks, against blocks that finalize in under a second. The feature is designed to reduce that window of visibility; the announcement does not claim that it prevents every form of MEV or trading abuse.

Sources