Aptos Encrypted Mempool Goes Live: How It Could Reduce MEV Attacks

Aptos Encrypted Mempool Goes Live: How It Could Reduce MEV Attacks

Custom Image
Aptos officially launched its Encrypted Mempool on October 12, 2026, introducing optional transaction encryption designed to reduce front-running and sandwich attacks on its Layer-1 blockchain. Implemented through Aptos Improvement Proposal 144 (AIP-144), the upgrade conceals transaction instructions until validators finalize their ordering, limiting the information available to MEV bots before execution. Unlike systems that depend on external private transaction services, Aptos integrates encryption directly into its existing consensus infrastructure. The feature is available through compatible wallets, including Petra, although higher transaction fees, privacy limitations, and uncertain adoption remain important considerations for decentralized finance (DeFi) traders and developers.
 

Key Takeaways

  • Aptos Encrypted Mempool launch: Aptos activated its optional transaction encryption feature on October 12, 2026, under AIP-144, integrating protection for pending transactions into its existing blockchain infrastructure.
  • MEV and sandwich attack protection: Encrypted transaction payloads remain concealed until block ordering is finalized, making certain front-running and sandwich attacks harder to execute. Actual reductions in attacks have not yet been independently established.
  • Higher transaction fees: Encrypted transactions require a minimum gas-unit price of 200 octas plus 375 additional gas units. Aptos's documented example shows a sevenfold fee increase for a simple transaction at minimum gas prices.
  • Network performance: Aptos reported approximately 20 milliseconds of additional latency per block in a 50-node benchmark, although production performance may vary with network conditions and transaction demand.
  • Wallet and DeFi integration: Petra supports encrypted transaction submission, while Decibel plans to integrate the technology. Developers can access encryption through Aptos TypeScript SDK version 7.0.0 and later.
  • Privacy and adoption limitations: Sender addresses and gas information remain visible, and transaction details become publicly auditable after execution. Broader DeFi adoption and measurable improvements in trading protection remain uncertain.
 

Aptos Encrypted Mempool Launches on Mainnet Under AIP-144

Aptos officially launched its Encrypted Mempool on October 12, 2026, introducing optional transaction encryption on its Layer-1 blockchain. Developed under Aptos Improvement Proposal 144 (AIP-144), the upgrade allows users to conceal transaction instructions before they enter the network's pending transaction pool. According to the Aptos Foundation, the feature is integrated into the blockchain's existing consensus infrastructure rather than relying on an external encryption service. The mainnet activation gives users another way to submit transactions while maintaining compatibility with the network's existing applications and smart contracts.
 

AIP-144 Approval and Mainnet Activation

AIP-144 is classified as an accepted core improvement proposal in the Aptos governance repository. Its implementation followed a series of network preparations, including the August 25, 2026, execution of a governance proposal initializing Encrypted Mempool framework resources and enabling ChunkyDKG shadow mode. Another proposal, executed on October 6, enabled ChunkyDKG V1, supporting the distributed key-generation infrastructure required for encrypted transactions. These changes preceded the October 12 public launch.
 
The upgrade extends Aptos's transaction-processing capabilities without requiring developers to rewrite existing Move smart contracts. Encryption is available on a per-transaction basis, allowing ordinary and encrypted submissions to coexist on the network. This approach gives users flexibility while allowing decentralized applications to introduce encrypted transaction support through compatible wallets and development tools.
 

Petra Wallet Support and Developer Integration

The Aptos Foundation confirmed that Petra wallet supports encrypted transaction submission through its signing interface, allowing users to select encryption when approving supported transactions. Developers can also integrate the functionality into existing applications using the Aptos TypeScript SDK. However, the feature is not automatically enabled for every transaction, and its availability depends on compatible software and account configurations.
 
The initial rollout includes several important integration details:
  • Petra wallet: Identified by Aptos as the first wallet to offer encryption directly during transaction signing, giving users access to the feature without requiring a separate transaction service.
  • Aptos TypeScript SDK: Version 7.0.0 and later supports encrypted transaction creation and submission, allowing developers to add the functionality without modifying existing Move smart contracts.
  • Decibel integration: The Aptos-based perpetual futures exchange plans to use encrypted transactions to protect pending trading orders. Its announced integration does not establish that the feature was fully deployed on Decibel at launch.
 
