# Aptos Activates an Encrypted Mempool to Hide Transaction Intent Until Ordering Source: TechNewsList (https://technewslist.com) Canonical URL: https://technewslist.com/en/article/aptos-encrypted-mempool-mainnet-mev-protection-2026-10-13-morning Section: DeFi & Crypto (https://technewslist.com/en/defi-crypto) Author: TechNewsList Language: en Published: 2026-10-13T07:52:44.526+00:00 Updated: 2026-10-13T07:52:44.710758+00:00 > Aptos now lets users opt into protocol-native payload encryption, keeping function calls and arguments hidden until consensus fixes block order while preserving on-chain auditability afterward. ## TL;DR - Aptos users can opt into encrypting transaction payloads before submission, while sender and gas information remain visible. - Validators order ciphertext first and collectively decrypt only after consensus fixes the block, reducing opportunities for payload-based front-running. - Aptos reports about 20 milliseconds of added block latency in a 50-node benchmark, but live market behavior still needs observation. ## Key points - The validator set jointly creates an epoch encryption key and no sub-threshold group can decrypt a pending payload. - The first release hides the called function and arguments but does not conceal the sender account or gas-fee fields. - A batched threshold scheme keeps validator communication constant-size for a block rather than scaling with every transaction. - Petra exposes encryption in its signing flow and Aptos TypeScript SDK version 7 or later supports client-side encryption. - Existing Move contracts do not need changes because decryption occurs before normal transaction execution. ## What happened Aptos has switched on an encrypted mempool on mainnet, giving users an opt-in way to conceal transaction payloads before execution. The sender and fee remain visible, but the called function and its arguments are encrypted on the client. Validators receive ciphertext, agree on its position in a block and reconstruct the plaintext only after consensus has finalized that order. The resulting transaction is then recorded normally, so post-trade auditors and explorers do not lose the final public history. ![Diagram of Aptos batched threshold decryption and block ordering](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1791877955139-u2fi47-aptos-encrypted-mempool-mainnet-mev-protection-2026-10-13-morning-inside-1-7578a577ac.webp) *The official workflow diagram shows encryption before ordering and threshold decryption after the block is fixed. Credit: Aptos Labs.* The implementation is defined in AIP-144 and uses the existing validator set rather than a private relay or separate committee. Petra is the first wallet to expose the choice directly during signing, and the Aptos TypeScript SDK supports it from version 7.0.0. Decibel, a perpetual-futures venue on Aptos, says it plans to keep orders private until execution. ## Why it matters Public mempools leak intent. A bot can observe a pending swap, copy it, trade ahead of it or surround it with transactions that worsen the user's price. Private builders can reduce that exposure, but they become another trusted party that sees plaintext. Aptos is trying to make confidentiality part of consensus so the protection inherits the chain's existing trust assumption. That distinction matters for financial applications where an order is valuable information before it executes. Protocol-native encryption cannot remove every form of maximal extractable value, and it does not hide identities or outcomes after finality. It can, however, narrow the window in which transaction contents are available to block producers and searchers who might exploit ordering. ## Technical details Clients encrypt against a public key jointly produced by validators for each epoch. The block leader proposes an order without seeing payload contents. After finalization, validators publish decryption shares and execution proceeds normally. Aptos says no single validator, nor any set below the network's two-thirds honest-stake threshold, can decrypt a pending transaction on its own. ![Aptos privacy stack covering accounts balances and transaction intent](https://rkhynbcsbnkkcwgexzwg.supabase.co/storage/v1/object/public/media/api/1791877957218-561jeg-aptos-encrypted-mempool-mainnet-mev-protection-2026-10-13-morning-inside-2-45b4855f2f.webp) *Aptos' privacy-stack diagram places encrypted mempool at the intent layer alongside other opt-in controls. Credit: Aptos Foundation.* The system uses batched threshold encryption so a validator's communication remains constant-size for the full block instead of growing with the batch. Aptos reports roughly 20 milliseconds of overhead per block in a 50-node test against its production AptosBFT implementation. That is small beside sub-second finality, but application-level measurements under congestion will be more informative than a controlled benchmark. ## Market / industry impact The release puts pressure on other high-throughput chains to explain who can read order flow and when. Private RPC services, trusted execution environments and external key committees each solve part of the problem with different failure modes. Aptos can claim a cleaner trust story, although validators still control consensus and users must deliberately choose encryption for each transaction. For exchanges and wallets, adoption will depend on defaults and compatibility. If encrypted submission adds friction or higher fees, only sophisticated traders may use it, leaving ordinary flow exposed. If wallets make the control understandable and venues demonstrate better execution quality, privacy at the intent layer could become a normal product feature rather than a specialist MEV tool. ## What to watch next The first evidence should come from live usage: the share of encrypted transactions, fee differences, failed decryptions and ordering behavior during volatile periods. Researchers should also test liveness when validators are slow or unavailable, because a privacy mechanism that delays execution at the worst moment can create a new operational risk even if its cryptography is sound. Aptos has disclosed two important boundaries: addresses and gas fields remain visible, and final transactions remain auditable on-chain. Future versions may broaden confidentiality, but each added secret complicates compliance, indexing and debugging. The strongest outcome would be measurable reduction in harmful front-running without opaque intermediaries or a material loss of finality and reliability. ## Sources - [Aptos Foundation](https://aptosnetwork.com/currents/encrypted-mempool-mainnet) - [AIP-144](https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-144-encrypted-mempool.md) - [Crypto.news](https://crypto.news/aptos-launches-encrypted-mempool-how-does-it-work/) Mentions: Aptos, AIP-144, Petra, Decibel, AptosBFT ## Sources - [Aptos Foundation](https://aptosnetwork.com/currents/encrypted-mempool-mainnet) - [AIP-144](https://github.com/aptos-foundation/AIPs/blob/main/aips/aip-144-encrypted-mempool.md) - [Crypto.news](https://crypto.news/aptos-launches-encrypted-mempool-how-does-it-work/)