Implement a rank-based fee discount system for data consumers staking Pyth tokens ($PYTH)

ABSTRACT

The current Oracle Integrity Staking (OIS) system focuses on incentivizing data publishers and other stakers (delegators) to hold and stake $PYTH. However, this system does not directly apply or appeal to another key stakeholder group—data consumers (users of Pyth price feeds).

I am therefore proposing an additional staking program that incentivizes data consumers to hold and stake $PYTH, by offering them discounts on price update fees (when new fee structures are implemented in future). The purpose of this is to give $PYTH added utility, and therefore be an additional driver of $PYTH token price, which I believe is a key factor in Pyth’s future growth.

RATIONALE

First, why is the price of $PYTH important?

Currently, data publishers are rewarded for providing reliable, high-quality data to the network. The primary benefit they receive are publisher rewards in the form of $PYTH (via publisher programs such as the OIS). The attractiveness of this incentive is tied to the $PYTH price. One of Pyth’s main distinguishing features is that it offers first-party data from some of the most established and reputable financial institutions. It is imperative that Pyth maintains this key competitive advantage by ensuring that these data publishers are retained and remain incentivized.

A higher token price means increased value of rewards for data publishers, which in turn retains and attracts more top-tier data publishers. This leads to a higher-quality product, which in turn attracts more data consumers, which equates to more potential revenue, and more value pouring into the ecosystem.

The implementation of a rank-based fee discount system for data consumers would increase buying pressure and therefore bolster token price, leading to the reinforcing cycle of value, as described above.

PROPOSED PLAN AND FEASIBILITY

The system would not be implemented immediately, as I believe fees should still be kept to a minimum (as it is now) to encourage continued growth of Pyth’s market share. Therefore, this will only be implemented once there are significant changes to the update fee structure (i.e. when fees are no longer dirt cheap and discounts actually make a difference).

However, at a strategic time, this new system (if approved) may be communicated to data consumers ahead of time, so that they can start to position themselves appropriately (e.g. start accumulating $PYTH).

Here is a more detailed explanation of how the system could work:

Broad Concept:

  1. Data consumers are ranked based on the amount and duration of staked $PYTH.
  2. Fee discounts are awarded dynamically based on these rankings, creating a competitive environment among data consumers to secure the highest possible discount.
  3. Data consumers with longer staking durations and larger amounts of staked $PYTH will rank higher, incentivizing early acquisition and long-term staking.
  4. A dynamic ranking system discourages selling or reducing stake, as it would negatively impact their rank and future fee discounts.

Mechanism and Structure:

  1. The proposed system could be structured under a newly created “Pyth Data Consumer Association” (PDCA), where membership and eligibility to price feed discounts starts with a minimum stake of $PYTH.
  2. Members of the PDCA will receive different fee discounts based on their staking rank within the PDCA.
  3. Both the duration of staking and the total amount of $PYTH staked are considered, which attracts and rewards early adopters.

Mitigating Drawbacks:

  1. To maximize fairness, the system must be designed to protect smaller members of the PDCA, preventing large consumers from monopolizing the system.
  2. The system must be designed such that it remains attractive to new data consumers in the future. In other words, early adopters should not have an overwhelmingly unbalanced advantage in the system that completely disincentivizes new participants from joining the PDCA in future.
  3. To encourage long-term holding and continued demand for $PYTH, this system may also be paired with other forms of token utility, such as revenue sharing for token holders (which would further reduce net operating costs for data consumers who are staking $PYTH).

PROJECTED IMPACT ON THE PYTH ECOSYSTEM

The implementation of this rank-based fee discount system is expected to generate several positive effects for the Pyth ecosystem:

Increased Demand for $PYTH:

  1. Data consumers will accumulate more $PYTH to improve their rank and secure higher fee discounts.
  2. The staking requirements and competitive nature of the rank system create buy pressure, leading to a net positive impact on token price.

Enhanced Data Publisher Incentives:

  1. As the token price increases, data publisher rewards have increased value, attracting and retaining top-quality, first-party data providers.
  2. This further enhances the quality of Pyth’s price feeds and reputation, making it a preferred choice for builders and creating a virtuous cycle of value.

Capture

Strengthened Long-Term Value Proposition:

  1. Data consumers who stake early will be better positioned for higher discounts as network fees increase in the future, promoting a forward-looking mindset that encourages early adoption and long-term participation.
  2. When data consumers are also $PYTH holders, they have a vested interest in the continued success of the Pyth Network and also reap the benefits when token price goes up. In this way, the interests of stakeholders are aligned.

Broader Ecosystem Benefits

  1. Regular Pyth community members and stakers benefit from the increased demand and rising value of $PYTH. This in turn supports community growth and awareness in the wider Web3 community.
  2. If this system is successful, it would contribute to both customer retention and acquisition.
  3. The proposed system supports sustainable growth and value inflows into the ecosystem, while minimizing the risk of unsustainable price bubbles.