These integrations establish the initial availability of Aptos Encrypted Mempool, although widespread adoption and measurable improvements in trading protection have not yet been independently demonstrated.
 

How Does Aptos Encrypted Mempool Reduce MEV and Sandwich Attacks?

Aptos Encrypted Mempool aims to reduce maximal extractable value (MEV) attacks by preventing traders, automated bots, and block proposers from reading protected transaction instructions before their execution order is finalized. On public blockchains, pending transactions can expose information that sophisticated traders exploit for profit. By concealing these details during transaction ordering, Aptos makes certain front-running and sandwich attacks more difficult to execute, although encryption cannot eliminate every form of MEV.
 

How Front-Running and Sandwich Attacks Exploit Pending Transactions

Front-running occurs when a trader or automated bot uses information about a pending transaction to place another trade ahead of it, potentially profiting from the resulting price movement. On decentralized exchanges (DEXs), visible trading instructions can reveal the assets involved, transaction amounts, and expected market impact. MEV bots analyze this information to identify profitable opportunities before the original transaction executes. Such activity can disadvantage ordinary traders, particularly when large swaps affect prices in liquidity pools.
 
Sandwich attacks are a more specific form of transaction manipulation. An attacker identifies a pending swap, places a transaction immediately before it to influence the execution price, and submits another transaction afterward to capture a profit. For example, a bot might purchase a token before a large buy order and sell it after the victim's transaction increases the token's price. The victim may receive fewer tokens than expected, while the attacker benefits from the price difference. This strategy depends on identifying the targeted trade and influencing transaction ordering before execution.
 

How Threshold Encryption Protects Aptos Transactions

Aptos addresses this vulnerability through batched threshold encryption, which prevents individual validators from independently decrypting protected transaction payloads before consensus. The user's device encrypts the transaction using a public encryption key generated collectively by the validator set for the current network epoch. The encrypted transaction is then submitted for inclusion in a block, allowing validators to establish its position without knowing the specific smart-contract function or arguments it contains.
 
Once consensus finalizes the block's contents and ordering, validators collectively produce the decryption information required for execution. According to AIP-144, the process uses stake-weighted threshold cryptography, meaning that no individual validator or insufficiently large group can decrypt protected transactions independently under the protocol's security assumptions. The batched design also allows validators to process multiple encrypted payloads using a shared decryption operation, reducing the computational and communication overhead that would otherwise accompany transaction-by-transaction decryption.
 

Which MEV Strategies Become Harder to Execute?

The main advantage of encrypted transaction ordering is that attackers lose access to information they would normally use to select profitable targets. Once a protected transaction's position is finalized, a bot cannot retroactively insert a trade ahead of it within that finalized block after discovering its contents. This limits opportunities for attacks that depend on advance knowledge of another user's trading intentions. However, ordinary market movements and MEV strategies that do not require reading encrypted payloads may still affect transaction outcomes.
 
The mechanism also restricts several related forms of transaction exploitation:
  • Trade copying: Automated traders cannot directly inspect an encrypted transaction's function and arguments to imitate its trading strategy before the ordering decision.
  • Profit-based transaction selection: Block proposers cannot use concealed swap details to identify and prioritize transactions solely according to their expected trading profitability.
  • Unconfirmed transaction exposure: Under AIP-144's cryptographic design, a block's reconstructed decryption key applies to the encrypted payloads committed to that block, rather than automatically revealing other pending transactions.
 
These protections address the information advantage behind several harmful MEV strategies. Their effectiveness in actual trading conditions will depend on implementation security and how extensively encrypted transactions are used across the Aptos network.
 

Aptos Encrypted Mempool Fees, Privacy Limits, and DeFi Impact

Aptos's encrypted transaction system introduces additional costs and technical limitations that traders must consider before using it. While the upgrade is designed to reduce exposure to harmful MEV strategies, its practical value depends on transaction size, execution requirements, and application compatibility. The network's performance benchmarks and independent security review also provide important context for evaluating whether encrypted transactions can support broader decentralized finance (DeFi) activity.
 

Aptos Encrypted Transaction Fees and Gas Costs

