Two Distinct Systems
Whop benefits from two separate Aptos features that serve different purposes:
Archon provides speed. 10ms block times and 30ms inclusion confirmations. Central exchange responsiveness for an onchain system.
The encrypted mempool provides fairness. It prevents front-running by hiding transaction contents from validators until after block inclusion.
These are independent systems. Archon handles responsiveness. The encrypted mempool handles MEV protection.
MEV and Its Impact on Whop
MEV (Maximal Extractable Value) is value captured by reordering, inserting, or front-running transactions in a block. For a trading platform, the relevant forms are:
Front-running: A market maker or validator observes a large incoming taker order in the mempool and submits their own trade ahead of it. They buy low, the victim's order pushes the price up, they sell high. Extracting value from the victim's order.
Sandwich attack: An attacker brackets a known swap order: buy before it (to push price up), let it execute at the inflated price, sell after (collecting the spread). The victim gets worse execution than the mid-market price would warrant.
Permissionless crank timing: On systems with a permissionless crank (like Decibel perps), an attacker who controls crank timing can time matching to execute favorably positioned orders first. This is not front-running in the classical sense. It's a structural timing advantage from controlling when settlement happens.
For Whop specifically: Without MEV protection, a well-resourced market maker watching the mempool could see an incoming 500 BTC market buy and front-run it. Placing a limit buy slightly ahead, pushing the price, and selling into the victim's order. The victim pays more than the fair market price. The market maker captures the difference.
At scale, this extraction degrades execution quality for all non-sophisticated participants and concentrates value among those with infrastructure to observe the mempool. It undermines the premise of a fair exchange.
Archon Consensus Architecture
Archon is Aptos's Multi-Leader Primary-Proxy consensus architecture. It delivers low block times through parallelized block production:
- ›Multiple validators can simultaneously propose blocks (Multi-Leader)
- ›Block transmission is optimized through direct validator-to-validator communication (Primary-Proxy)
- ›Result: 10ms block times, 30ms inclusion for standard transactions
What Archon gives traders:
- ›Faster feedback: an order submitted to the mempool is included in a block within 30ms
- ›Tighter execution: a signal caller can enter a position and publish the call within a shorter window, making the entry-to-publication delay metric more granular and meaningful
- ›Better bot performance: AIP-125 keeper bots that trigger on Pyth price updates respond faster
- ›CEX-like responsiveness: a 30ms confirmation time is meaningfully close to the 5-10ms acknowledgment of a centralized exchange
What Archon does NOT give traders:
- ›MEV protection of any kind
- ›Fair ordering
- ›Protection against front-running
- ›Protection against information asymmetry from mempool observation
Archon makes the system fast. It has nothing to say about what happens to transaction ordering within those fast blocks.
The Encrypted Mempool
The encrypted mempool proposal encrypts transaction contents before validators see them. Validators order transactions into blocks based on metadata (gas price, nonce) without reading the transaction payload. The payload is decrypted only after the transaction is committed to a block.
The mechanism:
- 02User signs and encrypts their transaction payload using a threshold encryption scheme
- 04The encrypted transaction is broadcast to the mempool
- 06Validators see: sender, gas price, nonce, and encrypted payload (opaque ciphertext)
- 08Validators include transactions in blocks based on gas price priority. Identical to today
- 10Once the block is finalized, the payload is decrypted and executed
The critical property: no party can read the transaction contents before execution. Not validators. Not other market makers. Not infrastructure operators.
What this prevents:
- ›Front-running by validators (they can't read the order before including it)
- ›Front-running by other market makers with mempool infrastructure (the order is ciphertext to them)
- ›Sandwich attacks via mempool observation (the swap details are hidden until execution)
- ›Information asymmetry between those with mempool access and those without
What this does not prevent:
- ›MEV from block ordering (a validator can still sequence valid transactions within a block)
- ›Statistical front-running (observing patterns in trade timing even without reading content)
- ›Post-inclusion MEV from multi-block strategies
For Whop: Once the encrypted mempool is live, order flow on the Spot CLOB cannot be front-run by watching the mempool. A whale accumulating 10,000 BTC through the orderbook over 50 transactions has each of those transactions hidden from validators and market participants until after execution. Combined with UTT's position size privacy, the information available to potential front-runners is minimal.
Governance status: Proposed October 2025. Pending governance approval as of April 2026. Not yet live on mainnet.
The Whop Crankless Design and MEV
The spot CLOB's crankless design provides a different form of MEV protection orthogonal to the encrypted mempool.
On Decibel perps, the permissionless crank is a sandwich attack vector: an attacker observes the pending order queue, submits their own order to benefit from timing the crank. The attacker controls when the crank fires relative to the pending orders.
The Whop spot CLOB is atomic crankless. Settlement happens within the taker's transaction. It matches, books, and settles in a single atomic operation. There is no timing window between "order queued" and "order settled" for an attacker to exploit.
The combined picture:
- ›Crankless design eliminates crank-timing MEV (structural, already present at launch)
- ›UTT hides position sizes (structural, Zone 2 when deployed)
- ›Encrypted mempool hides transaction contents from validators (pending governance)
Each layer addresses a different MEV vector. The combination makes the Whop spot CLOB the most MEV-resistant onchain CLOB in the Aptos ecosystem.
Whop MEV Protection Stack
- ›Crankless CLOB: Eliminates crank-timing MEV. Matching happens atomically in the taker's transaction.
- ›UTT: Eliminates position size information leakage. Competitors cannot see settlement sizes.
- ›Encrypted mempool (pending governance): Will eliminate mempool observation front-running once live on mainnet.
The encrypted mempool is pending governance as of April 2026. Until it ships, the crankless design and UTT privacy provide the primary MEV defenses. For a full comparison to Hyperliquid, Lighter, Phoenix, and other exchanges, see the Competitive Landscape doc.