Pyth Network has strengthened the link between product adoption and its native token. Under the newly approved “100% Rule,” all eligible revenue and assets received by the Pyth DAO from network products can be used to acquire PYTH for the Pyth Strategic Reserve.
The wording matters. This is not a promise to spend every dollar of gross product sales on buybacks. Commercial revenue-sharing agreements remain in place, and the rule applies to the portion that reaches the DAO. The acquired tokens are held in a DAO-controlled reserve rather than burned or distributed to holders.
The new policy replaces a slower monthly process
The Pyth DAO approved OP-PIP-136 to replace the original reserve mechanism. Previously, the DAO considered converting one-third of its non-PYTH treasury balance each month, with a separate governance action required for recurring purchases. The revised policy provides standing authorization to convert all eligible product receipts into PYTH.
The change removes the fixed one-third ceiling and shortens the gap between revenue collection and reserve purchases. It also broadens the mechanism beyond a single monthly balance snapshot: eligible USDC, SOL and other assets received by the DAO can be transferred to the Pythian Council’s operations multisig for execution under defined controls.
Pyth said the first acquisitions under the revised authorization were completed on September 30, 2026. The reserve already held roughly 42 million PYTH after that purchase cycle, giving the program an existing inventory before the new revenue rule begins to compound.
“All product revenue” means all eligible DAO receipts
Pyth’s official announcement describes the policy as committing every dollar earned by the DAO from Pyth products to buying PYTH. Product businesses can still operate under their existing commercial terms. Where a product sends 60% of revenue to the DAO, for example, that 60% becomes eligible for the reserve; the remaining share does not suddenly become DAO property.
| Step | What happens | What it does not mean |
|---|---|---|
| Product earns revenue | Subscriptions, listings, indices and other services generate fees | Gross sales are not automatically the DAO’s full balance |
| DAO receives its share | Eligible assets arrive under existing revenue-sharing terms | The new vote does not rewrite commercial agreements |
| Reserve buys PYTH | The operations multisig can execute open-market purchases within its mandate | Authorization does not create an instant market order for every receipt |
| PYTH enters the reserve | Purchased tokens remain under DAO control | They are not burned and are not paid out to token holders |
This distinction makes the model easier to assess. The potential buying flow depends on two variables: how much revenue the products generate and how much of that revenue the DAO is contractually entitled to receive.
Pyth’s revenue base is becoming material
Pyth reported annual recurring revenue of $11.5 million in September 2026, up 86% quarter over quarter. Its product suite includes Pyth Pro, Listing as a Service, Pyth Indices, the Data Marketplace and other network services. Pyth Indices alone reached $1.81 million in fixed ARR, according to the network’s September product report.
The DAO’s September revenue report offers a more direct view of the amount available to the reserve. Pyth Pro and related services recorded about $916,471 in gross monthly revenue, with $553,693 allocated to the DAO under existing agreements. That gap between gross revenue and the DAO share is precisely why the “100%” headline should be read carefully.
Revenue growth can now translate into recurring token demand without a new monthly vote. If the business expands, the purchasing budget can expand with it. If revenue stalls or collection is delayed, buyback capacity falls accordingly.
Execution rules limit how the reserve can trade
The authorization is broad, but it is not unrestricted. OP-PIP-136 sets a maximum transaction size of $25,000 and a maximum slippage tolerance of 5%. Execution should generally use aggregators such as Jupiter, while limit orders must be placed at least 0.1% below the displayed market price. Transaction proofs and monthly reports are required.
The reports must disclose assets received, assets converted, PYTH acquired, execution prices, fees, slippage, transaction links and any unconverted balance. The operations multisig cannot sell the accumulated PYTH, borrow against it, use leverage or derivatives, or distribute the reserve without a separate DAO authorization.
Implementation is still being refined. OP-PIP-140, proposed in October, addresses a mistaken USDC transfer and clarifies how future fees should move directly to the operating wallet. That work does not reverse the policy, but it shows that governance approval and reliable operational settlement are separate steps.
Why the change matters for PYTH
A clearer revenue-to-demand channel
The strongest change is structural. Product usage can now create a recurring source of open-market demand for PYTH. The mechanism is measurable because the DAO can publish receipts, purchase amounts and average execution prices.
A growing strategic reserve
The DAO accumulates an asset it governs instead of leaving all product income in stablecoins or SOL. A larger reserve can align the treasury more closely with long-term network performance, although it also increases concentration in PYTH and reduces diversification.
No automatic reduction in token supply
Reserve purchases move tokens from the market into a controlled wallet, but they do not destroy them. PYTH’s maximum supply remains 10 billion, and the published allocation schedule still includes unlocks for previously locked tokens. Buybacks can absorb some market supply without cancelling dilution risk.
The policy is supportive, but it does not create a price floor
Recurring purchases can improve the demand side of the market, especially if revenue grows while available liquidity remains limited. They can also become predictable enough for traders to anticipate, which may reduce the surprise once execution begins.
The main counterweights are token unlocks, broader market conditions, execution timing and product-revenue volatility. A large unlock can exceed the amount bought by the reserve. Likewise, a falling token price allows the same dollar budget to buy more PYTH, while a rising price reduces the number of tokens accumulated. The policy creates a feedback channel, not a guaranteed valuation.
PYTH rallies as the market reassesses the revenue link
The KTX PYTHUSDT perpetual market quoted PYTH near 0.08365 USDT on October 9, up 10.41% over 24 hours. The session traded between 0.07297 and 0.08637 USDT, while reported 24-hour turnover reached 236.11 million USDT. The weekly chart shows a sharp recovery from the mid-2026 lows, although PYTH remains below the peaks visible in late 2025.
Funding was slightly negative at the time of the snapshot, even as price rose. That combination can indicate that perpetual positioning had not become uniformly long, but a single funding reading is temporary and cannot establish the cause of the rally. Revenue-policy headlines, broader altcoin flows and short covering can all affect price at the same time.
Traders can monitor the KTX PYTHUSDT perpetual market for live prices, order-book depth and funding. Because leverage magnifies both gains and losses, liquidation risk should be managed against mark price and available margin rather than the latest traded price alone.
What to watch next
- Monthly DAO receipts: revenue reported by the business is less useful than the amount actually transferred to the DAO.
- PYTH purchased: compare the token quantity, dollar spend and average execution price.
- Reserve balance: confirm that purchased tokens remain in the disclosed wallets and are not sold.
- Product growth: ARR, paying customers and new product launches determine the future buyback budget.
- Unlocks and circulating supply: evaluate reserve demand alongside scheduled token releases.
- Execution quality: fees, slippage and unconverted balances reveal whether the mechanism works efficiently in practice.
Frequently asked questions
Is Pyth using 100% of gross product revenue to buy PYTH?
No. The policy applies to eligible revenue and assets received by the Pyth DAO. Existing revenue-sharing agreements determine how much of gross product revenue reaches the DAO.
Are the purchased PYTH tokens burned?
No. They are held in the Pyth Strategic Reserve under DAO control. Removing tokens from immediate circulation can affect available supply, but it is not the same as permanently destroying them.
Will PYTH holders receive reserve tokens?
Not under the current mandate. The operations multisig is prohibited from distributing, selling or borrowing against the accumulated PYTH without separate governance approval.
Does the 100% Rule guarantee that PYTH will rise?
No. It creates recurring demand linked to DAO revenue, but price still depends on liquidity, unlocks, market positioning, adoption and the broader crypto cycle.
How can investors verify the buybacks?
The Pythian Council is required to publish monthly reports covering receipts, conversion amounts, average execution prices, costs, slippage and on-chain transaction links.
This article is for informational purposes only and does not constitute financial or investment advice. Crypto assets and leveraged derivatives are volatile and may result in substantial losses.