The homepage provides the clearest current operational framing: Pyth is selling itself as a broad market-data layer with first-party publishers, thousands of feeds, and multi-chain distribution.
The docs whitepaper page is useful because it states the core thesis in one place: direct-from-source financial data, including equities, FX, crypto, and metals, made available to any L1 blockchain.
The Whitepaper 2.0 announcement is the most concise current source for the design transition that matters analytically: Pyth uses a pull-based cross-chain delivery model, Pythnet handles aggregation/broadcast, and consumers pay update fees.
That announcement is also where governance importance becomes explicit: fee policy, reward distribution, and publisher permissioning are described as governance subjects.
The governance portal confirms there is a live permissions-and-proposals surface, which matters because Pyth’s practical decentralization depends not just on data publishers but on who can admit publishers and tune incentives.
Open questions for a later pass
Pull more detail from the whitepaper PDF on aggregation, confidence intervals, and publisher incentive mechanics.
Compare Pyth’s first-party publisher model directly against Chainlink’s node/operator model and Chronicle’s signer / source assumptions.
Add a more explicit note on where publisher admission could create cartel dynamics despite the “first-party data” framing.