Pyth Core → Pro Migration: Consolidating Pyth's Price Feed Products

[zenyas]

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?

1. 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.

1. 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.

1. 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

1. 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

1. Community Discussion — Looking to collect end-users’ feedback for timeline/proposal refinement

2. CO-PIP Vote — Formal vote to approve the migration plan and empower the Pythian Council to execute on it

[Derrp]

In terms of future sustainability, this makes a lot of sense. We cannot rely on token unlocks indefinitely to fuel the continuation of the Pyth Network: in all of its categories.

We need to optimise the circular economy of receiving sufficient income from data consumers to:

• Continue to pay current data publishers
• Increase the flexibility to onboard new publishers to increase the diversity and accuracy of data, and new price feeds and markets!
• Continue to support our contributors including Douro Labs (we will require more from them into the future) as we build towards being the price of everything
• Continue to support community and promotional endeavours with incentives to spread the word of Pyth Network

I know there will likely be some pushback with this, but I do see the need for economic sustainability as an inevitable step that we must take. This seems like a logical step to do this, as well as streamline the product offerings and payments.

I support this proposal and look forward to the replies.

[spank2023]

This might be a simple-minded approach, but when you say Pyth Core is “essentially negative,” I’m assuming overhead savings alone when transitioning to single-system feed (Pro) would justify the change? Even if none of the Core users migrated to Pro, it seems infrastructure cost savings would offset the $9k/month lost revenue from no longer having Core. I guess the only downside in that example would be a lower number of overall PYTH users?

All that being said, I agree that pushing for a sustainable revenue model (independent of token unlocks) makes the most sense. This proposal seems like it will help achieve that long-term goal.

[Quintzor]

Unifying the Pyth price feed products into one and trimming some of the overhead is a great strategy moving forward. I think Pyth needs to make that jump forward in the space and push for being THE premium price feed service. While this move will push out some smaller players, I still believe it is the correct move. I imagine some larger partners would like to see a less open product as well…because they can use their subscription to Pyth Pro as an advertising tool, notifying users that they have the most accurate and reliable data coming to them in milliseconds.

While I think smaller projects should have a chance to demo and trial run Pyth Pro, simply giving out these gems at a loss is not beneficial for Pyth in the long term. There are plenty of projects making millions in liquidations and fees, so paying a premium for the data to their userbase is logical.

I support this proposal and understand at least a portion of the pros and cons of both options.

[SkyZ]

My moma said

Strike while the iron is hot.

Pythpro for the win

[N0name_trader]

Very legit proposal in my opinion. When you will just compare the metrics of maintenance vs revenue, you will understand that more… intensive moves should be applied for supplying the business model with enough fuel.
In my perspective Pyth Core was a really nice promo for everyone to understand the quality of the product and eventually, subs is the most logical things here
I guess even trial period is not needed at all
So 100% for it

[Flint]

open infrastructure
enterprise data feed

Consolidating around Pyth Pro makes sense: stronger revenue model, faster data, and simpler architecture. It would also help to clarify the real number of free-tier Core users. The key will be a smooth migration and clear support across all chains.

[Mersault]

The choice is obvious.

There’s zero point in sticking with a Pyth Core that’s bleeding money. Pyth Pro is strictly superior, it’s cost-effective, and the revenue potential is on another level, especially with a marketplace on the horizon.

[lowkeigh]

The choice seems obvious in my opinion.

Now that Pyth Pro is online with a clear PMF, there is no need to maintain Pyth Core services especially if they are running at a loss.

I would much rather see the consolidation of resources into other more products such as Pyth Pro and Entropy.

I have no doubts there will be some users who may disagree with this decision and may migrate away, I think the steps outlined above are more than fair will minimise disruptions to users and are well within Pyths best interests to proceed with

[scp]

I think this direction makes sense from both a product and operational perspective.

One benefit of services like Pyth Pro is pricing predictability. Since subscriptions are USD-denominated, the cost is more stable compared to pricing models based on crypto-native tokens that may fluctuate in value.

In addition, focusing more on off-chain data distribution could reduce operational overhead compared to maintaining a full on-chain oracle stack with a large validator set such as Pythnet with Pyth Core.

From a sustainability perspective, subscription-based services can provide more predictable and recurring revenue, while simplifying the architecture help lower infrastructure and operational costs. This combination of recurring revenue and reduced operating costs could strengthen the long-term economics of the network.

Overall, consolidating the price feed products under a clearer structure seems like a sensible step.

Just 1 question @zenyas as you said “All existing Pyth Core contracts upgraded to redirect to Pyth Pro. Any users who didn’t migrate are automatically migrated.“ However, Pyth Pro user requires an API key. What will happen to those migrated automatically but without a proper API key to access the pricefeed?

From SCP with Love

[Blaq]

Merging the price feeds makes sense, I strongly support this move.

buh the only downside I see to this is, Pyth core user might refuse in terms of the fees structure buh it stated everyone be migrated automatically.

Good one though

[CrownOfLagos]

I love your momma Send my regards

[CrownOfLagos]

Pyth Pro is greater even in terms of the fees,
I strongly agree to unifying both Products.
Pyth core users might not have issues with it when the two products are merge.

Great idea Bless