Abstract
This Operational PIP proposes to:
-
Migrate all Pyth Core (Pythnet) users to Pyth Pro (Lazer), prioritizing the Pyth Network around a single, unified price feed product
-
Grant the Pythian Council authority to execute the migration plan, including contract upgrades required for the cutover
-
Authorize Douro Labs (as administrator of Pyth Pro) to develop and maintain the compatibility layer
A follow-up Constitutional PIP will be submitted upon Pythnet sunset (Q3 2026) to update the Pyth DAO Constitution accordingly (removing Pythnet and PGAS terminology).
Rationale
The Pyth DAO currently maintains two price feed systems:
-
Pyth Core — The original pull oracle, used by hundreds of DeFi protocols across 100+ blockchains
-
Pyth Pro — The current commercialized product, offering higher frequency data (50ms to real-time) with a sustainable revenue model
Prioritizing Pyth Pro delivers three benefits:
-
Revenue opportunity — Pyth Pro generates ~$65K/month for the DAO vs Core’s ~$9K/month. Hypothetically, converting even 25% of ~300 Core users to Pro subscriptions could yield ~$2.7M annual DAO revenue.
-
Cost savings — Maintaining Pythnet and the dual-system architecture costs ~$1M+ annually. Eliminating this overhead improves DAO sustainability
-
Superior product for users — Pyth Pro offers faster updates (50ms–1ms vs ~1s), broader asset coverage (equities, FX, commodities), and unified price feeds across market sessions. The full reasoning is detailed in the forum discussion (https://forum.pyth.network/t/pyth-core-pro-migration-consolidating-pyths-price-feed-products/2398).
Key Terms
| Term | Definition |
|---|---|
| Pyth Core | The existing pull oracle system powered by Pythnet |
| Pyth Pro | The commercialized price feed product (also known as Lazer) administered by Douro Labs |
| Compatibility Layer | API wrapper providing Pyth Core interfaces on Pyth Pro infrastructure |
| Contract Cutover | Upgrade of existing Pyth Core contracts to redirect requests to Pyth Pro |
Implementation Plan
The migration will be executed by Douro Labs (as operator of Pyth Pro) and the Pythian Council, subject to DAO approval.
| Phase | Timing | Action |
|---|---|---|
| 1 | Days 1–7 | On-chain vote on this OP-PIP |
| 2 | April 1, 2026 (may extend to May 1) | Douro Labs delivers compatibility layer (same APIs as Pyth Core) |
| 3 | April – July 2026 (may extend to August 1) | User migration period; users update contract addresses and off-chain URLs |
| 4 | July 1, 2026 (may extend to August 1) | Pythian Council upgrades Core contracts to redirect to Pro |
| 5 | Q3 2026 (may extend to Q4) | Pythnet sunset; Constitutional PIP submitted for cleanup |
Timeline Flexibility
Each phase may be extended by up to one month if required to ensure a smooth migration. Total potential extension: up to one additional quarter.
The Pythian Council will communicate any timeline adjustments via the forum. Extensions do not require additional DAO votes provided they remain within these bounds.
Chain Support
Chains with alternative VMs are not included (for now) in this migration. Users on these chains may continue accessing Pyth prices via websocket subscriptions, but on-chain verification will not be supported until a separate deployment agreement is reached (and technical work performed).
| Chain Type | On-chain Pro API | On-chain Core API | Websocket |
|---|---|---|---|
| All EVM chains |  |
|
|
| All SVM chains | |
|
|
| Sui | |
|
|
| Aptos | — | — | |
| NEAR | — | — | |
| Starknet | — | — | |
| Fuel | — | — | |
| TON | — | — | |
| Movement | — | — | |
| CosmWasm chains | — | — | |
Proposal: OP-PIP-100: Pyth Core to Pyth Pro Migration | Pyth Governance