Summary
This proposal explores the idea of distributing a portion of OIS (Oracle Integrity Staking) rewards in stablecoins (e.g., USDC primarly from the Pyth DAO Reserve) instead of exclusively in PYTH tokens. The goal is to reduce sustained sell pressure on $PYTH, better align incentives with long-term supporters, and make OIS staking more attractive to a broader set of participants while preserving $PYTH’s strategic role in governance and protocol alignment.
This is an idea-stage proposal intended to gather community feedback and assess feasibility (economic, technical, and legal).
Motivation
Currently, OIS rewards are primarily distributed in $PYTH tokens. While this aligns stakers with the protocol, it also:
-
Increases circulating supply through emissions
-
Creates predictable sell pressure from stakers who need liquidity
-
Encourages short-term farming behavior rather than long-term commitment
Core Idea
Introduce an option (or partial mechanism) for OIS staking rewards to be paid in non-PYTH assets, primarily stablecoins such as USDC, sourced from protocol revenue or treasury allocations.
Key principles:
-
PYTH remains the staking asset (no change to OIS security model)
-
Stablecoins are used only for rewards, not governance power
-
Rewards favor long-term, loyal stakers rather than short-term farmers
Revenue Source Considerations
The current primary revenue source for stablecoin rewards is Pyth Pro, Pyth Network’s premium data offering that generates protocol revenue from institutional and professional users.
Using a portion of Pyth Pro revenue for OIS rewards would:
-
Align staker incentives with real protocol usage and adoption
-
Avoid excessive $PYTH emissions and supply inflation
-
Create a clearer link between oracle performance, data demand, and staker rewards
Any allocation from Pyth Pro revenue would remain subject to DAO governance decisions, treasury constraints, and legal review.
Possible Reward Structure (Conceptual)
This is one illustrative model; exact mechanics are open for discussion.
1. Dual-Source Rewards
-
Base rewards: PYTH emissions (unchanged or reduced)
-
Bonus rewards: USDC sourced from:
-
Protocol revenue
-
Treasury-approved allocations
-
2. Loyalty / Duration Boost
-
Longer staking durations via OIS receive higher reward multipliers (eg 1.25x, 1.5x, 2x)
-
Early unstaking forfeits part of the stablecoin bonus
-
Encourages alignment with Pyth’s long-term vision
3. Anti-Farming Design
-
Stablecoin rewards vest or accrue over time
-
Boosts are non-transferable and reset on unstake
-
Emphasis on consistency, not capital size alone
Why Stablecoins?
-
Reduces immediate sell pressure on $PYTH
-
Introduces real yield perception for stakers
-
Attracts participants who prefer predictable returns
-
Separates security alignment ($PYTH staking) from reward extraction
Importantly, this does not eliminate $PYTH rewards entirely, but complements them.
Buybacks vs. Stablecoin Rewards
A common counterargument is that protocol revenue should be used for $PYTH buybacks instead.
This proposal does not oppose buybacks. Instead:
-
Buybacks support price and long-term value
-
Stablecoin rewards support user behavior and retention
A hybrid approach may be viable, depending on revenue scale.
Open Questions for the Community
-
Revenue Source: Which revenue streams (if any) are appropriate for OIS rewards?
-
Allocation: What percentage should go to buybacks vs. staker rewards?
-
Legal / Compliance: Are there jurisdictional constraints around distributing stablecoins?
-
Governance: Should stakers choose between PYTH-only or mixed rewards?
-
Security: Any unintended incentives affecting oracle quality or participation?
Next Steps
-
Gather feedback from stakers, node operators, and governance participants
-
Request input from Pyth Foundation / legal contributors on feasibility
-
Refine into a formal proposal if community interest is strong
This idea aims to strengthen OIS by rewarding loyal participation, reducing reflexive sell pressure, and aligning incentives with Pyth’s long-term sustainability. It is not a finalized design, but a starting point for meaningful discussion.
*Community feedback, critiques, and alternative designs are encouraged.
Special thanks to @arguer , @Amensch for your ideas and contributions.