All Contract Addresses

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.

The real difference between upgraded Core and Pro

Upgraded Core keeps one shared price on-chain.

• Your contract calls getPriceNoOlderThan and 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.

What happens on August 18, 2026

• Your current contract is upgraded in place. It starts accepting the new data payloads automatically. You keep your address, and your feed IDs don't change; nearly all feeds carry over (check yours).*
• hermes.pyth.network is redirected to the upgraded backend. The URL keeps working, but every request needs a Pyth API Key from that day on.
• From then on, "current" and "upgraded" are the same thing, and that distinction disappears. 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

1. 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).
2. Swapping the contract address without moving your data source, or vice versa. Each endpoint's payloads verify only on its own contract generation. Swap both together, or wait and let August 18 switch both for you (expect a brief switchover window; see the wait-path guidance).

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

Testnets

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	HDwcJB...8SWWaQCopy	HDw2E7...pVYrVLCopy
Solana receiver	rec5EK...v5LtFJCopy	rec2HH...2cRyHpCopy
Price feed	pythWS...2biRsTCopy	pyt2F4...brPCouCopy

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.

Pyth Pro program

Network	Pyth Pro
Solana Mainnet	pytd2yyk641x7ak7mkaasSJVXh6YYZnC7wTmtgAyxPtCopy

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.

Chains with Pyth Core only

Aptos, CosmWasm, Fuel, Iota, Movement, Near, Starknet, and TON currently have Pyth Core contracts only. Their per-chain addresses are on the Pyth Core contract addresses pages.