Implement Fees on Pyth Core Across Networks #2

Background

In February 2025, the Pyth community and DAO approved an increase in oracle fees on a subset of chains where Pyth is deployed.

Shortly after, the community proposed a broader pricing model: charging roughly $0.10 per price feed update across most supported chains. While this sparked discussion, feedback from many users raised concerns related to the current macro conditions.

Based on that feedback, I believe a gradual implementation of oracle fees is the better path to continue enabling adoption and enable applications to adjust over time. Still, sustainable economics are important, and the Pyth DAO/community should revisit a more comprehensive pricing as Pyth matures and usage patterns become clearer.

For now, this post focuses on the next incremental step: introducing moderate, targeted fees on additional EVM chains. The goal is to begin generating revenue for the DAO in a way that supports growth.

For reference, you can view the currently active Pyth Core fees here.

Proposal Overview

Building on the success of the opBNB experiment and the recent DAO vote to introduce fees on 8 blockchains, I propose continuing this approach across Pyth’s EVM deployments. The rollout should be gradual and guided by data—designed to avoid disrupting builders or adoption momentum.

Why Introduce Fees?

Introducing modest fees helps strengthen the network’s long-term economics by:

1. Attracting more publishers, increasing competition and data quality
2. Improving service quality for apps and developers using Pyth

Note: While fees generate revenue, the DAO has not yet approved any mechanism for distributing these funds.

Implementation Strategy

Fee Structure Considerations

Fees will be based on three core principles:

• Per-feed model: Fees apply to each individual price feed
• Per-update charges: Each feed update incurs a fee
• Proportionality: Fees should stay reasonable relative to overall transaction costs

Proposed Fee Structure

The table below is a recap of all suggested change (or not) for all EVM chains reviewed. If you want to review the process behind such numbers, please refer to the subsequent post below.

Next Steps

This proposal focuses exclusively on fee implementation strategy. The allocation and usage of generated fees will require separate discussion and governance decisions.

Community Feedback

We welcome input from all stakeholders:

• Publishers
• Oracle users
• Committed Pythians

Your insights will be valuable in refining this proposal and guiding the DAO’s decision-making process.