Aptos has launched opt-in encryption for pending transactions on mainnet, the network said in an October 12 announcement. The feature hides a transaction's payload while validators establish its ordering, then reveals it for execution. It does not turn Aptos into a permanently private ledger.
The rollout addresses a specific exposure: a pending transaction can disclose what a user intends to do before the blockchain processes it. For a trader, that information may give another participant an opportunity to trade ahead of the order. Encrypting the payload changes what observers can learn during that interval, rather than removing the public record afterward.
Ordering first, disclosure afterward
Aptos says the sender encrypts the payload before submission. Validators agree on the block while its transaction contents remain concealed, collectively decrypt the committed transactions and then execute them. The sender address and gas-fee fields remain visible. Petra is the first wallet to expose the option in its signing flow; Decibel's planned use is a future integration, not evidence that every exchange order already uses it.
The underlying AIP-144 specification describes threshold encryption integrated with consensus. Validators hold separate key shares, so one validator cannot simply unlock pending payloads alone. Shares are released after consensus confirms the block. The design also binds encrypted data to its sender, addressing an attack in which another account copies a ciphertext to expose the original user's intent.
This is a change to the pending-transaction stage. Our explanation of how a mempool works provides the broader distinction between waiting transactions and confirmed blockchain history, although Bitcoin's implementation and security model differ from Aptos.
Integration has costs and visibility limits
Aptos's developer documentation confirms mainnet availability and describes an encrypted build option in the TypeScript SDK. It also specifies a minimum gas-unit price of 200 Octas and an additional 375 gas units for decryption. Those charges mean encryption is not simply a free switch layered onto every existing transaction.
The documentation warns against simulating a plaintext version immediately before submitting its encrypted counterpart: observers could correlate the two and infer the supposedly hidden payload. It lists unsupported signer types and notes that some sponsored configurations expose an entry function. The amount of information disclosed therefore depends on the actual transaction construction, not just the presence of an encryption option.
Protection is not a guarantee of a better trade
Reducing advance visibility can limit one route to exploiting an order, but it does not eliminate market risk. A transaction can still encounter price movement, insufficient liquidity or adverse execution conditions. A user should not read payload encryption as a guarantee that a swap will receive its expected price.
Aptos reports roughly 20 milliseconds of extra latency in a 50-node benchmark. That is a benchmark result, not an independently measured promise for every live transaction. Adoption, wallet defaults and integration quality will determine how widely the new protection is actually used.