Encrypt Ethereum's Mempool

Encrypt Ethereum's Mempool!
Support EIP-8105:
Protect Ethereum users against front running, sandwich attacks, and real-time censorship at the protocol level
Every Ethereum user has felt this.
You submit a trade. You click mint. You hit send. Moments later, you get a worse price, miss the NFT, or watch your transaction stall.

Nothing went wrong on your side. You just played in public, and someone else played faster.
This is not a wallet problem, not a DEX problem, not a user mistake. It's how Ethereum handles transactions by default. Before a transaction is confirmed, it sits visible in the public mempool. Bots, builders, and others can see your intent and use that visibility to extract value from you with front running and sandwich attacks.
This EIP-8105 "Universal Enshrined Encrypted Mempool" changes this default. It let's you send transactions that stay hidden from absolutely everyone until your transaction is locked in by the chain.
By integrating a native encrypted mempool into Ethereum, this EIP removes the conditions that enable front running, sandwich attacks, and real-time censorship, and creates a path towards one day protecting all Ethereum users by default!
This site exists to drive action 🚀:
Rally the community to support including the EIP in the next upgrade, Hegotá
Invite all privacy projects to participate as key providers in a neutral, open encrypted mempool

Join the Effort
EIP-8105 Presentation at ACDE #229, Jan 29, 2026
Resources
Ethresearch Discussion
GitHub PR
Proposal for Hegotá headliner
Encrypted Mempools and Ethereum’s Roadmap: Fix or Distraction?
Debunking Myths and Misconceptions Around Encrypted Mempools
Hegotá Should Complete the Holy Trinity of Censorship Resistance
8 Reasons Why Ethereum Needs an Encrypted Mempool
1. It stops malicious MEV at the root
2. Protection moves toward default
3. No more trusting private intermediaries
4. Gives stronger security guarantees for mainstream adoption
5. Protects against harmful MEV, while still allowing good MEV
6. Complements ePBS and FOCIL for stronger censorship resistance
7. Reduces builder concentration risk
8. Future-proof and technology-agnostic
I'm in! How Can I Join the Effort?

1. Love this EIP? Share it!
A post will be pre-generated, which you can edit.
Post on X/Twitter
Post on Farcaster

2. Give Feedback on the EIP
See EIP on Ethresearch

3. Become a Supporter and/or Key Provider for the EIP
Publicly endorse the EIP by getting listed as a supporter.
The EIP is tech agnostic. Ethereum's top privacy projects are invited to build encryption on top.
DM Shutter on X/Twitter
Voices from the Mempool
Momentum for an encrypted mempool on Ethereum is accelerating 🚀 New voices are added each week.
FAQs
General questions
What is EIP-8105 (Universal Enshrined Encrypted Mempool)?
Will this protect all Ethereum users by default?
Does the EIP provide long-term privacy?
How viable are encrypted mempools?
Is this proposed EIP and encrypted mempool controlled by one project?
Is this the same thing as a "private mempool"?
Technical Questions
Where are encrypted transactions placed in a block?
What does an encrypted transaction consist of?
What metadata leaks before decryption?
What is the latency impact?
How does the protocol ensure that encrypted transactions pay for their blockspace?
What prevents invalid encrypted transactions from wasting block space?
What incentives do builders have to include encrypted transactions?
How is back-running MEV handled? Who captures it?
What ensures that decryption happens on time?
What if key providers fail or behave maliciously?
How are key providers registered and trusted?
How does the protocol prevent Key ID front running?
How do encrypted transactions behave under reorgs or when scheduled?
Have a questions, comments, or want to get involved?
DM us: x.com/ShutterNetwork

Encrypt Ethereum's Mempool!

Support EIP-8105:Protect Ethereum users against front running, sandwich attacks, and real-time censorship at the protocol level

EIP-8105 Presentation at ACDE #229, Jan 29, 2026

Resources

Ethresearch DiscussionGitHub PRProposal for Hegotá headlinerEncrypted Mempools and Ethereum’s Roadmap: Fix or Distraction?Debunking Myths and Misconceptions Around Encrypted MempoolsHegotá Should Complete the Holy Trinity of Censorship Resistance

8 Reasons Why Ethereum Needs an Encrypted Mempool

1. It stops malicious MEV at the root

2. Protection moves toward default

3. No more trusting private intermediaries

4. Gives stronger security guarantees for mainstream adoption

5. Protects against harmful MEV, while still allowing good MEV

6. Complements ePBS and FOCIL for stronger censorship resistance

7. Reduces builder concentration risk

8. Future-proof and technology-agnostic

I'm in! How Can I Join the Effort?

1. Love this EIP? Share it!

2. Give Feedback on the EIP

3. Become a Supporter and/or Key Provider for the EIP

Voices from the Mempool

Momentum for an encrypted mempool on Ethereum is accelerating 🚀 New voices are added each week.

FAQs

General questions

What is EIP-8105 (Universal Enshrined Encrypted Mempool)?

Will this protect all Ethereum users by default?

Does the EIP provide long-term privacy?

How viable are encrypted mempools?

Is this proposed EIP and encrypted mempool controlled by one project?

Is this the same thing as a "private mempool"?

Technical Questions

Where are encrypted transactions placed in a block?

What does an encrypted transaction consist of?

What metadata leaks before decryption?

What is the latency impact?

How does the protocol ensure that encrypted transactions pay for their blockspace?

What prevents invalid encrypted transactions from wasting block space?

What incentives do builders have to include encrypted transactions?

How is back-running MEV handled? Who captures it?

What ensures that decryption happens on time?

What if key providers fail or behave maliciously?

How are key providers registered and trusted?

How does the protocol prevent Key ID front running?

How do encrypted transactions behave under reorgs or when scheduled?

Have a questions, comments, or want to get involved?

DM us: x.com/ShutterNetwork

Support EIP-8105:
Protect Ethereum users against front running, sandwich attacks, and real-time censorship at the protocol level

Ethresearch Discussion
GitHub PR
Proposal for Hegotá headliner
Encrypted Mempools and Ethereum’s Roadmap: Fix or Distraction?
Debunking Myths and Misconceptions Around Encrypted Mempools
Hegotá Should Complete the Holy Trinity of Censorship Resistance