Pyth doesn't 'live' on any one consumer chain. The aggregation runs on Pythnet; consumer chains just host a verifier — a small contract that knows how to check Pyth's signatures and expose the latest signed update to any caller. A 'supported' chain is one where that verifier has been deployed and is being kept up to date.
What gets deployed per chain
- The verifier contract (Pyth's signature scheme plus storage for the latest update per feed)
- A small permissioned set of admin keys for upgrades
- Supporting infrastructure to attest cross-chain messages (Pyth uses Wormhole)
What the same feed ID means across chains
Feed IDs are global: BTC/USD has the same 32-byte identifier on every chain Pyth supports. A protocol building on multiple chains can use the same ID everywhere without translation tables. The verifier on each chain reads from the same Pythnet source of truth, so the price you read is consistent across all of them within their respective update windows.
Adding a new chain
When Pyth integrates a new chain, the work is: port the verifier contract to the chain's language/VM, deploy it, configure relayers to ship updates to it, and confirm cross-chain attestation is wired through. This is one-time work per chain — once done, the chain inherits the entire feed catalog automatically.
How to verify a chain's support
/chains on Pythscan lists every chain we've cataloged. The canonical source for whether a chain has an active verifier is the Pyth docs page for that chain — it shows the verifier contract address.