Douro Labs Tells CFTC: Liquidation Prices Need Many Sources, Not One

Douro Labs, the core contributor to Pyth Network, has formally asked the CFTC to require that crypto liquidations triggered by outside price feeds draw from multiple sources rather than a single exchange. The submission responds to the Commodity Futures Trading Commission's request for input on future rules for crypto asset markets. At stake is how margin calls and liquidations get priced when an exchange looks beyond its own order book.

The letter anchors its argument in a concrete failure. In 2021, Bitcoin printed at $8,200 on Binance.US while trading above $63,000 on other venues. That is not a rounding error. It is a roughly 87% divergence on the same asset at the same moment, and any liquidation engine keyed to the wrong venue would have wiped out positions that were healthy everywhere else.

Douro Labs presents the episode as a structural warning. Let one exchange's price decide liquidations, and you import that exchange's outages, glitches and thin liquidity into every margin account tied to it. The company's central pitch to regulators is simple: when exchanges use external prices to set margin and trigger liquidations, those prices should be aggregated across many venues.

What does this change for oracle regulation?

The second half of the letter is arguably the sharper one. Douro Labs asks the CFTC to evaluate oracles on how they are built, not on whether they appear on a fixed list of approved providers.

This is a direct jab at one likely regulatory instinct. A pre-approved list of price feeds is easy to write into a rulebook. It is also, in Douro Labs' telling, a gift to incumbents. The company argues a fixed list would lock in the largest players and freeze out newer architectures regardless of their engineering quality.

Design-based evaluation would instead ask questions like: how many sources feed the aggregate? How are outliers handled? How fast does the price update? That approach rewards construction over brand recognition.

Douro Labs is not a disinterested observer here, and its filing does not pretend otherwise. Pyth Pro, the price service the company develops and operates for the PYTH network, already works on exactly the basis it is recommending. In a separate CFTC filing, Douro Labs described Pyth Pro as an aggregated reference-price service that computes a single real-time reference price for each supported instrument.

So the letter doubles as a policy position and a market position. If the CFTC adopts design criteria over approved lists, services built on aggregation — Pyth Pro among them — clear the bar by construction.

Why the 2021 example still matters

The Binance.US episode is four years old, but the risk it illustrates has not aged out. Liquidation infrastructure has only grown more cross-referenced since, with lending protocols and perpetuals venues increasingly relying on external oracles to mark positions.

A single-venue feed concentrates failure in one place. An aggregate spreads it. That is the whole of Douro Labs' argument, reduced to one line, and it lines up with how traditional markets already treat reference prices — benchmarks like LIBOR's successors were rebuilt precisely because single-source quoting proved fragile.

The CFTC's request for input is the opening move in what could become the first comprehensive federal rulebook for crypto asset market structure under the agency's jurisdiction. Submissions like this one will shape which price-verification standards end up in any final rule. Market participants now wait on the Commission's next step, with any proposed rule on oracle standards likely to determine which price providers become infrastructure — and which become footnotes.