Uniswap’s governance community is debating a proposal that would let users execute swaps privately — without exposing their transaction details to the public mempool. The request for comment, filed by the team behind SilentSwap, outlines an optional “Swap Privately” path built on Uniswap v4 hooks and UniswapX.
Standard swaps wouldn’t change, and pool fees would stay the same. But the proposal tackles a long-standing pain point in decentralized finance: the transparent nature of on-chain swaps, which allows bots to front-run, sandwich attack, or exploit users based on leaked transaction intent.
How the privacy layer would work
The suggested architecture relies on zero-knowledge proofs — specifically zk-SNARKs — to hide swap details while still verifying them on-chain. It pairs that privacy with a pre-execution compliance screen, meaning the system would check an address against a list before letting a private trade go through.
That compliance step is notable. In earlier DeFi privacy debates, screening was often seen as an afterthought or a political concession. Here it’s baked in from the start, signaling a more mature conversation about how privacy and regulation can coexist in decentralized markets.
The RFC is still just a discussion. It’s not a live product or even an approved upgrade. Uniswap v4 hooks, which let developers customize pool behavior, make the technical approach possible. UniswapX, the protocol’s filler-based swap execution system, provides the infrastructure for routing private orders without exposing them to the public order book.
Why privacy matters in DeFi right now
On-chain transparency has always been a double-edged sword. It gives users verifiability and trustlessness, but it also opens the door to a whole class of extractive trading strategies. Bots monitoring the mempool can spot a pending large swap, buy the asset first to drive up the price, then sell it back to the swapper at a worse rate — the classic sandwich attack.
Private execution paths exist elsewhere — Flashbots, CoW Swap, and some layer-2 solutions offer ways to send transactions directly to validators or use batch auctions. But integrating that privacy into Uniswap’s core swap flow, even as an optional toggle, would bring it to the largest DEX by volume. That could shift user expectations across the entire market.
Governance hurdles ahead
The RFC faces a long road before any code lands on mainnet. Governance participants are already raising questions about technical safety — can the zk-SNARK system be trusted not to leak data? About user experience — will the extra step of compliance screening slow down trades? And about risk — if the screening is done by a centralized list, who controls it and how is it updated?
SilentSwap’s proposal pairs privacy with compliance, but it also puts the burden of defining “compliant” on the protocol’s governance. That’s a messy political question, especially as regulators around the world take a harder look at DeFi.
Uniswap’s size means whatever decision the community makes — approve, reject, or send back for redesign — will ripple through the ecosystem. Other DEXs will watch closely. Builders working on private execution will see which trade-offs are acceptable to a mainstream DeFi audience.
The conversation is just starting. No vote has been scheduled. Whether the optional privacy feature ever becomes a real toggle on the swap page depends on how Uniswap’s governance resolves those safety, compliance, UX, and risk questions in the weeks ahead.