Encrypted transactions on Aptos have a minimum gas-unit price of 200 octas, twice the standard minimum of 100 octas. They also incur an additional charge of 375 gas units to cover validator decryption work. According to Aptos's official documentation, a transaction consuming 150 gas units would cost 15,000 octas (0.00015 APT) at the standard minimum price. With encryption enabled, the same transaction would require approximately 105,000 octas (0.00105 APT), making it seven times more expensive in this example, excluding storage fees.
 
The higher cost does not mean every encrypted transaction will be seven times more expensive. The difference depends on execution complexity, network gas pricing, and applicable storage charges. The fixed decryption fee represents a larger proportion of the total cost for simple transfers than for computationally expensive transactions. Both the minimum encrypted gas price and decryption charge are controlled through Aptos's on-chain gas schedule, meaning future governance decisions could change these parameters.
 

Aptos Transaction Privacy Limits and Remaining Security Risks

Encrypted Mempool provides temporary transaction confidentiality, not complete anonymity. The protection applies to transaction instructions while they are pending, but it does not permanently conceal executed transfers or blockchain activity. Once transactions are finalized and executed, their details remain available for public verification. This differs from confidential asset systems designed to protect selected balance and transfer information after confirmation.
 
Several technical limitations remain relevant to users and developers:
  • Public transaction metadata: Sender addresses, sequence numbers, gas limits, and expiration timestamps remain observable. These details may reveal information about transaction urgency or account activity.
  • Contract identification: Certain transaction configurations can expose the target smart contract through a claimed_entry_fun field, even when the executable payload is encrypted.
  • Ciphertext size: Differences in encrypted payload length may help observers infer whether a transaction involves a simple transfer or a more complex contract interaction.
  • Transaction simulation: AIP-144 identifies a potential privacy risk when an application sends plaintext simulation data and the encrypted transaction to the same fullnode, allowing possible correlation through timing analysis.
 
These limitations are documented in the independent ZKSecurity audit and Aptos's technical specifications. They demonstrate why transaction encryption should be evaluated as a targeted protection against information-based exploitation rather than a substitute for comprehensive financial privacy.
 

Aptos Encrypted Mempool Performance and Security Audit

The Aptos Foundation reported approximately 20 milliseconds of additional latency per block in benchmarks involving 50 nodes running the production AptosBFT implementation. This measurement suggests that the encryption process can operate with relatively limited overhead under the tested conditions. However, it is a benchmark result rather than a guarantee of identical performance across production workloads. AIP-144 also acknowledges that the maximum throughput available exclusively for encrypted transactions is lower than that for ordinary transactions, although encryption remains optional.
 
Security assessment is another important consideration. ZKSecurity's March 13, 2026, audit documented 30 findings, including seven classified as high severity, four as medium, nine as low, and ten as informational. The report identifies remediation work for numerous issues, alongside acknowledged limitations involving confidentiality and transaction processing. These findings describe the implementation examined during the review and should not be interpreted as evidence that every identified vulnerability remained exploitable at the October mainnet launch. Nevertheless, the audit does not eliminate the need for continued security testing, monitoring, and verification of deployed fixes.
 

DeFi Trading Impact and Implications for APT Investors

Encrypted transaction processing could become useful for decentralized exchanges, liquidity providers, and institutions executing sensitive on-chain transactions. Large trades and treasury operations can reveal valuable information before execution, creating opportunities for other market participants to adjust their positions. Reducing that visibility may improve execution conditions for certain users, particularly in markets where pending-order information can influence trading behavior. However, the benefits will depend on how applications implement encryption and whether traders experience measurable improvements.
 
Several factors will help determine the upgrade's longer-term significance:
  • DeFi adoption: The percentage of eligible transactions submitted with encryption will provide a more meaningful adoption indicator than wallet or application support announcements alone.
  • Trading execution quality: Changes in realized slippage and suspected sandwich-attack losses could help assess effectiveness, provided comparisons account for trade sizes, liquidity, and market conditions.
  • Account compatibility: Aptos documentation states that keyless, federated keyless, and account abstraction accounts cannot currently sign encrypted transactions, limiting availability for applications using those account models.
  • Network reliability: Transaction inclusion rates, failed decryptions, and performance under sustained trading activity will help developers evaluate the system's suitability for demanding financial applications.
 
The encrypted mempool adds a transaction-protection capability that may influence how developers and trading platforms evaluate the Aptos network. Its contribution to ecosystem activity will depend on adoption and sustained usage rather than the launch announcement itself. Although investors can follow APT/USDT trading activity, short-term market movements do not establish the upgrade's effectiveness or its impact on token demand.
 

