Shutter Blog

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 harmful

What if your AI could launch time-locked encrypted workflows with just a few prompts? That’s now possible with today’s release of the testnet alpha of Shutter MCP, powered by Shutter API. With Shutter MCP, your AI can set up and run: * Confidential request for proposals * Sealed bug bounties

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.

DAO voters have long demanded permanent private voting. It’s now on Shutter’s roadmap. This post shares the architecture and a working POC showing how we’re extending threshold-encrypted voting with ElGamal-based homomorphic tallying - so votes are counted in the encrypted state and remain private.

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