A publisher in Pyth is the entity that originated a trade or quote and is signing for it directly. The publisher set is the part of Pyth that most clearly distinguishes it from earlier oracle designs: instead of a tier of nodes scraping public exchange APIs and re-publishing, Pyth's contributors are themselves the exchanges and market makers — names like Binance, OKX, Coinbase, Jane Street, Virtu, and Wintermute, alongside roughly two hundred others.
What a publisher submits
- A price — their best estimate of fair value at that moment
- A confidence interval — how tightly they believe their own estimate
- A status flag — Trading, Halted, Auction, or Unknown
Submissions land on Pythnet and flow into the per-feed aggregation that produces the public price every consumer reads.
Why first-party matters
If a feed is wrong, there is an identifiable party who signed it. That accountability is enforceable through Oracle Integrity Staking: PYTH holders stake against specific publishers, and a publisher caught submitting manifestly bad data is slashed — taking the delegated stake with them. Earlier oracle models could not attribute a slash to a specific reporter, so the slashing signal was weak.
Where to find them on Pythscan
/publishers lists every publisher in our catalog. Each profile shows the publisher type (CEX, market maker, prop firm, etc.) and the asset classes they contribute to. Per-publisher feed mappings are kept internal, in line with Pyth's own posture on publisher-key privacy.