Completing the Pyth Core upgrade
Everything you need to bring your Pyth Core integration up to date with the August 26, 2026 upgrade.
Pyth Network upgraded Pyth Core on August 26, 2026 at 16:00 UTC. Existing integrations kept working: the on-chain Pyth contract was upgraded in place by the Pyth DAO (except on Sui, which requires a manual swap), and Hermes requests are served by the upgraded backend automatically. The one new requirement is authentication on Hermes: every Hermes user needs a Pyth API Key.
For background on what changed and why, see the upgrade overview. For a walkthrough of the signers, data flow, and contracts behind the upgrade, see How the Pyth Core upgrade works.
All Hermes users need a Pyth API Key — hermes.pyth.network now requires
authentication, including for integrations that were upgraded automatically.
Register at Pyth Terminal →
Does this apply to you?
- Your app calls
hermes.pyth.network? Get a Pyth API Key in Step 1. - You use Pyth Core contracts on-chain? The DAO upgraded the current addresses in place on August 26 — no swap is required, except on Sui (see the decision section below).
- You only use a protocol that already integrates Pyth? No action needed from your side.
Your upgrade path
Step 1: Get a Pyth API Key
Required for everyone who calls Hermes. Sign up at Pyth Terminal: a free trial is included, paid plans cover ongoing use.
Sign up at Pyth Terminal
Step 2: Early upgrade or wait for automatic?
After Step 1, pick the path that matches your integration. Your choice is saved in the URL so you can share or bookmark a specific path.
Sui consumers must upgrade manually
The "Wait for automatic" path does not apply on Sui. Apps reference the Pyth package by object ID, and the DAO cannot swap that for you. See the Sui upgrade guide.
| Early upgrade (recommended) | Automatic upgrade | |
|---|---|---|
| Timing | You choose | Happened on August 26, 2026 at 16:00 UTC |
| Downtime | Up to you | Brief, during the switch |
| Hermes endpoint | Switch to the new Hermes endpoint | Keep using hermes.pyth.network, now with an API key |
| Contract address | You swap to the upgraded Pyth Core Contract | DAO upgraded the current Pyth Core Contract for you |
Early upgrade
This is the recommended path: it moves your integration fully onto the upgraded endpoint and contracts.
Move your Hermes calls to the new Hermes endpoint
Switch your Hermes base URL from hermes.pyth.network to pyth.dourolabs.app/hermes and add your API key that you got in Step 1. The routes and response shapes are unchanged. The upgraded endpoint is a drop-in replacement.
curl -H "Authorization: Bearer $PYTH_API_KEY" \
"https://pyth.dourolabs.app/hermes/v2/updates/price/latest?ids[]=0xe62df6c8b4a85fe1a67db44dc12de5db330f7ac66b72dc658afedf0f4a415b43"Routes and response shapes are unchanged. The upgraded endpoint is a drop-in replacement. See the new Hermes API reference for the full surface.
Per-chain availability: see the Pro-compatible column on the EVM, Solana, and Sui push-feed tables to confirm which feeds are already served by the upgraded Hermes today.
Swap your contract address
Swap your existing Pyth contract address for the upgraded Pyth Core Contract on your chain. The upgraded Pyth Core Contract preserves the Pyth Core interface. No other code changes are needed.
View all upgraded Pyth Core Contract addresses.
After the swap, your integration is fully on the upgraded stack.
Per-chain guides
Waiting for the Automatic Upgrade
Not applicable to Sui
This path does not apply on Sui. Apps reference the Pyth package by object ID, and the DAO cannot swap that for you. Follow the Sui upgrade guide instead.
The automatic upgrade ran at the cutover on August 26, 2026 at 16:00 UTC: the Pyth DAO upgraded on-chain contracts in place, and hermes.pyth.network began serving the upgraded payload with API key authentication required.
If your integration was on this path, the only thing left to check is authentication: a client still calling hermes.pyth.network without an API key fails with authentication errors. Add the Authorization: Bearer $PYTH_API_KEY header using the key from Step 1 and you're done — no contract change is needed, since your contract was upgraded in place.
Chain support
Pyth Core is supported on major EVM chains, Solana and Sui. See the upgraded Pyth Core contract addresses page for more details.
Feed support
Nearly all current Pyth Core feeds remain available after the upgrade, with new ones added. Look up your specific feeds on the feed explorer. If a feed you depend on isn't listed, contact the team.