$PYTH: Sigue el flujo de efectivo detrás de la regla de reserva del 100 %

Proof of X · 2026-10-17T10:46:54.000Z

Douro Labs informó de una distribución de 553,693 USDC a la Pyth DAO el 5 de octubre. Para $PYTH, ese ingreso en efectivo es un punto de partida más útil que el titular de la recompra del «100 %»: la cuestión económica es qué proporción de los ingresos recaudados de los clientes se convierte en una compra real en el mercado. El anuncio de Pyth del 8 de octubre describe su nueva política de reservas. OP-PIP-136 sustituye las votaciones mensuales recurrentes sobre compras por un marco permanente. Esto supone una mejora sustancial en la vía que lleva de la actividad comercial a la acumulación de tokens. También es una política con varios denominadores distintos.

Douro Labs reported a 553,693 USDC distribution to the Pyth DAO on October 5. For $PYTH, that cash receipt is a more useful starting point than the "100%" buyback headline: the economic question is how much collected customer revenue becomes an actual market purchase.
Pyth's October 8 announcement describes its new reserve policy. OP-PIP-136 replaces repeated monthly purchase votes with a standing framework. This is a substantive improvement in the route from commercial activity to token accumulation. It is also a policy with several distinct denominators.
Where the customer's dollar goes
For eligible DAO-owned products, Pyth says the DAO receives 60% of revenue. Committing all of that share to the reserve means 60 cents per dollar of eligible product revenue before considering payment form and execution. It does not redirect the entire customer dollar or change the existing commercial split.
The immediate beneficiary is the DAO treasury. PYTH provides governance participation, while the reserve creates a revenue-funded source of token accumulation. These arrangements establish neither an automatic cash dividend for every holder nor a token burn.
Douro's October 5 report links the 553,693 USDC distribution to the approved revenue-sharing framework. Its wording gives inconsistent revenue-period descriptions: one sentence references August 1–September 1 and another says September. I use it as a dated, issuer-reported distribution, not a clean monthly growth observation. The linked Solana explorer did not expose transaction details in the available reader, so independent onchain settlement verification remains incomplete.
A better authorization is not a fixed purchase multiplier
The earlier system allocated one-third of the non-PYTH treasury balance each month. The new framework encompasses eligible receipts and existing eligible treasury assets. A treasury stock and a period's income are different bases; replacing one-third with 100% does not by itself establish three times the executed buying.
OP-PIP-136 also distinguishes direct PYTH distributions from open-market purchases. In the preceding September 9 discussion, a Douro contributor committed future Pyth Pro-related distributions to monthly USDC settlement. That supports a traceable cash-to-swap route, and the reported October receipt is consistent with that direction. It still requires execution evidence after receipt.
Operational plumbing matters. The October 7 OP-PIP-140 proposal, now marked passed, specified recovery of 34,375.871282 USDC and a subsequent transfer of 748,076.168209 USDC to the execution multisig. Those were proposal-time amounts covering treasury assets. They are not independently verified swap proceeds or a second recurring-revenue figure to add to the October 5 receipt.
The scale and the remaining supply
Pyth's October 5 operating report put September paid subscriptions at approximately $11.5 million in annualized revenue, versus $10.4 million in August. ARR is a run-rate measure. It is not the DAO's collected cash, protocol net profit, or a guaranteed repurchase budget. Applying a 60% share indiscriminately to the entire reported business would also assume matching product eligibility.
The original tokenomics capped supply at 10 billion PYTH, with 15% initially circulating and vesting milestones at 6, 18, 30 and 42 months. Allocations included 52% for ecosystem growth and 22% for publishers: incentive inventory and customer-funded purchases have different funding sources.
Tokenomist's October 17 09:21 UTC snapshot reports 7,874,959,029 circulating tokens. The gap to the cap is approximately 2.125 billion, or 27.0% of that reported float. The tracker lists May 19, 2027 as the next unlock date. The exact next tranche amount was not independently confirmed here; the entire remaining gap must not be relabelled as that tranche. Unlocking also does not establish actual selling. Reserve acquisitions transfer existing tokens into treasury ownership without cancelling vesting obligations.
The competitive hurdle
Chainlink offers an existing alternative route from offchain enterprise and onchain service revenue into LINK through its reserve framework. Its broader data, cross-chain and workflow offering competes for infrastructure budgets. Pyth's paid-data catalog and subscription distribution therefore need to retain customers at sustainable acquisition and delivery costs; a larger allocation percentage alone cannot establish better commercial economics.
The strongest countercase is that a reserve balance can rise through direct token settlement or one-off treasury conversions while repeat customer cash collection disappoints. A useful execution report would separately identify eligible cash receipts, market swaps, direct PYTH deliveries, unconverted balances and fees. Matching those flows avoids double-counting the same revenue and distinguishes recurring demand from transition funding.
Sources checked October 17, 2026:
[1] Pyth, October 8 policy announcement: https://www.pyth.network/blog/the-100-rule-every-dollar-the-pyth-dao-earns-now-buys-pyth
[2] Passed OP-PIP-136: https://forum.pyth.network/t/passed-op-pip-136-pyth-strategic-reserve-v2/2711
[3] September 9 discussion and Douro reply: https://forum.pyth.network/t/pyth-strategic-reserve-v2-aligning-pyth-accumulation-with-pyth-pro-revenue/2696
[4] October 5 distribution report: https://forum.pyth.network/t/pyth-pro-douro-labs-report-september-2026/2720
[5] Passed OP-PIP-140: https://forum.pyth.network/t/passed-op-pip-140-recover-stranded-dao-usdc-transfer-the-treasury-to-the-pythian-council-ops-multisig-and-clarify-direct-fee-repatriation/2722
[6] September operating report, published October 5: https://www.pyth.network/blog/pyth-september-2026-report
[7] Original tokenomics, October 11, 2023: https://www.pyth.network/blog/understanding-the-pyth-tokenomics
[8] Tokenomist supply/unlock snapshot: https://tokenomist.ai/pyth-network
[9] Chainlink reserve framework, August 7, 2025: https://chain.link/blog/chainlink-reserve-strategic-link-reserve
My take: The new framework is constructive for PYTH's recurring demand because it gives commercial receipts a defined accumulation route with less governance delay. I would credit the next monthly execution report for verified cash-funded purchases, separating direct token deliveries and legacy treasury conversions. Sustained customer receipts reaching swaps would strengthen this judgment; rising reserves financed mainly by transition assets would weaken the recurring-demand case.
NFA. DYOR.