Originally published at https://mrnasdog.com/research/pyth/inflation
Pyth Network cannot create another PYTH — the token's mint account on Solana has surrendered both its minting authority and its freezing authority, so the 10,000M PYTH ceiling is enforced by code rather than by policy. Across the 90 days to Sep 7 2026 the Pressure Framework books 267.5K PYTH of sell pressure against 3.62M PYTH of open-market buyback, a net of -0.04%, with -0.03% projected forward. The constraint that matters is not issuance but the calendar: the third of four annual vesting cliffs fired on May 20 2026, twenty days before this window opens, and the fourth and final 2,125.0M PYTH does not move until May 19 2027.
The verdict, in one paragraph
Against a circulating base of 7,874.96M PYTH, the framework books 267.5K PYTH of sell pressure and 3.62M PYTH of buy pressure over the trailing 90 days — a net of -0.04% — and projects -0.03% for the next 90 days on the post-upgrade buyback run rate. The inflation monitor reads +0.01% for the same window, a gap of 0.05 percentage points, comfortably inside the framework's 0.5pp tolerance, so no monitor-gap warning ships on the PYTH overview page. The sign of that small gap is itself mechanical rather than mysterious: the wallet the bought-back PYTH lands in sits inside the classified float, so a buyback can never register as a supply reduction in a classifier series — only the framework sees it. The label for PYTH is a fixed-supply oracle token in the quiet stretch between two annual cliffs, with a small revenue-funded buyback doing the only work on either side of the ledger.
Sell pressure: where new PYTH comes from
It does not come from minting, and it cannot. Read live on Solana this build, the PYTH mint account reports a null minting authority and a null freezing authority against a supply of 9,999.96M PYTH. For a Solana token both nulls are one-way: no vote, no upgrade and no key can hand either authority back. The only direction that supply figure can ever move is down. So Sell #1, protocol inflation, is 0, and it is 0 permanently rather than pending a decision. Pyth Network did once move existing PYTH into the float through Oracle Integrity Staking, which paid stakers out of an allocated reward pool; a governance vote set that reward rate to zero and the pool ran dry on Apr 22 2026, seven weeks before this window opens. Staking and slashing on Pyth Network still run; the payout does not. The residual of that pool was withdrawn back to the Pyth DAO treasury inside the window, on Jul 23 2026, which is a movement out of the reward programme rather than into the market.
Sell #2, vesting unlocks, is 0, and this is the row that decides the page, so it is worth showing how the zero was earned rather than assumed. Pyth Network releases most of its supply in four equal annual cliffs of 2,125.0M PYTH. Three have fired, the most recent on May 20 2026. Ninety days back from Sep 7 2026 is Jun 9 2026, which puts that cliff twenty days outside the window and the next one, on May 19 2027, more than eight months beyond it. A cliff outside the window contributes nothing, and a trailing average is never substituted for one. The framework then checked the realised side rather than stopping at the calendar: the two Pyth staking accounts that took the largest share of the May release still hold 721.8M PYTH and 342.1M PYTH, and neither account carries a single transaction anywhere between Jun 9 2026 and Sep 7 2026 — so their balances are identical at both ends of the window, and 1,064.0M PYTH of freshly released supply demonstrably never moved. The arithmetic closes on the other side too: the on-chain supply less the classified float leaves exactly 2,125,000,000 PYTH unvested, precisely the one remaining tranche. Scheduled and realised agree, at zero.
Sell #3, Foundation and unscheduled unlocks, is 267.5K PYTH, and it is the only sell-side flow on the page. Eleven grant transfers left the Pyth DAO treasury through the governance program on a single day, Jun 9 2026 — seven of 12,500 PYTH and four of 45,000 PYTH — and nothing else left the treasury for the remaining 89 days. Because those payouts are sporadic and sit on no published calendar, the forward leg carries them at 0 rather than projecting a rate that does not exist. Sell #4, long-term locked or bankruptcy, is 0: PYTH has no bankruptcy estate, no trustee and no court-ordered distribution attached to it.
Buy pressure: where new PYTH goes
Buy #1, programmatic buyback, is 3.62M PYTH, and it is the largest number on the page in either direction. The Pyth DAO deploys one third of its treasury balance every month on open-market purchases of PYTH funded by what the network earns from Pyth Pro, Pyth Core, Entropy and Express Relay. Three rounds executed inside the window: 1.80M PYTH on Jun 9 2026, 1.14M PYTH on Jul 29 2026 and 0.67M PYTH on Aug 25 2026, for 3,618,164 PYTH in total. Each round was followed from the swap through to the treasury account, where the credited amounts match the reported ones to the sixth decimal, and the treasury's whole 90-day movement — 18.97M to 38.51M PYTH — reconciles against the seventeen transactions that produced it with a residual of zero. The bought PYTH is kept, not destroyed, which is why it comes back on the sell side as overhang. The forward leg is deliberately not the trailing average: the Pyth Core upgrade activated on Jul 31 2026, inside the window, moving the network onto mandatory keys and paid subscriptions, so the trailing figure blends two revenue regimes. Only the Aug 25 2026 round is entirely post-change, and three of those is 2.01M PYTH — the conservative read, since rounds have been decaying by roughly a third a month as the treasury is drawn down.
Buy #2, protocol fee burn, is 0, and both places a burn could show up were read rather than one. The Solana address tokens go to when they are meant to disappear holds under 2 PYTH. The count of PYTH in existence stands at 9,999,961,194 against a 10,000,000,000 genesis, which means fewer than 39,000 PYTH have been destroyed in the token's entire life — under 0.0005% of the float, so even attributing all of it to this window rounds to nothing. The mechanism agrees with both surfaces: Pyth Network routes revenue into buying PYTH back and holding it, not into destroying it. Buy #3, Foundation buy, is 0, because the DAO purchase is the only market buying anyone does here and it is already counted as Buy #1; booking it twice would double the entire buy side. Buy #4, new long-term lock, is 0: staking is live but pays no reward, so it draws nothing in, no new vault or term deposit was created, and the bought-back PYTH is not re-counted here either.
Foundation and overhang
The overhang on PYTH is large, fully enumerated and almost entirely on a calendar. The dominant item is the final vesting tranche: 2,125.0M PYTH still unvested, roughly 21% of the ceiling, releasing in one step on May 19 2027 and readable at every rebuild as the difference between the on-chain supply and the classified float. The second is the Pyth DAO treasury, at 38.51M PYTH at the end of the window against 18.97M at the start; it is the only pot on this token with a spender rather than a schedule, it is where every bought-back PYTH accumulates, and its address is read directly from Solana on each rebuild. The third is the already-released cohort sitting in Pyth staking accounts — 1,424.0M PYTH across four accounts untouched since May 2026, of which the largest single account holds 721.8M PYTH. These coins are counted as circulating but have never been to market.
The trigger sentence applies to all three. If the Pyth DAO treasury balance, the unvested remainder, or any of the dormant staking accounts falls between refreshes, that outflow enters Sell #3 at the next refresh. The treasury is the one to watch most closely, because it moved in both directions inside this window: out on Jun 9 2026 as grants, and in on Jul 3 2026 and Aug 4 2026 as two transfers of roughly 7.67M PYTH each, which are neither purchases nor releases and are therefore booked in neither ledger.
How PYTH compares to other cliff-vested oracle tokens
PYTH sits in an unusual intersection. On the issuance axis it is stricter than almost anything: a hard 10,000M ceiling with the minting authority irreversibly surrendered is a stronger commitment than a halving schedule, because a halving chain still mints on every block and simply mints less over time. Pyth Network mints nothing at all, and cannot be made to. Compared with uncapped continuous-emission layer-1s, where a staking-linked emission of 5% to 15% a year is normal and the ceiling is a policy rather than a number in code, PYTH does not have an issuance problem to solve.
What it has instead is a cliff structure, and that is the comparison that matters. A continuously-vesting token releases a thin slice every second, so its inflation reading is a steady positive number that never surprises anybody. Pyth Network releases in four annual steps, which means its supply reading is not one number but two alternating states: a single day each May when roughly 2,125.0M PYTH — 27% of today's float — becomes tradable at once, and eleven months of near-total stillness. This page is the stillness. A reader who takes -0.04% as a permanent property of PYTH will be wrong on one specific date, and the framework's job is to say which one: May 19 2027.
The third comparison is to exchange tokens that run quarterly buybacks and burns. Those offset issuance with a demand-linked removal that scales with usage and can push a reading genuinely negative. Pyth Network has the same shape of mechanism — a buyback fed by real subscription revenue — but two differences change what it does to the ledger. It buys and holds rather than burning, so the coins stay in the float as treasury overhang rather than leaving the supply permanently. And it is small: 3.62M PYTH over 90 days is 0.046% of circulating supply. For the buyback to offset a single annual cliff, Pyth Network would need to buy roughly 2,125.0M PYTH a year, which is about one hundred and fifty times the current rate. That is the distance between the mechanism existing and the mechanism mattering.
What to watch in the next 90 days
First, the monthly PYTH Reserve purchase, which is the only recurring flow on either side of this ledger and has fallen from 1.80M to 0.67M PYTH across three rounds; whether the Pyth Core paid model reverses that decay is the single biggest swing factor in the next reading. Second, Pyth Network revenue itself — reported at roughly $10.4M of annualised revenue in Aug 2026 — since a third of whatever reaches the DAO treasury becomes the buyback. Third, Pyth DAO governance, which has re-authorised the purchase programme in each of the last three months and is also the body that could fund a new staking reward pool; a refunded pool would move existing PYTH into the float and would enter Sell #3, not Sell #1, because minting stays impossible. Fourth, the Pyth DAO treasury balance at 38.51M PYTH, which is read on every rebuild and where any grant round shows up immediately. Fifth, the final vesting cliff on May 19 2027: it is outside every window this page covers, but it is the largest single dated supply event PYTH has left.
Summary
The MrNasdog Pressure Framework reads PYTH at -0.04% over the trailing 90 days and -0.03% projected forward: mixed flows, supply roughly steady. The structural mechanism is a fixed 10,000M supply with minting irreversibly disabled on Solana, a staking reward stream voted to zero and exhausted on Apr 22 2026, and a vesting calendar that releases in four annual steps rather than continuously — so a window that contains no step contains almost no supply. The key risk is exactly that calendar: on May 19 2027 the final 2,125.0M PYTH becomes tradable in a single day, and a 3.62M quarterly buyback that buys and holds rather than burning cannot meaningfully absorb it. The ceiling is the genuine comfort: no vote is needed to stop Pyth Network minting, because no vote could start it.
MrNasdog Pressure Framework analysis of PYTH, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 7 2026.
Top comments (0)