Aptos activates Encrypted Mempool on mainnet with client-side encryption SDK update

Aptos has activated Encrypted Mempool on mainnet, saying the feature went live after onchain governance approval and can be used on an opt-in basis per transaction.

In a post on X, Aptos Labs said the system encrypts transaction payloads on the client side before submission, with block leaders ordering transactions without seeing the contents and validators decrypting them only after consensus finalizes the block. The company described the feature as live on mainnet and tied it to the latest SDK update.

How the feature is meant to work

According to Aptos, the protection applies to the transaction payload, including the function call and arguments, while the user’s wallet or app performs the encryption before the transaction enters the network. That means the contents of a pending transaction are not visible in plain form during ordering.

The company’s announcement also says the feature is optional. Users must choose to opt in for each transaction, and the Aptos TypeScript SDK version 7.0.0 or later is the client-side path described in the blog post.

The launch adds a privacy layer around pending transaction data, but it does not change the fact that the feature is selective rather than default across the network. Aptos framed it as a mainnet capability that users and builders can adopt where needed.