The Price Feed Council is one of three councils elected by Pyth token holders. Its mandate is the feed catalog: which instruments get listed as Pyth feeds, which get retired, and the quality standards new listings have to meet. Most feed-related operational changes flow through this council without needing a DAO-wide vote.
What it decides
- New feed listings — including the asset class, the publisher set that will support it, and the launch timing
- Deprecation — when a feed is no longer being maintained or has lost publisher support
- Listing standards — what makes a feed eligible (market liquidity, available publisher quotes, demand from integrators)
What it doesn't decide
The Price Feed Council operates within the bounds set by the Constitution. Anything that changes oracle parameters more broadly (slashing rules, aggregation thresholds) belongs to the Pythian Council. Anything that changes the Constitution itself, or moves treasury funds, requires a DAO-wide stake-weighted vote (an EXC-PIP).
How proposals work
A request to list a new feed or remove an existing one typically starts on the Pyth DAO forum. After discussion, the proposal is brought to the council. The council executes its decision through an on-chain multisig — check the Constitution for the current member count and signing threshold.
Where to follow it on Pythscan
The /councils/price-feed page has the current member roster and cycle history. /governance mirrors the forum and surfaces Price Feed Council proposals as they're posted.