Uniswap's 'Swap Privately' RFC: Privacy Trojan or Compliance Trojan Horse?

A new Request for Comments on Uniswap's governance forum is quietly rewriting the rulebook on DeFi privacy. Filed by a team calling themselves SilentSwap, the RFC proposes a feature called 'Swap Privately'—a native integration of zk-SNARKs, UniswapX, and v4 Hooks to shield user transactions from MEV bots. But buried in the technical specs is a pre-execution compliance screener. And that screener, in my view, is the real story. For years, DeFi has lurched between two poles: radical anonymity (hello, Tornado Cash) and total transparency (hello, MEV extraction). Uniswap, the liquidity giant processing billions daily, has mostly sat on the fence, offering no native privacy beyond what users hack together with private RPC endpoints. This RFC aims to change that. The pitch is seductive: a single checkbox in the Uniswap interface that routes your trade through a private channel, using zero-knowledge proofs to verify your compliance with off-chain sanctions lists—without revealing your identity. Speed is the asset, but silence is the warning. Here’s the architecture, stripped of hype. The user’s swap intent is first sent to an off-chain relayer—a 'compliance filter.' That filter runs a sanctions check (e.g., OFAC list) using a privacy-preserving oracle. If you pass, the relayer submits a zk-SNARK proof along with your order to the UniswapX filler network. The filler executes the trade on v4 pools with a custom Hook that validates the proof. The result: your wallet address is never exposed to the public mempool, and the filler sees only a blinded order. On paper, it’s elegant. In practice, it’s a minefield. I’ve spent a decade watching DeFi protocols collapse under the weight of their own complexity. Every extra component—a relayer, a compliance oracle, a zk-prover, a v4 Hook—is an attack surface. The 0x flash loan heist I broke in 2020 taught me that the most lethal exploits hide in the handoffs between systems. This RFC adds at least three new handoffs. The compliance filter alone is a single point of trust: who runs it? What jurisdiction? Can it be forked? The RFC doesn’t answer these questions. It doesn’t even specify whether the filter uses a centralized API or a decentralized oracle network. Gravity always wins, even in a vertical chain. Now the contrarian angle—the one most coverage will miss. This RFC isn’t really about privacy. It’s about regulatory viability. By integrating a pre-execution compliance check, Uniswap is signaling to the SEC and global regulators: 'We can play ball.' The subtext is clear: if you give us a clear rulebook for sanctions screening, we’ll automate it into our core protocol. That’s a massive shift from code-is-law orthodoxy. The house didn't know it was playing with fire until the fire started burning the furniture. Here, the furniture is the principle of permissionless access. Will this RFC pass governance? Unlikely in its current form. The Uniswap DAO is famously fractious, and power users—the ones filling orders—will resist anything that adds friction or exposes their order flow to a centralized filter. But the signal is worth tracking. If a watered-down version lands on mainnet within a year, it will force every major DEX to follow suit. The winners won’t be users or protocols. They’ll be the infrastructure players—compliance-as-a-service platforms, zk-rollup provers, and private relayers. FOMO drove the bus; reality hit the brakes. My takeaway after dissecting the RFC’s code references and forum discussions: this is a high-upside, high-risk experiment. The privacy benefits are real—your Uncle Bob won’t get sandwich-attacked on his Uniswap trade. But the trade-off is a subtle erosion of DeFi’s core promise: that no gatekeeper sits between you and the pool. Keep your eyes on the compliance filter. If it turns into a mandatory KYC checkpoint, the privacy trojan horse becomes a compliance Trojan horse. And in crypto, the horse always decides the destination.