Hook: The Unseen Tax on Every Transaction
On August 19, 2026, a small group of Ethereum researchers gathered for a call titled "Encrypt the Mempool." The agenda was ambitious: hide every pending transaction from MEV bots before they can frontrun. The trigger? Vitalik Buterin himself had been hit by the infamous Jaredfromsubway.eth bot just weeks earlier. The irony is sharp—the architect of Ethereum’s public ledger was bitten by its own transparency. But as I’ve learned from years of dissecting protocol patches, the most dangerous narratives are the ones that promise a clean fix. Correlation is a map, but causation is the terrain—and this terrain is full of trust assumptions no one wants to admit.
Context: The MEV Arms Race and the Memory Pool Problem
Today’s Ethereum mempool is a glass house. Every pending transaction is visible to anyone who cares to look. MEV searchers, operating sophisticated bots, scan this data for arbitrage opportunities, sandwich attacks, and liquidations. The result is an invisible tax on all users, estimated at $400 million per year at its peak. The current workaround is private relays—services that route transactions directly to block builders, bypassing the public mempool. But these relays are centralized intermediaries. They can censor, they can leak, and they introduce a new layer of trust. The Ethereum community’s answer is to build an encrypted mempool at the protocol level, so that transaction contents are hidden until they are included in a block. The leading proposals are EIP-8184 (LUCID), EIP-8105 (trust graph), and the inclusion list mechanism FOCIL (EIP-7805). Together, they form the backbone of what’s being called “the next frontier of MEV mitigation.”
Core: The Cryptographic Gordian Knot
Let’s start with LUCID. The idea is a commit-reveal scheme: a block builder submits a sealed envelope of transactions without knowing their contents. Only after the envelope is sealed does the key release happen, decrypting the block for execution. The bottleneck is the key release mechanism. LUCID proposes an external key publisher—either the transaction sender or a third party—who holds the decryption key until the commit phase ends. This is not a peer-to-peer solution; it’s a designated trust anchor. According to the EIP-8184 author, there is currently no known cryptographic construction that satisfies all the requirements for Ethereum’s scale: small public keys, non-interactive decryption, no trusted setup, practical ciphertext size, strong chosen-ciphertext security, and a credible path to post-quantum security. That’s a laundry list of impossibilities. In my experience auditing ICOs, I’ve seen projects promise “the impossible” and then quietly pivot to a centralized fallback. LUCID is doing the same—it’s admitting the cryptography isn’t ready and outsourcing trust to a key release node.
EIP-8105 takes a different approach. It introduces a directed trust graph, where registered providers can signal which other providers they trust. The trust, incentives, and penalization are all handled outside the consensus layer. This is effectively a reputation system grafted onto the protocol. It’s flexible, but it solves the problem of “who is honest” by punting it to a social layer. The ledger has no memory of promises; only code can enforce penalties. With no on-chain slashing for misbehavior, the trust graph is only as strong as the weakest set of colluding parties.
FOCIL (EIP-7805) is the inclusion list pipeline that ties these encrypted mempool proposals to the broader Ethereum roadmap. It allows multiple validators to signal which transactions a block builder must include, constraining the builder’s ability to censor. FOCIL is slated for the Hegotá upgrade in 2027 at the earliest. That means the encrypted mempool, as a system, cannot be deployed until the consensus layer supports these inclusion lists. The timeline is long—and the cryptographic hurdles are real.
The hidden cost of LUCID: the 1/8 gas limit and the reservation fee. The encrypted portion of a block is capped at one-eighth of the block gas limit, and the block builder must pay a reservation fee. If the key release fails, the builder loses the fee. This is a slashing mechanism in spirit, but it cannot distinguish between a malicious sender and a network failure. The result is a chilling effect on legitimate transactions—users may overpay in fees to avoid being penalized, or builders may refuse to include encrypted transactions altogether. The mechanism is designed to raise the cost of MEV attacks, but it does so by imposing a friction that hurts all participants.
Contrarian: The Trust Transfer That No One Is Talking About
Here’s the counter-intuitive truth: the encrypted mempool does not remove trust; it transfers it. Today, we trust block builders and private relay operators not to frontrun. Tomorrow, under LUCID, we would trust the key publishers. Under EIP-8105, we would trust the reputation graph gatekeepers. The attack surface shifts from “the mempool” to “the key release network.” The Ethereum community has a long history of fighting centralization, yet here they are proposing a scheme that by design creates a new class of trusted intermediaries. The key publisher is a single point of failure—or a small set of nodes that can be colluded with. The security assumptions are not materially better than those of a private relay. In fact, they may be worse, because the protocol now has a hard dependency on a party that is not even a validator. The ledger has no memory of the key publisher’s promises.
Moreover, the entire project assumes that the primary threat is frontrunning bots. But the biggest MEV today is not from retail frontrunning; it’s from sophisticated arbitrage strategies that actually improve market efficiency. The “evil” bots are a small fraction of the total. The encrypted mempool would also blind legitimate searchers, potentially reducing liquidity and increasing spreads. The protocol’s designers are solving for a worst-case scenario without accounting for the second-order effects on market structure. From my work tracking ETF inflows, I’ve learned that institutional participants rely on transparent order flow to hedge. Taking that away without a clear replacement could drive high-value traders to private channels or to other chains.
The post-quantum threat is the elephant in the room. The LUCID proposal explicitly requires “a credible path to post-quantum security.” But no known construction meets all the other requirements while being quantum-resistant. The timeline for Q-Day is now estimated at 2029 by some researchers. If Ethereum deploys an encrypted mempool in 2027 based on pre-quantum cryptography, it will need a major upgrade within two years to patch the vulnerability. That’s a recipe for disruption. The roadmap is building on sand.
Takeaway: Watch the Hegotá Upgrade, But Don’t Hold Your Breath
What does this mean for the average user? In the short term, nothing changes. The encrypted mempool is a research project, not a product. The real signal to watch is whether the cryptography community can produce a practical construction that satisfies all of LUCID’s requirements. If they can’t, the Ethereum ecosystem will likely converge on a hybrid solution—private relays with some protocol-level guarantees, but not full encryption. The Hegotá upgrade will include FOCIL, and that will be the true test: can inclusion lists alone reduce MEV enough to make the encryption debate less urgent? I suspect the answer is yes, and the encrypted mempool will remain a theoretical exercise for years.
But there is a more profound question: if we cannot trust the protocol to hide our transactions, do we trust third parties more? The history of finance—from clearinghouses to custodians—suggests we do. The encrypted mempool is a noble attempt to rebuild the trustless ideal, but the reality is that trust cannot be eliminated, only shifted. The next time you see a headline about “Ethereum hiding trades from bots,” remember: the code may be clever, but the trust is still human. Follow the gas, not the gossip.
