Pyth Network (PYTH)

Pyth takes the opposite approach to most oracles: instead of paying independent nodes to fetch prices from public APIs, it has the firms that actually make the markets publish their own data on-chain. The reasoning is direct — the party with the best price information is the one trading at that price.

First-party data removes a hop

A conventional oracle node reads a price from an exchange API and reports it. Pyth has exchanges and trading firms publish directly, signed with their own keys. There is no intermediary to be wrong or to be compromised, and the publisher's identity and reputation are attached to every update.

Aggregation includes a confidence interval

Publisher submissions are combined into a price and a confidence band expressing how much they disagree. That band is genuinely useful: a wide interval during volatility tells a contract that the price is uncertain, letting it widen margins or pause rather than acting on a number that looks precise and is not. Most oracles report a single figure and hide this entirely.

The pull model changes who pays

Rather than pushing updates on a schedule regardless of demand, prices are published to an off-chain layer and pulled on-chain by whoever needs them, at the moment they need them. The consumer pays for the update. This makes high-frequency feeds affordable for assets that could never justify continuous on-chain posting.

The trade-off to weigh

Data quality is excellent because it comes from market makers. Those same publishers are commercially active in the markets they report on, so the model depends on aggregation across many publishers to dilute any individual incentive to misreport. It is a different trust assumption from independent nodes, not an absent one.

What PYTH governs

The token governs the network's parameters, publisher set and fee distribution. Governance over which publishers may contribute is the substantive right here, since publisher quality is the entire product.