Key Notes
- Aptos has activated optional payload encryption on mainnet, keeping pending transaction details hidden until validators finalize the block’s ordering.
- Petra already supports the feature, while Decibel plans to use it for perpetual orders and the reported 20 ms overhead comes from a 50-node benchmark.
- Sender and fee metadata remain visible, completed transaction details become public, and developer documentation sets out higher minimum gas pricing and integration limits.
Aptos has activated an encrypted mempool on mainnet, allowing users to hide a transaction’s contents while validators decide where it belongs in a block. The optional feature targets the information advantage that trading bots and block producers can gain by reading pending orders before they execute.
The Aptos Foundation announced the rollout on October 12, saying Petra already offers encryption in its signing flow. Decibel, a perpetual futures exchange on Aptos, plans to use the system to conceal orders until execution. Sender addresses and fee information remain visible, and transaction data becomes public after the block’s ordering is finalized.
Closing the Window Before an Order Executes
A mempool holds transactions waiting to be included in a block. When their contents are readable, an observer can see the trade a user intends to make and try to profit from acting first. A sandwich attack, for example, places trades around a victim’s order to extract value from the resulting price movement.
The accepted AIP-144 specification changes that sequence. The user’s wallet or application encrypts the payload locally before submission, covering the function being called and its arguments. The block leader then proposes an order without reading those details.
Once consensus fixes the block’s contents and ordering, validators combine their decryption shares, recover the payloads and execute the transactions. Finalizing the order comes before execution in this design; encryption does not mean executing a trade without revealing it to the network.
The system uses the existing validators rather than handing decryption to a separate committee. Its security therefore depends on the chain’s stake-based consensus assumptions. A single validator cannot independently decrypt an encrypted pending transaction under the intended threshold model.
Petra Is Available; Decibel Integration Is Planned
Encryption is selected for individual transactions rather than imposed across all Aptos activity. In Petra, users can choose it during signing. Applications can also build encrypted transactions through the Aptos TypeScript SDK, with the launch announcement identifying support in version 7.0.0 and later.
For Decibel, the intended benefit is hiding trading instructions during the period when another participant could react before the order executes. The Foundation describes that integration as forthcoming. It has not presented the announcement as evidence that every Decibel order is already encrypted or that the exchange has eliminated all forms of maximal extractable value, commonly called MEV.
Existing Move smart contracts do not need to be rewritten to use the feature, according to Aptos. Wallet and application support still matters: the payload must be encrypted before it is sent, so a normal unencrypted submission does not gain protection merely because the network supports encrypted transactions.
The rollout is separate from MonoMove, the execution-engine overhaul Aptos Labs recently unveiled. That project remains on a development roadmap targeting mainnet in 2027, subject to governance approval. The encrypted mempool is a live change to transaction submission and ordering, rather than a claim that MonoMove’s benchmark gains are already deployed.
What the 20 Millisecond Benchmark Measures
Aptos reports roughly 20 milliseconds of additional latency per block in a 50-node benchmark using its production AptosBFT implementation. That is a measured overhead in a specified test, not a promise that every user’s transaction will finish exactly 20 milliseconds later under all network conditions.
The implementation uses batched threshold encryption, allowing validators to decrypt a block’s encrypted payloads together. The design keeps the communication required from each validator constant in size as the batch grows, addressing the cost of coordinating a separate decryption process for each transaction.
For traders, the practical trade-off is whether reduced exposure before execution justifies the additional processing and transaction cost. Network-level availability alone does not show how widely the feature is being used, and the announcement does not provide an adoption rate or a measured reduction in losses from front-running.
Temporary Confidentiality Has Defined Limits
The feature protects pending payloads, rather than making Aptos a fully private ledger. Account and fee metadata remain observable, and completed transaction details are recorded onchain. That differs from systems designed to separate a payment from the identity using a service, such as the Ethereum Foundation’s zkAPI project.
The official developer guide specifies a minimum gas-unit price of 200 Octas for encrypted transactions, twice the network’s base minimum. This is a price floor per unit of gas, not a statement that every encrypted transaction’s total fee is exactly double that of an ordinary transaction.
The guide also warns that simulating a plaintext copy can expose information that observers could correlate with a subsequent encrypted submission. Some sponsored or multisig flows disclose the targeted entry function, while keyless and account-abstraction signers are currently unsupported. Integration choices therefore affect the protection a particular user receives.
An independent ZKSecurity review examined the cryptography and consensus integration. It also identifies inherent privacy limits, including observable metadata and ciphertext length, and notes that encryption does not guarantee a proposer will include a transaction. The review records fixes and acknowledged limitations; it is not a guarantee against every trading attack.
The mainnet launch gives Aptos applications a new way to withhold trading intent before ordering is settled. Its value in practice will depend on wallet adoption, application integration and how those documented limits are handled.
Disclaimer: CoinScreamer is an independent media brand owned and operated by NuvexMedia LLC, publishing news, research, and market insights on digital assets and related technologies. NuvexMedia LLC invests in and collaborates with companies across the digital asset, blockchain, and technology sectors. These relationships do not influence CoinScreamer’s editorial coverage, and the publication maintains full editorial independence to provide accurate, timely, and objective information. © 2025 NuvexMedia LLC. All rights reserved. This content is for informational purposes only and should not be considered legal, tax, investment, financial, or other professional advice.
