On August 19, 2024, a group of Ethereum researchers dialed into a call titled "Encrypt the Mempool." The agenda was ambitious: hide pending transactions from MEV bots before they can front-run, sandwich, or liquidate. The trigger was personal. Vitalik Buterin's own address had been hit by Jaredfromsubway.eth, a notorious MEV bot. The market yawned. But beneath the surface, a structural shift is being proposed—one that could redefine how Ethereum orders transactions. Yet the closer I examine the proposals, the more I see a rug pull waiting to happen. Not a malicious one, but a cryptographic one.
Context: The Mempool as a Battlefield
Every Ethereum transaction, before it's included in a block, sits in the public mempool. MEV bots scan this pool for profit opportunities. Current defenses are band-aids: private relays send transactions directly to miners, but they trust a centralized intermediary. Other solutions like threshold decryption or trusted hardware introduce new trust anchors. The core problem remains: the mempool is transparent. The proposals—EIP-8184 (LUCID), EIP-8105, and FOCIL (EIP-7805)—aim to encrypt the mempool at the protocol level. LUCID uses a commit-reveal scheme: block builders submit sealed transactions, then a key publisher releases the decryption key. EIP-8105 introduces a directed trust graph where participants vouch for each other. FOCIL, slated for the Hegota upgrade around 2027, adds a committee of validators to enforce inclusion. This is not a single solution; it's a pipeline.
Core: The Cryptographic Gap
LUCID's design sounds elegant. But the devil is in the primitives. The authors of EIP-8184 admit: "There is currently no known cryptographic construction that simultaneously satisfies all requirements at Ethereum scale." Those requirements include small public keys, non-interactive decryption, no trusted setup, compact ciphertexts, strong chosen-ciphertext security, and a credible path to quantum resistance. I have seen this gap before. In 2017, while auditing Uniswap V2's constant product formula, I identified an edge case where extreme volatility could cause rounding errors. That was a fixable bug. This is a fundamental missing piece. No single primitive exists today that meets every criterion. The LUCID proposal sidesteps this by outsourcing decryption to an external key publisher. That shifts the trust from the mempool to the key publisher. It is not a trustless system; it is a trust relocation. The 1/8 block gas limit on encrypted transactions is a band-aid, not a solution. It limits throughput but does not prevent a malicious key publisher from withholding keys. The economic penalty—a prepaid fee that is forfeited on failed reveal—can punish honest senders if the network glitches. This is not a rug pull by design, but by omission.
Contrarian: The Real Goal Is Raising Attack Costs
Most commentary frames this as Ethereum's attempt to kill MEV. I disagree. The real objective is to raise the cost of MEV attacks, not eliminate them. The 1/8 gas cap and prepaid fees make selective inclusion expensive. The trust graph in EIP-8105 creates a reputation layer that can be gamed but is harder to automate. FOCIL's inclusion list forces builders to include transactions that validators approve, reducing censorship. Yet the system remains brittle. The key publisher in LUCID is a single point of failure. The trust graph requires off-chain enforcement of penalties. The FOCIL committee itself could be captured. The path to quantum resistance is a decade away. The market should not price in a solution that is years from even a testnet. The real rug pull is the illusion that a protocol-level fix is imminent. Private relays will remain the pragmatic choice for 2025-2026. The Hegota upgrade may bring parts of this, but the full encrypted mempool is a 2028+ story.
Takeaway: Position for the Long Wait
Institutional capital flowing into Ethereum via ETFs should not be swayed by these proposals. The MEV problem is structural, and the solution is iterative. I am not shorting ETH, but I am shorting the hype around instant fixes. The code will speak louder than the press releases. Until I see a working testnet with a quantum-safe primitive, I consider this a research project, not a product. The next time you see a headline about encrypted mempools, remember: the cryptographic rug pull is still in the making. The question is not if, but when—and whether the trust assumptions will be worth the cost.
