Key Takeaways
- Encryption is optional for each transaction.
- Instructions are revealed after block ordering is finalized.
- Petra offers the option; Decibel plans to use it.
Why a visible pending trade can cost its sender
In its October 12 announcement, Aptos said encrypted mempool was live on mainnet. A mempool holds pending transactions before they are included in a block. When their contents are visible, observers can inspect instructions before execution.
Consider a hypothetical swap large enough to move a token’s price. A bot that sees the pending order could try to buy first, let the user’s swap push the price higher, then sell afterward. This sequence, known as a sandwich attack, can leave the user with worse execution. It depends on seeing the instruction while there is still an opportunity to trade around it.
Encryption removes that view of the transaction’s payload—the function being called and its arguments—during ordering. It does not promise a particular execution price: an encrypted swap can still face ordinary market movement, limited liquidity or restrictive slippage settings.
Ordering comes before the instructions are revealed
The AIP-144 protocol proposal describes three stages:su
- Submission: The client encrypts the payload before sending the transaction.
- Ordering: Validators agree on the block while its encrypted instructions remain unreadable.
- Decryption and execution: Validators reveal the payloads after consensus, then execute the transactions.
Finality here means agreement on the block and its transaction order. Aptos separates that agreement from execution, allowing instructions to remain concealed until their position is fixed.
The sender account and gas-fee fields remain visible at submission. Completed activity is recorded publicly afterward. As with other approaches to blockchain privacy, concealing selected details does not make an account anonymous.
The validators also handle decryption
The validators jointly generate encryption keys for each epoch, a period during which the validator set is fixed. Decryption requires enough stake-weighted shares—pieces of the decryption capability—rather than access by a single validator. Aptos therefore uses its consensus validators instead of appointing a separate decryption committee.
The proposal also specifies a one-time trusted setup ceremony. The security explanation should therefore include the cryptographic setup as well as validator behaviour, rather than treating the absence of an external committee as the entire trust model.
ZKSecurity’s independent review examined the encryption scheme, key-management components and integration with transaction processing. Gas metering was outside its scope. The review provides implementation evidence, but it should not be presented as a guarantee against every failure or trading risk.
How users enable it—and what the benchmark shows
According to Aptos, Petra exposes encryption in its signing flow. Users choose it for individual transactions. Decibel, the Aptos perpetual-futures exchange, plans to use the feature; the announcement does not establish that its integration is already operating.
Developers can submit encrypted payloads through the Aptos TypeScript SDK, with support from version 7.0.0. Existing Move contracts require no changes.
Aptos reports roughly 20 milliseconds of additional latency per block in 50-node benchmarks. That measures processing overhead, not savings for traders or production performance during congestion. Encryption conceals instructions during ordering; whether a trade receives a better price still depends on the market and the application executing it.
This article is provided for informational purposes only and does not constitute financial or investment advice. Blockchain privacy tools can reduce selected forms of information exposure without guaranteeing anonymity or protection from all trading risks.
Be the first to comment