Dear Pyth fam,
Late response here.
1. On Adjusting Pyth Core Fees Across Chains
I strongly believe we must be cautious when setting the per-call price for Pyth Core across different chains. Unlike many competitors, Pyth supports a large number of small to medium-sized dApps. Many of these projects are barely breaking even or are still in early growth phases.
If fees rise too aggressively — especially if changes occur quarterly — this could introduce significant uncertainty for them. Such volatility in operating costs may push some builders to consider alternative oracle solutions purely for predictability.
I understand the need for revenue optimization, but I think pricing needs to be balanced with ecosystem health.
Recently I saw Pyth added push-oracle support to several chains. If the intention is to expand push-oracle coverage, that might help reduce costs for certain integrators — but more clarity on rollout strategy would be helpful.
2. On Buybacks
I support the idea from @arguer of adjusting the scale of buybacks based on actual revenue flowing into the DAO. A flexible model feels more aligned with sustainability. If the DAO earns more, we can buy back more; if revenue slows, buybacks should naturally scale down. Or if the price movement is under negative under certain market index, we buy more.
This preserves treasury health while still accumulating PYTH over time.
3. On PYTH Token Utility & Community-Driven Use Cases
I recently discussed this with a few ecosystem members, and one recurring theme is that we need more use cases and traction for the $PYTH token beyond staking and governance.
I understand that $PYTH token utility in the web3 ecosystem maybe outside Douro Lab’s core focus — but that doesn’t mean the community can’t build around it.
Something like:
-
small games (e.g. fogofishing on FOGO, but using PYTH under the hood)
-
$ORE-style experiences or simple on-chain gambling games
-
playful experiments that get people interacting with the token
The goal isn’t to turn $PYTH into a gaming token, but to create demand, attention, and positive sentiment around the ecosystem. Even small fun projects can have a meaningful impact on community engagement.
Perhaps the DAO could allocate a portion of revenue to fund game developers or community builders who want to experiment with PYTH-based mini-apps.
The current downtrend of the token — in what is supposedly a bullish market — signals that we may need to rethink how PYTH fits into the broader crypto culture and narrative.
Closing Thoughts
I support many aspects of the proposal, but I believe:
-
fee adjustments must be approached gradually and thoughtfully
-
buybacks should scale with revenue
-
PYTH token utility needs new energy, creativity, and community experimentation
Thank you to everyone working hard to move the pyth ecosystem forward.