Ethereum’s mempool gets a privacy upgrade

Why This Proposal Matters

Ethereum has spent years treating the public mempool like a necessary inconvenience. It is transparent, efficient, and brutally easy to exploit. EIP-8105 proposes a different bargain: encrypt pending transactions until inclusion, then reveal them after the fact. That sounds like a narrow technical adjustment, but it reaches into the core of MEV, order flow, censorship resistance, and the economics of block production. If the proposal gains traction, the market will have to think less about raw transaction visibility and more about who controls decryption, ordering, and timing.

The reason this matters now is simple: Ethereum’s current architecture still leaves users exposed to sandwich attacks, backrunning, and other forms of value extraction that thrive in a public mempool. The proposal is explicitly scheme-agnostic, which means it is designed to accommodate several encryption approaches rather than locking Ethereum into one cryptographic path. That flexibility is useful, but it also signals that the technical and governance debates are not settled. In other words, the proposal is as much about institutional design as it is about cryptography.

What EIP-8105 Is Actually Changing

At the center of EIP-8105 is a universal encrypted mempool concept. Rather than broadcasting transaction payloads openly before block inclusion, the system would keep them hidden until the transaction is confirmed in a block. The proposal also appears to rely on a registry of key publishers and a controlled decryption process, which is meant to reduce the ability of outside actors to inspect and exploit pending orders. The exact mechanism is important, but the larger point is more important: the mempool becomes less of a public auction and more of a cryptographically mediated queue.

Recent discussion around the proposal shows that Ethereum developers are not merely debating encryption in the abstract. A separate design direction, often discussed under the name LUCID, has emerged as an alternative path, and recent community discussions suggest the original EIP-8105 framing has been reconsidered in favor of a two-slot approach with different privacy and penalty assumptions. That does not make EIP-8105 irrelevant. It makes it a live reference point in a broader redesign effort, one that reflects a real tension between elegance, flexibility, and deployability.

The Real Trade-Off Is Trust, Not Just Privacy

The dominant narrative says encrypted mempools are simply “better privacy.” That is too shallow. The real question is what kind of trust Ethereum is willing to introduce in order to reduce malicious MEV. Any encrypted design creates dependencies: on key distribution, on reveal timing, on validator coordination, and potentially on additional infrastructure that is less transparent than the current mempool. That is the uncomfortable truth. The more the network hides, the more carefully it has to define who is allowed to see what, and when.

That matters structurally because Ethereum’s market design has always rewarded the fastest reader of public information. An encrypted mempool would not eliminate competition; it would relocate it. The competition would move from mempool surveillance to cryptographic infrastructure, validator behavior, and the economics of inclusion. For builders, wallets, and trading systems, that means the edge may shift from speed to integration quality. For users, the promise is cleaner execution. For the protocol, the cost may be a more complicated trust surface.

What This Means For Investors

For investors, the key takeaway is that Ethereum’s value proposition is widening beyond settlement into market design. If encrypted mempool architecture matures, it strengthens the argument that Ethereum is not just a smart contract platform, but a programmable execution layer trying to reduce the tax of adversarial order flow. That is not an immediate catalyst for price, but it is a meaningful structural narrative. Networks that can credibly reduce extractive friction often attract more serious activity over time, especially from users who care about predictable execution rather than speculation alone.

What to watch next is whether Ethereum core developers converge on one encrypted mempool architecture, or whether the field fragments into competing implementations. Also watch for concrete moves around key management, penalty logic, and validator integration. Those details will tell you whether the proposal is heading toward protocol reality or remaining a research-grade blueprint.

Focus: Ethereum is not just trying to hide transactions; it is trying to rewrite who captures value from them.

Adam McCauley, Senior Blockchain Analyst, The Chain Journal