IMPLEMENTATION AND NEXT STEPS

  1. Design the Ranking Algorithm. Develop a fair and transparent algorithm that considers both staking duration and the amount of $PYTH staked to determine rank and fee discounts. It should be fair and attractive to all potential data consumers, big and small, current and future.

  2. Obtain DAO approval. Gather feedback from DAO members and the community, refine the proposal and obtain DAO approval.

  3. Establish the PDCA. Create the Pyth Data Consumer Association as a structured entity within the ecosystem, setting the minimum staking requirements for entry.

  4. Keep fees minimal in the near-term. To reiterate the point, price update fees should be kept at a minimum to encourage continued growth and adoption. However, there should be a communication plan which encourages protocols to be forward-thinking and consider the potential future benefits of $PYTH staking when new fee structures are eventually implemented.

  5. Monitor and Adjust. Regularly review the system’s performance, obtaining feedback and adjusting parameters as necessary to ensure fairness, competitive dynamics, and sustainable value generation.

QUESTIONS AND UNCERTAINTIES

The attractiveness of this program (to data consumers) is dependent and proportional to the update fees. Since I expect update fees to remain highly competitive for the near future, the idea of discounts may not sound appealing initially. One possible idea to generate initial momentum and attract data consumers to the PDCA is to offer incentives like premium services, faster speeds, or staking APR.

However, price update fees will inevitably have to go up at some point in order to make Pyth a profitable and sustainable endeavor. Furthermore, incentivization for data publishers must continue even when token emissions cease. When fees go up, customer retention would depend on the extent to which the quality and scope of Pyth’s services surpasses that of its competitors, and the effectiveness of other customer retention initiatives.

This proposed implementation could be a useful piece in addressing some of these uncertainties and helping us realize the bright future we all envision for Pyth.

5 Likes

gm @arguer

First and foremost, thanks a lot for putting a very thorough proposal in the Idea Bank!

I overall agree with your idea of having discounted Pyth update fees for users (applications) that are going further than only leveraging the Pyth Price Feeds.

You put forward the idea of them staking PYTH which would entitle them a discount on fees charged by the Pyth oracle contracts.

While this can make sense, I feel it would require quite some technical and maybe too complex work.

Imagine: An app would stake on Solana and uses the Pyth oracle on Base. It would require some crosschain matching of their SPL wallet to the one doing price updates on Base. And this every time they do a price update ; for some apps it could be thousands of times per day. Here I feel it might be too much overhead.

A somewhat similar outcome but different idea/implementation is to have reduced fees charged to the user if he pays the oracle fees in PYTH token (rather than the chain native gas token).

This path would also introduce some complexities as the PYTH token is not available on all the chains the Pyth oracle is deployed on.

Another one would be more on how applications integrate the Pyth oracle. Some apps are the one triggering and doing the price updates (and thus paying the fees) onchain but some delegate this action to their end users (mostly true for perpetual protocols using Pyth). In this later design, it would require that the user himself (not the app) holds PYTH which somewhat defeats the purpose again.

Anyhoo I think it is great to get this conversation going and once again want to thank you for all the time you put in this.

4 Likes

@KemarTiti, thanks for taking the time to read and respond to my idea, and making me think more about the technical feasibility. If we’re still interested in exploring this further, I have an idea that could make implementation easier, while still achieving the overarching intent of my proposal.

Instead of providing real-time fee discounts for each price update (which, as you mentioned, requires repeated cross-chain matching and additional processes to pull staking rank data and apply discounts), we could implement a periodic fee rebate system.

Here’s how it could work:

  1. The big idea is that the user is refunded a percentage of the fees they paid, but only at the end of a pre-set timeframe (e.g. weekly or monthly). The percentage received will be based on a snapshot of the user’s rank in the ranking system.

  2. First, the data consumer (e.g. an app) registers their SPL wallet where their $PYTH is staked, by signing a message to prove wallet ownership, then “binds” it to their other addresses (EVM or others) that their app uses to pay for price update fees, and does any other verification required to prove that they are a legitimate data consumer. Completion of this step gives them entry into the ranking system / PDCA.

  3. The ranking system can be managed onchain on the Solana network, where $PYTH staking takes place. As previously explained, the ranking algorithm should account for both amount and duration of staked $PYTH. Since the system would now involve periodic snapshots, there should be mechanisms to prevent people from gaming it.

  4. After the snapshot happens (each week or month), a percentage of the fees paid by the user is refunded to the address from which the fees were paid. The percentage depends on the user’s rank at the snapshot.

This would still effectively be a fee discount system, just executed in a slightly different way.

2 Likes

A thorough and extremely interesting idea. Will come back with some more concrete thoughts, but also wanted to take the time to thank you for putting in the time on this. Glad to see Pythians continue leading the way :crystal_ball:

2 Likes

a very solid proposal!

i do agree with @KemarTiti on the complexity of connecting staked Pyth in Solana and fees on 80+ blockchains but you came up with a solution for it already!

it seems like weekly can be done same with every epoch, with warmup and cooldown already in place, i think “gaming” it is already accounted for

i’ll have to digest most of the proposal but just sharing what came to mind after reading!

1 Like