Decibel Trade switches on Aptos’ Encrypted Mempool to shield trader orders
- Published
- Updated
- Since then
- 2 new reports
- In
- Layer 1
Decibel Trade activated Aptos’ Encrypted Mempool, and Aptos said the feature is live on mainnet. The feature lets users encrypt transaction details before block ordering is finalized, and it is framed as a way to reduce MEV-style ordering attacks.
Key claims & sources
What it means
Public mempools on chains like Ethereum have let validators and searchers see pending trades before they land, a design flaw known since Flashbots documented MEV extraction in 2020. Sandwich bots and frontrunners exploit this visibility to insert trades around victims' orders, taxing swaps with worse execution. Aptos, built as a Move-based L1 since 2022, built the Encrypted Mempool to close that gap. Decibel Trade is the first production venue to switch it on for live order flow.
Traders using Decibel Trade now submit orders that validators cannot read until block ordering is locked in, meaning sandwich bots have nothing to target. Market makers and retail swappers gain tighter effective execution without needing private RPC endpoints or third-party MEV-protection relays. Validators lose the information edge that let some extract value from pending transactions. Other Aptos-based apps can adopt the same encryption layer rather than building their own privacy tooling.
MEV extraction has become one of the clearest value leaks in on-chain trading, visible wherever a public mempool exposes intent before execution. Encrypting that intent trades one problem for another: it hands more trust to the mechanism that decrypts transactions at the right moment, and that process still needs scrutiny over who holds the keys and when. A mempool that hides orders from predators can just as easily hide them from auditors if the decryption step is not itself verifiable.
Whether other Aptos-native exchanges and aggregators enable the Encrypted Mempool beyond Decibel Trade will show if this becomes a chain-wide default rather than a single venue's feature. Aptos has not set a mandate forcing adoption, so uptake depends on individual app teams weighing added latency against MEV protection. The next signal is which major Aptos DeFi protocol switches it on next.
Market reaction i
The move was larger before the first headline than after. That is an observation, not an explanation: the market also moves on things nobody publishes.
Coverage timeline
Every piece in order, with the time its news medium declares — if it is not believable we use ours and say so — and what it added to what was already known at that point. Arriving first is not the same as adding something.
Has this happened before?
| When | What happened | Figure |
|---|---|---|
| 25 days ago | Aptos Launches Encrypted Mempool To Hide Transactions Until Finality event | 1 actors in common · 4 news media |
| 28 days ago | Aptos moves Shelby storage into private beta with real customer workloads event | 1 actors in common · 2 news media |
| 30 days ago | Aptos unveils MonoMove, claiming up to 55x faster smart contract execution event | 1 actors in common · 3 news media |