On October 12, 2026,
Aptos officially deployed Encrypted Mempool on its mainnet, allowing users to optionally encrypt transaction contents before submitting them to the blockchain. The upgrade aims to reduce the risk of exploitation by bots through front-running and sandwich attacks.
According to Aptos, the new technology keeps transaction contents confidential while their execution order is being determined. Validators can only decrypt transactions after the block has been finalized through consensus, limiting the ability of bots to inspect pending orders and execute strategies that disadvantage users.
The development comes as MEV exploitation remains a challenge for the DeFi market. According to Cointelegraph's analysis of EigenPhi data, sandwich attacks caused approximately $60 million in losses for Ethereum traders over the 12 months ending in October 2025.
Although Encrypted Mempool strengthens transaction protection, it also introduces trade-offs involving gas fees and performance. However, Aptos reported that the additional impact on block processing time was relatively small in technical tests.
Key Takeaways
October 12, 2026: Aptos officially launched Encrypted Mempool on mainnet, allowing users to optionally encrypt the contents of individual transactions.
Encrypted Mempool was developed under AIP-144, integrating directly into the AptosBFT consensus mechanism without requiring an external organization to manage decryption.
Transaction contents remain hidden until their order within a block is finalized, limiting bots' ability to exploit transaction information through front-running or sandwich attacks.
Sender addresses and gas fee information remain public, while transaction contents become available for inspection after block finalization.
Sandwich attacks caused approximately $60 million in losses on Ethereum over the 12 months ending in October 2025, according to EigenPhi data cited by Cointelegraph.
The minimum gas price for encrypted transactions is 200 octas per gas unit, compared with 100 octas per gas unit for regular transactions. This does not mean every encrypted transaction necessarily incurs twice the total fee.
A benchmark involving 50 nodes recorded approximately 20 milliseconds of additional latency per block, according to Aptos.
Petra Wallet has integrated transaction encryption, while Decibel, a perpetual futures trading platform, plans to use the technology to protect order contents before execution.
What Happened? Aptos Deploys Encrypted Mempool on Mainnet
Aptos Introduces Transaction Encryption Before Execution
On October 12, 2026, Aptos announced that Encrypted Mempool was officially operational on mainnet, marking the completion of one of the network's transaction protection upgrades.
A mempool is an area where pending transactions are stored before validators select them for inclusion in blocks.
In a public transaction model, information about smart contract calls, asset types, and transaction amounts may be visible to network observers before transactions are executed.
This creates opportunities for bots to analyze pending transactions and exploit transaction ordering for profit.
Encrypted Mempool is designed to address this issue by encrypting transaction contents directly on users' devices before they are submitted to the blockchain.
Unlike certain transaction protection solutions that require users to submit orders through private RPC providers or trusted block builders, Aptos integrates encryption directly into its consensus protocol.
According to Aptos, this design relies on the existing validator set operating the network rather than requiring users to trust an additional party responsible for managing transaction data.
How Does Encrypted Mempool Work?
The mechanism described in AIP-144 uses threshold encryption, allowing validators to coordinate transaction decryption after the execution order has been determined.
The process involves five main steps:
Transaction encryption: When users select Encrypted Mempool, their wallets or applications use the network's current encryption key to encrypt transaction contents directly on their devices.
Submitting transactions to the mempool: The transaction payload is encrypted before being sent to validators. Sender addresses and
gas fee information remain visible.
Determining transaction order: Validators propose and agree on transaction ordering within a block without knowing the contents of encrypted transactions.
Decryption after consensus: Once the block is finalized, validators coordinate through a threshold decryption mechanism to recover transaction contents.
Execution and recording: Transactions are executed, and their data becomes available for inspection on the blockchain after completion.
An individual validator cannot independently decrypt a pending encrypted transaction.
Aptos states that this mechanism relies on the existing validator set's security assumptions, with consensus thresholds linked to the network's staked assets.
However, Encrypted Mempool is not a fully anonymous system.
The technology protects transaction contents only during the pre-execution stage. Once a block is finalized, transaction information becomes publicly accessible to preserve the blockchain's transparency and verifiability.
Petra Wallet and Decibel Integrate the New Technology
According to the official announcement, Petra Wallet is the first wallet to support Encrypted Mempool directly within the transaction signing process.
Users can enable encryption for supported transactions without modifying existing smart contracts.
Aptos has also introduced this functionality in its TypeScript SDK starting with version 7.0.0, allowing developers to integrate encrypted transactions into their applications.
Meanwhile, Decibel, a perpetual futures trading platform built on Aptos, plans to use Encrypted Mempool to keep order contents confidential before execution.
This is a notable use case because derivatives trading platforms can be affected when trading strategies and order details are exposed before processing.
Background / Context: MEV and the Problem of Public Blockchain Transactions
What Is MEV?
MEV, short for Maximal Extractable Value, refers to the value that can be extracted by selecting, ordering, or excluding transactions during block production.
Not all MEV activities harm users. Certain activities, such as arbitrage, may help correct price differences across markets.
However, exploitative forms of MEV, particularly front-running and sandwich attacks, can directly disadvantage traders.
Front-running occurs when an entity observes a pending transaction and attempts to place its own transaction ahead of it to profit from anticipated price movements.
A sandwich attack is an exploitative strategy in which a bot executes transactions before and after a user's order to profit from the resulting price impact, potentially causing the user to receive a worse execution price.
According to Cointelegraph's analysis of EigenPhi data,
Ethereum users lost approximately $60 million to sandwich attacks over the 12 months ending in October 2025.
This figure represents losses from one specific form of MEV, not the total losses caused by all MEV activities on Ethereum.
Why Are Pending Transactions Targeted by Bots?
One of the defining characteristics of public blockchains is the ability to verify transactions and network state.
However, when transaction information is disclosed before execution order is finalized, parties capable of monitoring and reacting quickly can exploit that information.
This is particularly relevant to decentralized exchange transactions, where a large order can affect prices within a liquidity pool.
Bots can analyze pending transactions, identify potential price movements, and attempt to adjust their own transaction positions to generate profits.
The underlying issue is not that blockchain data becomes public after transactions are completed. Rather, it is the ability to access transaction contents before execution order has been finalized.
Encrypted Mempool attempts to reduce this risk by separating the moment transaction ordering is determined from the moment transaction contents are revealed.
MEV Protection Solutions Existed Before Aptos
Before Aptos introduced Encrypted Mempool, several blockchain networks and infrastructure projects had already developed methods to limit the exploitation of pending transactions.
Some solutions use private RPC services or trusted block builders to prevent transactions from being directly exposed to public mempools.
Other approaches rely on trusted execution environments or independent decryption committees to protect transaction contents.
These models can reduce MEV-related risks, but they often require users to trust additional infrastructure components beyond the standard validator set.
Aptos has chosen a different approach by integrating threshold encryption into the AptosBFT consensus mechanism.
According to the project, this solution does not introduce additional trust assumptions beyond the security conditions already applied to the network.
However, this does not mean the system is entirely risk-free. Its protection still depends on the security of the cryptographic algorithms, consensus mechanism, and validator behavior.
Why It Matters: Why Is Encrypted Mempool Significant?
Protecting Users at the Protocol Level
One of the most important differences of Encrypted Mempool is that transaction protection is integrated directly into the blockchain infrastructure.
Under many existing models, applications or users must actively select private transaction service providers to reduce MEV risks.
With Aptos, users still decide whether to encrypt each transaction, but the processing takes place within the network's validator system.
This could make MEV protection easier to integrate into wallets and decentralized applications.
However, its effectiveness will depend on application support and the proportion of transactions that use encryption.
MEV bots often gain an advantage by analyzing transaction information before users' trades are executed.
Encrypted Mempool limits access to smart contract call details and transaction parameters during the pending stage.
This could make front-running and sandwich attack strategies that depend on observing transaction contents in advance more difficult to execute.
However, the technology does not eliminate every risk.
Bots can still use public market data, liquidity conditions, and unencrypted information to develop trading strategies.
Additionally, risks related to slippage, market volatility, and smart contract vulnerabilities remain.
Therefore, Encrypted Mempool should be understood as a mechanism for reducing transaction information exploitation, not a solution that guarantees users will always receive the best execution price.
Introducing encryption increases computational and processing requirements during block production.
According to Aptos, the minimum gas price for encrypted transactions is 200 octas per gas unit, compared with 100 octas per gas unit for regular transactions.
However, the total transaction fee also depends on gas consumption and the specific conditions of each transaction.
Regarding performance, Aptos published benchmark results involving 50 nodes, showing that encryption and decryption added approximately 20 milliseconds of latency per block.
Compared with Aptos's reported sub-second block finality, this additional latency was relatively small in the testing environment.
However, the 20-millisecond figure is not a guarantee of fixed latency under all mainnet conditions.
These trade-offs will need to be evaluated through actual network performance and transaction costs as Encrypted Mempool adoption increases.
Impact: Implications for Aptos, DeFi, and the Crypto Market
Impact on Aptos Network
For Aptos, Encrypted Mempool introduces a transaction protection feature at the infrastructure level.
The upgrade could make the network more attractive to applications requiring limited disclosure of transaction information before execution.
Financial trading applications, decentralized exchanges, and order-processing protocols may consider this capability when selecting a blockchain infrastructure provider.
Notably, Aptos states that existing Move smart contracts do not need to be modified to support the new mechanism.
This could reduce some integration costs for developers.
However, adding transaction protection capabilities does not automatically translate into increased users, revenue, or on-chain activity.
Such impacts will need to be confirmed through data after the upgrade achieves broader adoption.
Impact on DeFi and DEX Users
For DeFi users, the most obvious potential benefit is reducing the risk of exploitation through pending transaction information.
This could be particularly useful for activities such as token swaps or submitting orders to trading protocols.
By preventing order contents from being revealed before execution order is determined, certain sandwich attack strategies may become more difficult to carry out.
However, the level of protection depends on whether users enable encryption, whether applications support the feature, and market conditions at the time of trading.
Encrypted Mempool also does not replace application-level risk management mechanisms, such as slippage limits and liquidity checks.
Impact on Developers and Trading Applications
For developers, Encrypted Mempool support within the Aptos SDK enables the creation of applications capable of protecting transaction contents before execution.
Petra Wallet has integrated the feature into its transaction signing process, while Decibel has been announced as an application planning to use the new mechanism.
This creates opportunities to develop trading products in which certain order details remain confidential during the pending stage.
However, adopting the technology still requires an evaluation of user experience, transaction costs, processing times, and compatibility with individual applications.
Impact on APT Token
The Encrypted Mempool upgrade could strengthen Aptos's blockchain infrastructure development narrative, particularly in transaction security and
DeFi.
If the number of applications and transactions using the feature increases, network activity could benefit.
However, Encrypted Mempool does not create a direct mechanism for increasing the price of APT.
Its impact on the token will depend on network usage, fee mechanisms, demand for APT, and broader market conditions.
There is currently insufficient data to conclude that the upgrade will generate sustainable changes in APT's price or demand.
What Happens Next? Key Developments to Watch
Encrypted Mempool is already operational on the Aptos mainnet. Therefore, the next focus is no longer the deployment date but adoption and real-world effectiveness.
Several important factors should be monitored:
Encrypted transaction adoption: The number and percentage of transactions using Encrypted Mempool compared with total transactions on Aptos.
Wallet integration: Whether wallets other than Petra introduce transaction encryption options.
DeFi adoption: Actual implementation by Decibel and other trading applications.
MEV reduction effectiveness: Data on front-running, sandwich attacks, and other transaction-ordering exploits before and after the upgrade.
Costs and latency: Actual transaction fees, finality times, and the impact on mainnet performance as encrypted transaction volume increases.
Security feedback: Results from audits, research, and independent assessments of the threshold encryption mechanism.
Aptos stated that the system had undergone an independent security assessment by ZKSecurity.
However, security evaluation and improvements must continue as the technology is used in real-world environments.
In the long term, the success of Encrypted Mempool will depend on its ability to reduce harmful forms of MEV while maintaining transaction experiences and network performance suitable for application requirements.
FAQ
1. What Is Aptos Encrypted Mempool?
Encrypted Mempool is a feature launched by Aptos on its mainnet on October 12, 2026. It allows users to optionally encrypt transaction contents before they are included in blocks.
The contents are decrypted only after transaction ordering has been finalized through the network's consensus mechanism.
2. Does Encrypted Mempool Completely Prevent MEV?
No. The technology helps limit MEV strategies that depend on observing transaction contents in advance, including certain types of front-running and sandwich attacks.
However, other forms of MEV and risks related to price volatility and liquidity may still occur.
3. Are Transactions Using Encrypted Mempool Anonymous?
No. Encrypted Mempool encrypts transaction contents only during the pending stage.
Sender addresses and gas fee information remain public, while transaction contents become available for inspection after block finalization.
4. Does Encrypted Mempool Increase Aptos Transaction Fees?
Potentially. Encrypted transactions must meet a minimum gas price of 200 octas per gas unit, compared with 100 octas per gas unit for regular transactions.
However, this does not mean every encrypted transaction incurs twice the total fee, as costs also depend on actual gas consumption.
5. Where Can Users Access Encrypted Mempool?
Petra Wallet is the first wallet to integrate transaction encryption into its signing process.
Additionally, developers can use the Aptos TypeScript SDK starting with version 7.0.0 to integrate this functionality into their applications.
Actual support depends on each wallet and platform.
6. Could the Encrypted Mempool Upgrade Affect APT's Price?
The upgrade could increase interest in Aptos's transaction infrastructure and security capabilities.
However, there is currently insufficient data to determine its direct impact on APT's price.
Long-term effects will depend on adoption, DeFi activity, and overall market conditions.
Disclaimer: The information provided here is for informational purposes only and should not be considered financial, investment, legal, or professional advice. Always conduct your own research, consider your financial situation, and, if necessary, consult with a licensed professional before making any decisions.