Conclusion

Aptos's October 12, 2026, Encrypted Mempool launch introduces a new approach to protecting pending transactions from information-based MEV attacks. By integrating threshold encryption into its existing validator infrastructure, the network aims to make front-running and sandwich attacks more difficult without requiring changes to existing Move smart contracts. However, higher transaction costs, limited metadata privacy, and implementation risks remain important considerations. The upgrade's longer-term significance will depend on wallet integration, DeFi adoption, and measurable improvements in trading execution. Until sufficient production data becomes available, its potential benefits should be distinguished from independently demonstrated reductions in MEV-related losses.
 

🔥 Beyond the Headlines: What KuCoin 5.0 Means for You

Market news moves fast — but where you act on it matters just as much. This October, KuCoin launches KuCoin 5.0, transforming KuCoin into a rebuilt platform. Here's what actually changes for you:
 
  • One account for everything. Older platforms split your money across separate "spot," "margin," and "futures" accounts and expected you to understand why. KuCoin 5.0's unified account removes that entirely — deposit once, and everything is simply there (only available to VIPs for now).
  • Stocks, indices, and commodities. KuCoin 5.0 expands beyond crypto into global markets. When crypto chops sideways and equities rally (or the reverse), you rotate in minutes instead of opening a brokerage account and waiting days for fiat rails.
  • Real-world assets (RWA). Tokenized exposure to traditional assets like commodities, right inside your crypto account. One of the fastest-growing segments in global finance is no longer reserved for institutions — you access it from the same balance you trade with.
  • Earn while you learn. Not ready to trade? KCUSD lets your stablecoins earn daily, auto-compounding interest. The lowest-stress way to put your idle deposit to work for 4% yield.
  • An AI assistant in plain language. Ask questions, get market context, understand what you're looking at — built into the platform, no jargon required.
  • An app that doesn't overwhelm. Faster, cleaner, and consistent — intuitive from the first tap, not after a tutorial.
  • Safety you can check, not just trust. A MiCAR-licensed EU entity, Proof of Reserves you can verify yourself, and internationally certified security (SOC 2 Type II, ISO 27001:2022).
 
Create your account in minutes — and start on the platform built for where crypto is going, not where it's been.
 

FAQs

Can Aptos Encrypted Mempool Work With Orderless Transactions?

Yes. Aptos supports combining encrypted payloads with orderless transactions, which use replay-protection nonces instead of relying on traditional account sequence-number ordering. Developers can configure both features through the TypeScript SDK. This combination can be useful for applications submitting multiple independent transactions concurrently.

Can Developers Simulate Aptos Encrypted Transactions Before Submission?

Direct simulation of encrypted payloads is not supported by the Aptos TypeScript SDK. Developers can simulate an equivalent plaintext transaction to estimate execution requirements, but doing so may expose sensitive information. Applications handling confidential trading instructions should carefully assess this privacy risk before using plaintext simulation.

How Is Aptos Encrypted Mempool Different From Private RPC Services?

Private RPC services typically send transactions through selected intermediaries instead of broadcasting their contents broadly. However, the receiving service may still access the original transaction details. Aptos uses cryptographic protection integrated with its existing validator system, reducing the need to disclose pending transaction instructions to a separate private transaction operator.

Does Aptos Encrypted Mempool Guarantee Better Swap Prices?

No. Encrypted transaction submission does not guarantee better swap prices or eliminate losses caused by market volatility. Liquidity depth, price impact, slippage settings, and execution conditions can still affect trading outcomes. The feature primarily addresses information-based transaction exploitation rather than the ordinary financial risks of decentralized trading.
 
 

Disclaimer

The information provided on this page may originate from third-party sources and does not necessarily represent the views or opinions of KuCoin. This content is intended solely for general informational purposes and should not be considered financial, investment, or professional advice. KuCoin does not guarantee the accuracy, completeness, or reliability of the information, and is not responsible for any errors, omissions, or outcomes resulting from its use. Investing in digital assets carries inherent risks. Please carefully evaluate your risk tolerance and financial situation before making any investment decisions. For further details, please consult KuCoin’s Terms of Use and Risk Disclosure.