# Q3 2026 — Pyth Core Onchain Fees: Final Review **URL:** \ **Category:** Ideas Bank\ **Created:** [July 13, 2026, 12:29pm UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638 "2026-07-13T12:29:32Z")\ **Posts on this page:** 7\ **Page:** 1
**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\ **Post date:** [July 13, 2026, 12:29pm UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/1 "2026-07-13T12:29:32Z")
### Summary **Proposal: No fee changes for Q3 2026.** With Pyth Core sunsetting at the end of this month per [OP-PIP-100](https://forum.pyth.network/t/op-pip-100), the Pythian Council recommends skipping the usual fee adjustment cycle. The engineering effort, governance overhead, and implementation time aren’t justified for a product with weeks left. That said, we’re posing an open question to the community before finalizing. ### Revenue Performance The fee implementation has been working. Monthly protocol revenue across all EVM chains: ```auto | Month | Revenue | | -------- | ------- | | Jan 2026 | $1,765 | | Feb 2026 | $8,140 | | Mar 2026 | $20,756 | | Apr 2026 | $19,534 | | May 2026 | $37,672 | | Jun 2026 | $27,340 | ``` **Total H1 2026: ~$115K.** Up from near-zero before fee implementation. The Q2 fee adjustments (moving toward $0.015/update target) contributed to the May/June jump. Revenue normalized in June as some high-activity chains migrated to Pro. ### Current State Q2 fees are live across 70+ EVM chains. Since implementation: - **Most chains:** Still within target range ($0.009-0.015/update) - **Some drift:** Token volatility pushed a few chains above or below target - **One outlier:** Monad fees now yield ~$0.0002/update and the token volatility pushed it well below target A proper recalibration would require updating fee contracts across dozens of chains, significant engineering and council time for marginal benefit. ### Why Skip Q3 Adjustments 1. **Sunset timeline:** Core deprecates end of July. Migration to Pro is already underway. 1. **Resource cost:** Contract upgrades, Wormhole governance execution, council implementation — all for ~3 weeks of relevance. 1. **Migration focus:** Douro Labs and integrators are focused on Pro onboarding, not Core maintenance. ### **Open Question** **Should we 2x (or else) fees instead?** Rather than fine-tuning fees, what if we **doubled/tripled/etc all Core fees** as a migration accelerant? I personally lean toward no changes as the sunset timeline does the work for us. But if the community feels strongly that a fee increase would meaningfully accelerate migration, I am open to it. ---
**Author:** ![Frozenmind](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/frozenmind/32/858_2.png) [@Frozenmind](https://forum.pyth.network/u/Frozenmind)\ **Post date:** [July 13, 2026, 2:24pm UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/2 "2026-07-13T14:24:10Z")
IMO I think that we should significantly increase the fees on Pyth Core to accelerate migration. Some projects might have missed the news about the sunset but a sudden and substantial increase in fee will not be missed/disregarded. I would go as far as 3x increase to really achieve this goal. Now the window is pretty small between now and the sunset so might be too much effort in the end but if we happen to change the timeline for sunset or decide to keep Core for a little longer we should make the increase now. ---
**Author:** ![lowkeigh](https://avatars.discourse-cdn.com/v4/letter/l/ee7513/32.png) [@lowkeigh](https://forum.pyth.network/u/lowkeigh)\ **Post date:** [July 14, 2026, 9:26am UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/3 "2026-07-14T09:26:09Z")
I agree with @Frozenmind suggestion. I think a 2X of fees aligns with our goals here nicely. ---
**Author:** ![Derrp](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/derrp/32/670_2.png) [@Derrp](https://forum.pyth.network/u/Derrp)\ **Post date:** [July 16, 2026, 7:44am UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/4 "2026-07-16T07:44:11Z")
A nice incentive to migrate… I like your thinking. ---
**Author:** ![scp](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/scp/32/627_2.png) [@scp](https://forum.pyth.network/u/scp)\ **Post date:** [July 16, 2026, 8:53am UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/5 "2026-07-16T08:53:37Z")
Dear @KemarTiti , Good post ser. Nice work. I support the idea from @Frozenmind and @lowkeigh It might be a good idea to increase the fee and alert the users of pyth core that something has been changed. SCP ---
**Author:** ![KemarTiti](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/kemartiti/32/5_2.png) [@KemarTiti](https://forum.pyth.network/u/KemarTiti)\ **Post date:** [August 3, 2026, 2:57pm UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/6 "2026-08-03T14:57:27Z")
After further thought, I’d like to propose a different direction: **set all Core fees to 0 (1 wei technically) prior to the August 18th upgrade.** Here’s the rationale: **1. The upgrade changes the fee model** On Aug 18th, these Core contracts will be automatically upgraded to accept data from Pyth Pro as Pythnet sunsets. Pyth Pro’s monetization is off-chain, so charging on-chain fees on top of that would double-dip/add extra costs. **2. Consistency with current architecture** Today’s already-upgraded Core contracts don’t have on-chain fees. Neither do Pro contracts. Keeping fees on the legacy contracts for their final 2 weeks creates an inconsistent experience for integrators. **3. Cleaner migration path** Rather than raising fees as a migration “stick,” removing them entirely simplifies the transition. Integrators migrating to Pro don’t need to adjust their gas budgets mid-flight. **4. Minimal revenue impact** Migration is already well underway. Core revenue in June ($27K) was down from the May peak ($37K) as integrators move to Pro. With around 2 weeks left and declining usage, the operational overhead of a fee change likely outweighs any marginal revenue we’d collect. **Proposal:** Pythian Council applies 0 fees (1 wei) to all Core contracts across all chains before August 18th. ---
**Author:** ![Frozenmind](https://sea1.discourse-cdn.com/flex001/user_avatar/forum.pyth.network/frozenmind/32/858_2.png) [@Frozenmind](https://forum.pyth.network/u/Frozenmind)\ **Post date:** [August 3, 2026, 4:00pm UTC](https://forum.pyth.network/t/q3-2026-pyth-core-onchain-fees-final-review/2638/7 "2026-08-03T16:00:40Z")
Totally makes sense at this point in time. My previous proposal was mostly to cover the situation where Pyth Core sunset would be delayed which appears to not be the case. Lets proceed with this change as soon as possible IMO. 🧠