Encrypted Mempools

This article provides insights on proposing encrypted mempools in various environments, offering a practical framework tailored to your context.

Ethereum’s public mempool has always been a double-edged sword.  On one hand, it reflects the openness of the network and allows for auditability. On the other, that same openness creates an “exploit window,” where pending transactions can be seen and acted upon before they’re finalized. This fuels

Encrypted mempools dramatically reduce censorship and malicious MEV, but face limitations such as potential collusion, rigid setups, and added latency. In this article, we’ll explore advanced, deployable cryptographic primitives - beyond FHE and MPC - that can address these limitations.

Myths and misconceptions about encrypted mempools can hinder adoption and obscure the value that they offer to Ethereum and its users.

Ethereum's $1 trillion security initiative aims to attract institutional capital, but the chain’s transparent mempool enables $1.8 billion in malicious MEV extraction.

Glamsterdam is Ethereum’s next big upgrade - and a chance to dramatically improve decentralization and censorship resistance. Shutter supports prioritizing EIP-7732 (ePBS) and EIP-7805 (FOCIL), with encrypted mempools and silent threshold encryption proposed as powerful future implementations.

Not all MEV is bad. Arbitrage and liquidations help DeFi run smoothly - but front-running and sandwich attacks exploit users. Shutter’s encrypted mempools stop the malicious kind while preserving the good, restoring fairness without killing efficiency. Here's how it works.

We appreciate the thoughtful perspectives of the analysts at a16z Crypto on the limitations and potential of encrypted mempools in addressing MEV (Maximal Extractable Value). Their recent blog post raises valid points and highlights genuine challenges. That said, we see several key issues differently and offer a perspective informed by

Front-running, vote manipulation, and leaked moves are killing trust in dApps. This post breaks down how the commit-reveal works to fix this - and how Shutter upgrades it with threshold encryption to keep dApps fair, private, and tamper-proof.