# Proposal: Introduce PYTH as an Optional Payment Token for Pyth Network Services

**URL:** <https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681>\
**Category:** Ideas Bank\
**Created:** [August 30, 2026, 3:18pm UTC](https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681 "2026-08-30T15:18:22Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dauler](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@Dauler](https://forum.pyth.network/u/Dauler)\
**Post date:** [August 30, 2026, 3:18pm UTC](https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681/1 "2026-08-30T15:18:22Z")

</div>

I propose that the Pyth DAO introduce PYTH as an optional payment token for Pyth Network services, allowing applications and protocols to pay a portion of their fees using PYTH.

The goal is to create a stronger connection between the growth and utilization of the Pyth Network and demand for its native token.

Motivation

Currently, PYTH plays important roles in governance and Oracle Integrity Staking. However, users and protocols consuming Pyth data generally do not need to acquire PYTH to use the network.

This can create a potential disconnect:

More Pyth Network usage → more network revenue, but not necessarily more demand for PYTH.

Allowing PYTH to be used directly for payments could help reduce this gap and create additional economic utility for the token.

Proposed Mechanism

The DAO could establish a system where:

Protocols and applications can choose to pay a portion of their Pyth fees in PYTH;

Payments made in PYTH could receive a small incentive or discount compared with existing payment methods, if considered economically sustainable;

A portion of the PYTH collected could potentially be directed toward a burn or permanent removal from circulation, subject to DAO approval;

The percentages, limits, and incentives could be adjusted over time based on the results of the mechanism.

As an initial experiment, the DAO could allow 10–20% of eligible fees to be paid in PYTH and review the results after a defined trial period.

Expected Benefits

Creates additional direct utility for PYTH;

Can generate organic demand for the token;

Creates a stronger connection between Pyth Network usage and PYTH economics;

Could reduce circulating supply if a portion of collected PYTH is permanently removed;

Potentially strengthens the long-term economic model of the Pyth ecosystem;

Allows PYTH utility to be tested without replacing existing payment methods.

This proposal does not seek to make PYTH mandatory or replace existing payment methods. Instead, PYTH would simply become an additional payment option, allowing protocols and applications to determine whether it provides economic value for them.

Governance Question

I would like to ask the Pyth DAO community to discuss whether PYTH should become an official optional payment token for Pyth Network services.

If the community considers the idea viable, the DAO could then evaluate:

What percentage of fees could be paid in PYTH;

Whether an incentive or discount should be offered;

How collected PYTH should be handled — for example, treasury allocation, buybacks, burning, or another mechanism approved by governance;

What trial period and metrics should be used to evaluate the mechanism.

The core idea is simple:

If Pyth Network usage continues to grow, PYTH should have a stronger role in capturing the economic value generated by that growth.

---

<div class="post-metadata">

**Author:** ![Joy](https://avatars.discourse-cdn.com/v4/letter/j/b77776/32.png) [@Joy](https://forum.pyth.network/u/Joy)\
**Post date:** [August 31, 2026, 9:43am UTC](https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681/2 "2026-08-31T09:43:15Z")

</div>

I fully agree that we need to increase token utility as a way to raise the value of Pyth.

---

<div class="post-metadata">

**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 31, 2026, 10:20am UTC](https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681/3 "2026-08-31T10:20:14Z")

</div>

Hey,

Thanks a lot for the post @Dauler

IMO there are 2 levels to your points:

1. Douro paying the Pyth DAO w/PYTH tokens ; every month, Douro Labs pays 60% back of the revenue it generated selling Pyth Pro to the DAO. This can be done both in stablecoins as well as PYTH tokens (or a mix of the 2). And actually the past few months, Douro had elected to pay the monthly Pyth Pro w/ PYTH tokens instead of stablecoins
2. Purchasing Pyth data subscription (on [pyth.com](http://pyth.com)) is already possible w/ crypto ; the collected amount is then part of the point 1 above at the end of the month when Douro does the distribution to the DAO

And in both cases, PYTH tokens have been accepted therefore I believe your idea is already in effect.

More generally about the idea that more revenue would be generated if the own token was accepted is IMO not so true (and this for all other protocols accepting their own tokens) – or at least the little extra sale generated would not overcome the discount provided to entice apps/companies paying natively in PYTH. I see it as a nice to have but this is not life changing.

And please note that there’s a monthly recurrent PYTH purchase plan with the DAO treasury - See the Pyth Reserve section on the forum

---

<div class="post-metadata">

**Author:** ![Dauler](https://avatars.discourse-cdn.com/v4/letter/d/5f8ce5/32.png) [@Dauler](https://forum.pyth.network/u/Dauler)\
**Post date:** [August 31, 2026, 11:22am UTC](https://forum.pyth.network/t/proposal-introduce-pyth-as-an-optional-payment-token-for-pyth-network-services/2681/4 "2026-08-31T11:22:13Z")

</div>

Thank you for the explanation regarding PYTH payments and the Treasury buyback program.  
Based on that, I would like to propose a different idea to increase the structural utility of PYTH within the Pyth Network.  
PYTH as Economic Collateral for Publishers  
The Pyth DAO could explore a mechanism where certain data publishers, especially those providing highly relevant feeds or carrying greater economic responsibility, would be required to hold a certain amount of PYTH staked as collateral.  
The goal would be to create a direct relationship between participation in Pyth’s infrastructure and demand for the PYTH token.  
How it could work  
Eligible publishers would maintain a minimum amount of PYTH staked.  
The requirement could vary depending on the importance, volume, or economic value of the feeds provided.  
Publishers with greater participation or higher performance/quality could receive additional benefits.  
In cases of proven malicious behavior or violations of network rules, a portion of the collateral could be subject to penalties, according to rules approved by the DAO.  
The requirements could be adjusted through governance as the network grows.  
I am not proposing that this mechanism become mandatory for all publishers immediately. It could start as an experimental program for selected feeds or new publishers and then be evaluated by the DAO.  
Question for the Community  
Should the Pyth DAO explore whether PYTH could take on a larger role as economic collateral within the network’s infrastructure?  
I believe this approach is interesting because it does not depend on discounts or simply making PYTH an accepted payment method.  
The idea is to make the growth of Pyth’s own infrastructure create additional economic reasons to hold and use PYTH.
