Don Wilson, founder of DRW and its crypto arm Cumberland, recently stated that regulators fundamentally misunderstand perpetual futures. This is not a polite disagreement. It is a structural conflict between two incompatible incentive systems: one designed for investor protection through central clearing, the other optimized for capital efficiency through decentralized risk transfer.
I have spent the last five years auditing smart contracts for zero-knowledge proofs and DeFi protocols. Perpetual futures are one of the most technically elegant instruments in crypto. They solve a real problem: how to offer leveraged exposure without an expiry date. The mechanism—funding rate, mark price, liquidation engine—is a self-regulating feedback loop that mirrors the continuous settlement of a CME futures contract but without the intermediary.
Hook: The Code Says Something Different
Wilson’s criticism centers on the gap between what regulators assume perpetual futures are and what they actually are under the hood. In a recent interview, he warned that this "misunderstanding" could stifle innovation and prevent broader adoption across industries.
The raw smart contract logic of a perpetual futures protocol—say, GMX v2 or dYdX v4—reveals a system that is not a security, not a derivative in the traditional sense, and not a casino. It is a peer-to-peer market for synthetic exposure, collateralized by on-chain assets, with forced liquidations triggered by oracle price feeds. The state machine is deterministic. There is no counterparty risk beyond the liquidity pool’s solvency.
Context: The Protocol Mechanics
Perpetual futures (perps) were invented by BitMEX in 2016. Since then, they have evolved into the most traded product in crypto, surpassing spot volume by orders of magnitude. The core innovation is the funding rate: a periodic payment between longs and shorts that anchors the perp price to the spot price. No expiry, no delivery, just synthetic exposure.
Wilson’s firm, DRW, is a major market maker in both traditional and crypto derivatives. His view carries weight. When he says regulators misunderstand, he is not referring to a lack of education. He is referring to a categorical error: treating perps as though they are unregulated securities or futures contracts under the Commodity Exchange Act.
Core: Code-Level Analysis and Trade-offs
Let me be precise. I have personally reviewed the liquidation logic of several perp protocols. The typical contract defines a position’s health as a function of collateral, notional size, and mark price. If the health falls below a threshold, the position is liquidated by a keeper who receives a fee. This is automated and transparent.
The regulatory concern centers on leverage—sometimes up to 100x—and the absence of a central clearing party (CCP). But from a game-theoretic perspective, the perp design already includes built-in risk controls that are more responsive than any CCP’s margin model. The funding rate adjusts in real time based on demand. The liquidation engine runs continuously. There is no need for a daily settlement window.
Yet regulators trained on the 2008 financial crisis see a product that amplifies systemic risk without backstops. They see retail traders losing everything. They see exchange failures (FTX) and conclude that any unregulated derivative must be dangerous.
Math doesn’t care about your jurisdiction. The equations that govern a perp’s solvency are the same on Ethereum mainnet as they are on a private database. The difference is verifiability. On-chain, every liquidation, every funding payment, every oracle update is auditable in real time. Off-chain, you need a subpoena.
Contrarian: The Blind Spots in Wilson’s Critique
Wilson’s framing is correct but incomplete. He argues that misunderstanding leads to bad regulation. But the deeper issue is that regulators fear losing control over financial plumbing. If perps become a standard tool for corporations and funds to hedge exposure, the existing derivatives exchanges (CME, ICE) lose market share. The regulatory capture dynamic is real.
There is also a blind spot in Wilson’s own position. DRW profits from market making in perps. Regulation that kills perps would hurt his business. So his critique, while technically sound, also serves a commercial interest. I have seen this pattern before: projects preach decentralization until the tax bill arrives.
The real risk is not that regulators misunderstand perps. It is that they understand them perfectly but choose to limit them for reasons other than safety. In that case, no amount of technical education will help.
Privacy is a protocol, not a policy. The on-chain nature of perps also creates privacy concerns. A regulator can see all positions of a single address. If KYC is required at the protocol level, the pseudonymity vanishes. This is a feature for compliance but a bug for users who value financial privacy.
Takeaway: Vulnerability Forecast
Expect a bifurcation. Regulatory-driven bans on perps in major jurisdictions (US, EU) will push volume to unregulated offshore exchanges or to fully decentralized protocols on L2s. The latter are harder to shut down but face high proof-generation costs today.
Based on my experience auditing ZK-rollup circuits, I predict that within two years, we will see a perp protocol built on a privacy-preserving ZK-rollup that offers leverage while hiding both positions and counterparties. That will trigger a second wave of regulation. The conflict will not end; it will escalate.
Wilson is right about the misunderstanding. But the solution is not to persuade regulators. It is to build systems that cannot be regulated in the traditional sense. That is the only technically honest path forward.
The funding rate is not a bug. It is a mechanism. Regulators can either learn to read the source code—or they can watch the market trade without them.