Summary
Phase 2 (https://forum.pyth.network/t/passed-op-pip-87-pyth-token-phase-2-pyth-strategic-reserve/2293) established the PYTH Strategic Reserve, funded by protocol revenues, to purchase PYTH on the open market. However, monthly OIS (Oracle Integrity Staking) emissions (~7M PYTH per month) still exceed these monthly purchases (~2–3M PYTH), creating net sell pressure.
This proposal introduces Phase 3: allow OIS rewards to sunset naturally when the current reward pool depletes in early March 2026 (estimated March 5th). No new allocation would be made to OIS, but we urge the DAO to consider retaining economic incentives for publishers, including a requirement to stake as a condition to providing data.
Please note that governance staking would remain unchanged — PYTH holders can continue staking for voting as they always have.
With OIS emissions ending and protocol revenues growing, the network moves toward sustainable tokenomics where purchases made by the DAO exceed emissions.
| Metric | Current (until Feb 2026) | Post-Phase 3 (Q2 2026+) |
|---|---|---|
| Monthly OIS emissions | ~7M PYTH | 0 PYTH |
| Monthly PYTH purchases | ~2–3M PYTH | ~5–15M PYTH (growing) |
| Net monthly flow (OIS vs purchases) | OIS exceeds purchases by ~4–5M | Purchases exceed OIS |
Note: Post-Phase 3 purchases based on projected DAO net proceeds ramping from ~$250K (Q2 2026) to ~$758K (Q4 2026), translating to ~5M–15M PYTH/month at current prices.
Background
- Phase 2 Recap
OP-PIP-87 (https://forum.pyth.network/t/passed-op-pip-87-pyth-token-phase-2-pyth-strategic-reserve/2293) (passed in December 2025) directed the Pyth DAO to:
-
Allocate 1/3 of Treasury monthly to purchase PYTH on the open market
-
Accumulate purchased tokens in the Strategic Reserve (https://forum.pyth.network/c/pyth-reserves/12)
-
Task the Pythian Council with optimizing on-chain pricing for Pyth Core, Entropy and Express Relay
The mechanism is now operational. Recent purchases:
- Current Revenue Sources
- Pyth Pro (Off-chain Subscriptions)
Per CO-PIP-9 (https://forum.pyth.network/t/passed-co-pip-9-proposal-to-assign-douro-labs-as-administrator-and-initial-distributor-for-subscriptions-to-pyth-data-off-chain/2220), Douro Labs distributes 60% of Pyth Pro revenue to the DAO.
| Period | Total Revenue | DAO Share (60%) |
|---|---|---|
| Sep–Dec 2025 | $262,222 | $157,333 |
| December 2025 | $90,408 | $54,245 |
| January 2026 | $122,833 | $73,700 |
| Total | $475,463 | $285,278 |
- Price Feed Listings
One-time payments for new price feed listings via the Price Feed Council (https://forum.pyth.network/c/price-feed-council/6) have generated over $300,000 since 2025. Example: HAEDAL/USD (https://forum.pyth.network/t/price-feed-request-haedal-protocol-haedal/2120/4) was listed for a $20,000 payment.
- On-Chain Protocol Fees
Fee collection is now being activated across products:
| Product | Status | Proposal |
|---|---|---|
| Express Relay | Live (Feb 9, 2026) | OP-PIP-92 |
| Core (Price Feeds) | Pending | OP-PIP-93 (this week) |
| Entropy | Pending | OP-PIP-94 (this week) |
Prior to fee activation, contracts accumulated ~$100K (Core), ~$150K (Entropy), and ~$110K (Express Relay) as documented in the Phase 2 discussion (https://forum.pyth.network/t/pyth-token-phase-2/2284).
- OIS (Oracle Integrity Staking)
Oracle Integrity Staking (https://forum.pyth.network/t/passed-co-pip-4-upgrade-staking-program-in-mainnet-to-add-staking-for-data-integrity/1743) was launched in late 2024 following the Community Integrity Pool (CIP) design (https://forum.pyth.network/t/community-proposal-for-the-design-of-the-community-integrity-pool-cip/1571) proposed by CMS and the community. The program enables PYTH stakers to delegate to data publishers, with slashing mechanisms to penalize poor data quality.
The Pyth Data Association funded the initial reward pool to bootstrap the program’s practical implementation. Current spending: ~1.8M PYTH/week (~7M PYTH/month).
The reward allocation is nearly exhausted. The program will naturally conclude in early March 2026 absent re-funding.
Proposal
→ Do Not Renew OIS
When the current OIS reward allocation depletes (projected early March 2026), do not allocate additional tokens to this program. This is a Pythian Council operational action that:
-
Ceases new reward emissions once current funding is exhausted
-
Allows existing stakers to withdraw at their convenience
-
Preserves staking infrastructure for governance voting
-
Does not affect publisher operations or data quality
Rationale
OIS has never been triggered. Since launch, not a single slashing event has occurred. The DAO has distributed close to 100,000,000 PYTH in staking rewards to publishers and non-publisher DAO members without the slashing mechanism ever being invoked. While this may indicate high publisher quality, it raises the question of whether the current implementation of OIS is the optimal use of DAO resources.
Pyth’s primary security is structural. The network’s data integrity derives from:
-
100+ first-party data publishers (exchanges, market makers, trading firms)
-
Aggregation algorithms that filter outlier prices
-
Confidence intervals that communicate price uncertainty
-
On-chain verification of cryptographic signatures
Ending OIS as originally designed enables sustainable token economics.
Current OIS emissions of ~7M PYTH/month exceed the ~2–3M PYTH in monthly purchases. Eliminating OIS emissions to all stakers (publishers and non-publishers) while growing protocol revenues—projected to ramp from ~$250K/month (March 2026) to ~$758K/month (December 2026)—allows purchases to exceed this emission source.
Implementation
No contract upgrades required. The Pythian Council has the constitutional authority to manage OIS pool capacity and reward rates.
Action: If this idea receives community support and passes as a CO-PIP, the Pythian Council will pass an OP-PIP to set the OIS reward rate to 0 before the current funding depletes (target: before March 5, 2026).
Staker Impact: Existing stakers can withdraw tokens at their convenience. No lockup changes. Governance staking functionality remains available.
Future Considerations
I would suggest to keep the following points out of scope for this proposal but definitely merit future community discussion:
-
Mandatory Publisher Staking — Requiring data publishers to stake PYTH (subject to some slashing risk) as a condition to providing data could create stronger alignment between data quality and economic incentive.
-
Unlock Schedule Adjustments — The current vesting schedule includes significant unlock events (May 2026/2027). Modifications could further support sustainable token economics. These are substantial changes warranting dedicated analysis and separate proposals.
Discussion Points
-
Staking behavior: Do community members anticipate that sunsetting OIS rewards will lead to significant unstaking, or will stakers remain for governance participation?
-
Publisher participation: Are there concerns about publisher engagement without OIS delegation incentives?