Summary
We propose migrating all Pyth Core (Pythnet) users to Pyth Pro (Lazer) and consolidating the Pyth Network around a single, unified price feed product.
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
This proposal outlines a structured migration plan that ensures uninterrupted service for existing users while unlocking significant revenue opportunity for the DAO.
Why Now?
- Revenue Reality
Pyth Pro has proven dramatically more profitable than Pyth Core:
| Metric | Pyth Core | Pyth Pro |
|---|---|---|
| Revenue Model | Update fees | Subscription ($5K-$10K+/month) |
| Monthly Revenue | $9,000 | ~$108,000 |
| Annual Revenue | $108,000 | ~$1,300,000 |
| DAO Share (Annual) | $108,000 | ~$780,000 |
Core fees were increased via OP-PIP-93 in early 2026. February 2026 revenue across all Core contracts accumulated approximately $9,000.
At current rates, Pyth Core generates $9K/month while Pyth Pro generates ~$65K/month for the DAO — a 7x difference today, with Pro still scaling faster.
- Cost Savings
Maintaining Pythnet and the dual-system architecture costs approximately $1M+ annually (~$83K/month) in engineering time and operational resources. This includes:
-
Pythnet validator infrastructure
-
Dual codebase maintenance
-
Support for two different integration paths
-
Ongoing security reviews for both systems
Net impact: Pyth Core is essentially negative when factoring in its share of infrastructure costs.
- User Opportunity
There are approximately 300 active Pyth Core users (per DefiLlama). Converting even a fraction to Pyth Pro subscriptions represents meaningful revenue opportunity:
Conservative Scenario: 25% Conversion at Crypto+ Tier ($5K/mo)
| Timeframe | Gross Revenue | DAO Share (60%) |
|---|---|---|
| Monthly | $375,000 | $225,000 |
| Annual | $4,500,000 | $2,700,000 |
Comparison to Today:
| Metric | Current (Core) | Post-Migration (25% conversion) |
|---|---|---|
| Monthly DAO Revenue | $9,000 | $225,000 |
| Annual DAO Revenue | $108,000 | $2,700,000 |
| Increase | — | 25x |
- Better Product
Pyth Pro offers strictly superior capabilities:
-
Faster updates — 50ms to 1ms vs. Core’s ~1 second
-
More symbols — Equities, FX, commodities beyond just crypto
-
Better infrastructure — Purpose-built for performance
-
Same reliability — Battle-tested with institutional users
-
Unified price feed — no more segmented price feeds based upon market sessions
Migration Plan
Phase 1: Develop Compatibility Layer
Target: April 1
Build a compatibility layer for Pyth Pro that provides the exact same APIs as Pyth Core (new URL/addresses, same interface/ABI).
Phase 2: User Migration
Target: April 1 – July 1 (3 months)
Users migrate by updating contract address and pointing off-chain services to new URL. Simple config changes for most.
Phase 3: Contract Cutover
Target: July 1
All existing Pyth Core contracts upgraded to redirect to Pyth Pro. Any users who didn’t migrate are automatically migrated.
Summary
| Date | Milestone |
|---|---|
| March 2026 | Proposal discussion & approval |
| April 1 | Compatibility layer ready |
| April 1 – July 1 | User migration period |
| July 1 | Contract cutover complete |
| Q3 2026 | Pythnet sunset |
Chain Support
EVM & SVM Chains
Pyth Pro supports all EVM and SVM chains. Contract deployment is handled on-demand — when users subscribe to Pyth Pro, Douro Labs may deploy contracts to their required chain(s) at no additional cost.
Non-EVM/Non-SVM Chains
Chains with alternative VMs require custom integration work and are not included in this migration:
-
Starknet
-
Fuel
-
TON
-
NEAR
-
Aptos, Movement
-
CosmWasm-based chains (Osmosis, Neutron, Injective, etc.)
Users on these chains may continue using Pyth Core until sunset. Pyth Pro support for these ecosystems requires both a Pro subscription and a separate deployment agreement (grant or commercial deal) to cover custom integration costs.
Next Steps
-
Community Discussion — Looking to collect end-users’ feedback for timeline/proposal refinement
-
CO-PIP Vote — Formal vote to approve the migration plan and empower the Pythian Council to execute on it