Lucid Encrypted Mempool

EIP-8184

Ethereum encrypted mempool initiative: live sandwich protection metrics, working group decisions, and specifications.

Protocol Architecture & MEV Genealogy

From Public Mempools to LUCID Encrypted Inclusion

The evolution of transaction visibility, ordering power, and censorship resistance in Ethereum: tracing how public mempool MEV led to PBS, inclusion lists (FOCIL), and LUCID (EIP-8184).

1. The Fundamental Question of Ethereum Block Construction

"Who gets to decide which transactions enter Ethereum, in what order, and how much information do they receive before making that decision?"

In traditional Ethereum, the mempool is an unencrypted gossip layer. Every pending transaction is visible to all network participants before block inclusion. While open, this transparency exposes users to predatory MEV, driving trade volume into private channels and creating centralizing dependencies.

2. Understanding the Three Types of MEV

External Markets

Exogenous MEV

Information originates outside Ethereum (e.g. price shifts on centralized exchanges like Binance creating arbitrage opportunities across DEX pools).

State Discrepancies

Endogenous MEV

Opportunities already present within existing Ethereum state (e.g. price imbalances between Uniswap and Sushiswap liquidity pools).

Transaction-Induced (LUCID Target)

Autogenous MEV

Opportunities created by the user transaction itself (e.g. a large trade shifting pool reserves). LUCID hides transaction parameters until inclusion is committed to eliminate autogenous exploitation.

3. The Mempool to LUCID Evolution Pipeline

How transaction privacy and inclusion mechanisms developed step-by-step.

01

Public Transaction Mempool

Base Layer (2015+)
Historical

Ethereum nodes maintain local pools of pending unencrypted transactions gossiped across the peer network.

Significance: Open and permissionless, but leaves all transaction parameters visible before block inclusion.
02

The Emergence of MEV

Maximal Extractable Value
Historical

Searchers inspect pending mempool transactions to extract profit via arbitrage, liquidations, and sandwich attacks.

Significance: Demonstrated that transaction ordering itself possesses substantial economic value.
03

Specialized Block Builders

Block Construction
Historical

Block construction shifts from simple validator sorting to specialized builders optimizing block profitability.

Significance: Began the separation between entity proposing blocks and entity constructing transaction bundles.
04

PBS & MEV-Boost

Off-Protocol PBS (2022)
Live

Post-Merge architecture where validators outsource execution block building to builders through trusted relays.

Significance: Democratized MEV rewards for validators but concentrated block construction power among a small set of builders.
05

Builder Censorship & Concentration

Centralization Threat
Historical

A small group of specialized builders came to control block construction, creating the capability to censor transactions.

Significance: Highlighted the core risk: whoever controls block building controls inclusion.
06

EIP-7547: Inclusion Lists

EIP-7547
SupersededSpec

Proposed allowing individual block proposers to specify transactions that builders must include in their payloads.

Significance: First major effort to restore proposer inclusion authority under Proposer-Builder Separation.
07

EIP-7805: FOCIL (Fork-Choice Inclusion Lists)

EIP-7805
In DevelopmentSpec

Committee-based inclusion lists enforced directly by consensus attesters through fork choice rules.

Significance: Makes transaction inclusion a protocol consensus requirement rather than relying on single proposers.
08

Private Order Flow Proliferation

Private Relays
Live

Users send transactions to private RPC endpoints to avoid public mempool sandwiching.

Significance: Protects users from front-running but risks starving the public mempool and centralizing order flow.
09

EIP-7732: Enshrined PBS (ePBS)

EIP-7732
In DevelopmentSpec

Moves Proposer-Builder Separation from off-protocol MEV-Boost directly into Ethereum consensus rules.

Significance: Establishes in-protocol builder bids and Payload Timeliness Committees (PTCs).
10

EIP-8184: LUCID Encrypted Mempool

EIP-8184
ProposedSpec

Public encrypted transaction inclusion with commit-before-reveal semantics using Sealed Transactions and key release.

Significance: Combines public permissionless inclusion with hidden transaction intent to eliminate front-running and sandwiching.
11

EIP-7886: Delayed Execution

EIP-7886
DraftSpec

Separates consensus block attestation from execution state processing to prevent bottlenecking validator nodes.

Significance: Allows complex payload processing without slowing down time-critical consensus voting.

4. Architecture Comparison: Public vs Private vs LUCID Encrypted Mempool

Feature / AttributePublic MempoolPrivate Order FlowLUCID (EIP-8184)
Visible Before InclusionYes (Plaintext)No (Hidden from public)No (Ciphertext until commit)
Public Permissionless PathYesNo (Requires private RPC)Yes (Public network)
Sandwich / Front-Running ProtectionPoor (Exposed)ModerateHigh (Commit-before-reveal)
Requires Trusted IntermediaryNoYes (Private Relays)No (Protocol Native)
Builder Plaintext VisibilityBefore commitmentBefore commitmentAfter commitment only
Censorship Resistance PairingStandard networkProvider dependentPaired with FOCIL (EIP-7805)

5. Intersecting Protocol EIP Ecosystem

AI Disclaimer: Some content or metadata on EIPsInsight may be AI-inferred or automatically compiled. If you find any discrepancy, please contact us at dev@avarch.org.