All Contract Addresses
Pyth Core (current), upgraded Pyth Core, and Pyth Pro contract addresses side by side for every supported chain.
Pyth has three kinds of on-chain contracts. This page explains how to tell them apart and lists all three side by side, per chain.
If you remember one thing: Pyth Core and Pyth Pro are two different products with two different shapes. The "upgraded" contract is not Pro. It's the next generation of the Pyth Core contract you already use: same interface, same feed IDs, now with the richer data and customizability that Pro introduced.
| What it is | Built for | |
|---|---|---|
| Pyth Core (current) | The contract you integrated against today. Keeps a shared price on-chain that any contract can read | Existing integrations |
| Pyth Core (upgraded) | The same interface and feed IDs at a new address, with richer data and more customization. Still keeps the shared price on-chain | Upgrading your existing integration: swap the contract address and the Hermes endpoint together, with an API key |
| Pyth Pro | A different model: no price stored on-chain. Each transaction carries its own millisecond-fresh signed price, verified on the spot | Latency-critical trading priced per transaction: perps fills, RFQ and quote-based execution |
The real difference between upgraded Core and Pro
Upgraded Core keeps one shared price on-chain.
- Your contract calls
getPriceNoOlderThanand reads the same canonical price every other protocol on the chain sees. - That's the shape lending markets, CDPs, and vaults are built around: liquidations triggered by third parties, share prices computed in view functions, protocols composing by reading the same stored value.
- Sponsored push feeds keep the price fresh, so passive protocols integrate with a single read.
- The upgrade changes none of this: same interface, same feed IDs, better data behind them.
Pyth Pro attaches the price to each transaction.
- Nothing is stored on-chain. Every transaction that needs a price carries a freshly signed one, verified on the spot.
- Each trade executes on a price that is milliseconds old: what perps fills and RFQ execution need, and what no stored price can provide.
- The trade-off: no shared price for other contracts to read.
One question decides it. Do other contracts, third-party liquidators, or view functions need to read your price on-chain? If yes, you want Core. If not, take a look at Pyth Pro.
What happened on August 26, 2026 at 16:00 UTC
- Your current contract was upgraded in place. It accepts the new data payloads automatically. You kept your address, and your feed IDs didn't change; nearly all feeds carried over (check yours).*
hermes.pyth.networkwas redirected to the upgraded backend. The URL keeps working, but every request needs a Pyth API Key since that day.- "Current" and "upgraded" are now the same thing, and that distinction is disappearing. What remains is Core vs Pro: the same upgraded data, either stored on-chain for everyone to read, or attached fresh to each transaction.
* Except on Sui, where the in-place upgrade isn't possible; see the Sui upgrade guide.
The two mistakes this page exists to prevent
- Swapping a Core integration to a Pro address. Pro has a different interface, different feed IDs, and no stored price to read, so it isn't a drop-in replacement for a Core integration. If you're upgrading Core, you want the upgraded Core address (listed below).
- Swapping the contract address without moving your data source, or vice versa. Each endpoint's payloads verify only on its own contract generation. The August 26 cutover switched both together for existing integrations; if you swap now, swap the contract address and the Hermes endpoint together.
Where to go next: the upgrade guide for the how, or the Pyth Pro docs if per-transaction pricing is what you need. All addresses, all three kinds, are below.
EVM
Mainnets
| Network | Pyth Core (current) | Pyth Core (upgraded) | Pyth Pro |
|---|---|---|---|
| 0G Mainnet | — | — | |
| Abstract | — | — | |
| ApeChain | — | — | |
| Arbitrum One | — | ||
| Arc | — | ||
| Astar zkEVM | — | — | |
| Aurora Mainnet | — | — | |
| Avalanche C-Chain | — | — | |
| Base | — | ||
| Berachain | — | ||
| BitTorrent Chain Mainnet | — | — | |
| Blast | — | — | |
| BNB Smart Chain Mainnet | — | ||
| Boba Network | — | — | |
| Camp Network Mainnet | — | — | |
| Canto | — | — | |
| Celo Mainnet | — | — | |
| Chiliz Chain Mainnet | — | — | |
| CLV Parachain | — | — | |
| Conflux eSpace | — | — | |
| Core Blockchain Mainnet | — | — | |
| Cronos Mainnet | — | ||
| Cronos zkEVM Mainnet | — | — | |
| Data Network | — | — | |
| EOS EVM Network | — | — | |
| Ethereal | — | — | |
| Ethereum Mainnet | — | ||
| Etherlink Mainnet | — | ||
| Eventum Mainnet | — | — | |
| Evmos | — | — | |
| Fantom Opera | — | — | |
| Filecoin - Mainnet | — | — | |
| Flow EVM Mainnet | — | ||
| Fluent | — | ||
| Gnosis | — | — | |
| Gravity Alpha Mainnet | — | — | |
| Hedera Mainnet | — | — | |
| Hemi | — | — | |
| Horizen EON Mainnet | — | — | |
| HyperEVM | — | ||
| Injective EVM | — | ||
| Ink | — | — | |
| IOTA EVM | — | — | |
| Kaia Mainnet | — | — | |
| Kava | — | — | |
| KCC Mainnet | — | — | |
| Kinto Mainnet | — | — | |
| Lightlink Phoenix Mainnet | — | — | |
| Linea | — | — | |
| Manta Pacific Mainnet | — | — | |
| Mantle | — | — | |
| MegaETH | — | ||
| Merlin Mainnet | — | — | |
| Meter Mainnet | — | — | |
| Mezo | — | ||
| Mode | — | — | |
| Monad | — | ||
| Morph | — | — | |
| Neon EVM Mainnet | — | — | |
| OP Mainnet | — | — | |
| opBNB Mainnet | — | — | |
| Orange | — | — | |
| Plasma Mainnet | — | — | |
| Polygon Mainnet | — | ||
| Polygon zkEVM | — | — | |
| Polynomial | — | — | |
| Robinhood Chain | — | ||
| Ronin Mainnet | — | — | |
| Scroll | — | — | |
| Sei Network | — | ||
| ShimmerEVM | — | — | |
| Skate Mainnet | — | — | |
| Soneium | — | ||
| Sonic Mainnet | — | ||
| Subtensor EVM | — | — | |
| Superseed | — | — | |
| Swellchain | — | — | |
| Taiko | — | — | |
| Tempo | — | ||
| Unichain | — | — | |
| Viction | — | — | |
| WEMIX3.0 Mainnet | — | — | |
| World Chain | — | — | |
| XCHAIN | — | — | |
| ZetaChain Mainnet | — | — | |
| ZKFair Mainnet | — | — | |
| zkSync Mainnet | — | — |
Testnets
| Network | Pyth Core (current) | Pyth Core (upgraded) | Pyth Pro |
|---|---|---|---|
| Abstract Sepolia Testnet | — | ||
| Amoy | — | — | |
| Arbitrum Blueberry | — | — | |
| Arbitrum Sepolia | — | ||
| Arc Network Testnet | — | ||
| Aurora Testnet | — | — | |
| Avalanche Fuji Testnet | — | — | |
| Base Sepolia Testnet | — | ||
| Berachain Bepolia | — | — | |
| BinaryChain Mainnet | — | — | |
| BitTorrent Chain Donau | — | — | |
| Blast Sepolia Testnet | — | — | |
| BNB Smart Chain Testnet | — | ||
| Boba Network Goerli Testnet | — | — | |
| Canto Tesnet | — | — | |
| Celo Alfajores Testnet | — | — | |
| Celo Sepolia Testnet | — | — | |
| Chiliz Spicy Testnet | — | — | |
| Conflux eSpace (Testnet) | — | — | |
| Converge Testnet | — | — | |
| Core Blockchain Testnet | — | — | |
| Core Blockchain Testnet2 | — | — | |
| Cronos Testnet | — | ||
| Cronos zkEVM Testnet | — | — | |
| Curtis | — | — | |
| Data Network Aeneid Testnet | — | — | |
| Dela Mithreum Deperp Testnet | — | — | |
| Dela Sepolia Testnet | — | — | |
| Edgeware EdgeEVM Mainnet | — | — | |
| EOS EVM Network Testnet | — | — | |
| Ethena Testnet | — | — | |
| Ethereal Testnet V2 | — | — | |
| Ethereum Hoodi | — | — | |
| Ethereum Sepolia | — | ||
| Etherlink Ghostnet Testnet | — | — | |
| Etherlink Shadownet Testnet | — | — | |
| Eventum Testnet | — | — | |
| Evmos Testnet | — | — | |
| Fantom Testnet | — | — | |
| Filecoin - Calibration testnet | — | — | |
| Flow EVM Testnet | — | — | |
| Fluent Testnet | — | — | |
| GIWA Sepolia Testnet | — | — | |
| Gnosis Chiado Testnet | — | — | |
| Hedera Testnet | — | — | |
| Hemi Sepolia | — | — | |
| Hyperliquid EVM Testnet | — | — | |
| Injective Testnet | — | ||
| Ink Sepolia | — | — | |
| Kaia Kairos Testnet | — | — | |
| Kakarot Starknet Sepolia | — | — | |
| Kava Testnet | — | — | |
| KCC Testnet | — | — | |
| Lightlink Pegasus Testnet | — | — | |
| Linea Goerli | — | — | |
| Linea Sepolia | — | ||
| Manta Pacific Sepolia Testnet | — | — | |
| Manta Pacific Testnet | — | — | |
| Mantle Sepolia Testnet | — | — | |
| MegaETH Testnet (Deprecated) | — | — | |
| Meter Testnet | — | — | |
| Mezo Testnet | — | ||
| Mode Testnet | — | — | |
| Monad Testnet | — | ||
| Morph Holesky | — | — | |
| Morph Hoodi | — | — | |
| Morph Testnet | — | — | |
| Movement EVM Testnet | — | — | |
| Mumbai | — | — | |
| Neon EVM Devnet | — | — | |
| Nollie Skatechain Testnet | — | — | |
| Olive Testnet | — | — | |
| OP Celestia Raspberry | — | — | |
| OP Sepolia Testnet | — | ||
| opBNB Testnet | — | — | |
| Parallel Testnet | — | — | |
| Polygon Blackberry | — | — | |
| Polygon zkEVM Testnet | — | — | |
| Polynomial Sepolia | — | — | |
| Reya Cronos | — | — | |
| Robinhood Chain Testnet | — | ||
| Scroll Sepolia Testnet | — | — | |
| Sei Testnet | — | — | |
| Shiden | — | — | |
| ShimmerEVM Testnet | — | — | |
| Soneium Testnet Minato | — | ||
| Sonic Blaze Testnet | — | ||
| Sonic Testnet | — | — | |
| Subtensor EVM Testnet | — | — | |
| Superseed Sepolia Testnet | — | — | |
| Swellchain Testnet | — | — | |
| Syndr Nitro Testnet | — | — | |
| Tabi Testnetv2 | — | — | |
| Taiko Hekla (deprecated) | — | — | |
| Taiko Hoodi | — | — | |
| Tempo Testnet | — | ||
| Unichain Sepolia Testnet | — | — | |
| WEMIX3.0 Testnet | — | — | |
| Won Network | — | — | |
| World Chain Sepolia Testnet | — | — | |
| XCHAIN Testnet | — | — | |
| ZetaChain Testnet | — | — | |
| zKatana | — | — | |
| ZKFair Testnet | — | — | |
| zkSync Sepolia Testnet | — | — |
A — means that flavor isn't deployed on the chain. If your chain has no upgraded address, contact the team.
Solana
Pyth Core programs
The same program addresses are used across SVM networks.
| Program | Pyth Core (current) | Pyth Core (upgraded) |
|---|---|---|
| Wormhole receiver | ||
| Solana receiver | ||
| Price feed |
Pyth Core is also deployed on other SVM chains, including Eclipse, Sonic, Atlas, and Fogo. See the Core Solana and SVM contract addresses page for those.
Push Feed Accounts (Mainnet)
Each Solana push feed lives at a PDA derived from the Price Feed program ID and the price feed ID. The Price Feed program ID changes at the upgrade, so every per-feed account address changes too. Below are the upgraded account addresses (shard 0) for every sponsored feed. For the current (pre-upgrade) addresses, see the push feeds on Solana page.
The price feeds listed below are currently sponsored in Solana mainnet and devnet.
| Name | Upgraded Account Address | Price Feed Id | Update Parameters |
|---|
Pyth Pro program
| Network | Pyth Pro |
|---|---|
| Solana Mainnet |
For devnet and testnet, see the Pyth Pro contract addresses page.
Sui
Mainnet
Testnet
Pyth Pro on Sui: see the Pyth Pro contract addresses page.
Chains with Pyth Pro only
Cardano and Stellar have native Pyth Pro deployments; see the Pyth Pro contract addresses page.
Don't see your chain, or unsure which contract applies to you? We're adding chains regularly and can discuss custom arrangements. Contact the team →