Aptos announced the encrypted mempool’s mainnet launch, presenting it as a way to protect liquidity from maximal extractable value, or MEV, without sending transactions through a separate private relay or relying on a trusted block builder.

On a transparent blockchain, pending transactions can reveal an order’s assets, size and contract interactions before execution. Automated traders can use that information to place a transaction ahead of the user, or to trade before and after the order in a sandwich attack. The economic cost is borne by the original trader through worse execution, while the extracting bot captures the difference.

Aptos’ system changes when that information becomes visible. A compatible wallet or application encrypts the transaction locally before it enters the mempool. The sender’s address and gas fee remain visible, but the assets, amounts and Move contract payload are concealed. The Aptos developer documentation describes encrypted mempool support as an optional transaction feature exposed through the software development kit.

Validators can still agree on the order of encrypted transactions because they do not need to inspect the underlying instructions to establish sequencing. Once ordering is finalized, validators collectively decrypt the transaction and execute it onchain. Aptos says its existing validator set handles both ordering and decryption, rather than handing the latter responsibility to an external committee.

That trust model is central to the feature’s economic proposition. Institutions executing large trades, ordinary users seeking protection from MEV, decentralized applications and automated agents can potentially keep trade intent hidden while continuing to use the public network. Petra and Decibel are among the products identified by Aptos as supporting the feature.

The underlying protocol is described in AIP-144, Aptos’ accepted encrypted mempool proposal. The proposal outlines threshold decryption among validators, the cryptographic components required to protect transaction contents and the wallet and SDK changes needed for users to opt in.

Privacy, however, comes with a direct price. Aptos requires encrypted transactions to pay a minimum gas price set at twice the network’s base minimum. That surcharge creates a financial filter around adoption. Traders whose expected losses from MEV are high may accept the cost, while smaller users may continue using transparent transactions.

Performance is another consideration. Aptos reported an additional delay of roughly 20 milliseconds per block in testing with 50 nodes. That is a modest overhead in the reported benchmark, but encrypted execution also introduces operational dependencies. The protocol proposal identifies possible decryption-related liveness risks and metadata leakage, meaning encrypted contents do not make every aspect of transaction activity invisible.

The rollout has also drawn a critical assessment. zkSecurity published an audit of Aptos’ encrypted mempool that identified findings involving pairing checks, KZG openings, replay, transaction malleability, validator crashes and cases involving decryption without execution. The firm also raised privacy limitations. No opposing assessment was provided among the sources for this report, so the critical findings should be treated as the only external reaction located here, not as a resolved industry consensus.

The capital-flow question is whether protection against MEV justifies the extra cost and integration work. If decentralized exchanges and execution venues make encrypted ordering a default option for high-value trades, the feature could shift liquidity away from fully transparent transaction flows. Institutions could gain a new way to submit size without advertising intent, while AI agents could compete with less exposure to copy trading and order manipulation.

For now, Aptos has made privacy optional rather than universal. That leaves the main adoption risk with wallets, applications and users. If support expands, encrypted ordering could become part of the standard infrastructure for sensitive onchain execution. If usage remains concentrated among sophisticated traders, most retail liquidity will continue to pass through transparent mempools and remain exposed to the extraction dynamics Aptos is trying to limit.

#Aptos#Petra#Decibel#Move#AIP-144#zkSecurity
Image credits

Ethan Brooks is not a person. No notebook, no deadlines, no face behind the name — just a byline this newsroom publishes under. Here is the production line underneath it, because a name beside a portrait reads like a journalist, and this one is not one.

The models. Writing: gpt-5.6-luna. Out on the live web: gpt-5.6-luna and gpt-5.6-terra. Pictures: gpt-image-1. Swap one in the newsroom and this line swaps with it — it is read off the machines, not typed here.

How a story is made

  • Research. The searching model reads around the story, pointed at primary sources — the filing, the post, the repository — rather than at somebody else's write-up of them.
  • Writing. The writing model drafts it against what was found, at Ethan Brooks's usual length and in Ethan Brooks's usual register.
  • The loop. A reviewer reads the draft and sends it back with notes. Then reads it again. A piece can go round several times before it leaves the building.
  • Enrichment. A quotation has to appear word for word on the page it is taken from. A chart may only use figures that appear in the source it cites. Whatever fails is dropped, and the reason is kept.
  • Fact check. A last pass hunts for claims the article makes and its sources do not.
  • A human stop. Sensitive subjects are held for a person to read before publication, and a person can kill any of it at any point.

If that sounds less like a newsroom and more like a factory: quite. It is called Press Factory.

This article was generated using AI and published automatically without human pre-publication review.

Read and checked by admin on 10/14/2026

How this article was made

The article was produced by the Grandmonts Media News Engine using automated research, drafting and verification workflows. No human editor reviewed the article before publication. Grandmonts Media remains responsible for the published content. Errors can be reported at office@grandmonts.cz.