DEV Community: MrNasdog

BLIFE Inflation Analysis · September 2026 · Mixed flows, supply roughly steady

MrNasdog — Thu, 27 Aug 2026 04:02:07 +0000

Originally published at mrnasdog.com/research/binancelife/inflation by MrNasdog.

BinanceLife issued nothing over the last 90 days and holders burned 5,048 BLIFE of their own accord — a net of −0.00% against −0.02% from our supply monitor, a gap of 0.02 percentage points and no warning chip. BLIFE is supply-inert by construction: the BEP-20 contract on BNB Chain carries no mint function and no burn function anywhere in its compiled code, and its owner slot was set to the null address roughly one minute after launch on Oct 4 2025. The cap is not a promise, it is the absence of a lever — but the concentration risk that replaces dilution risk is real, and it is large.

The verdict, in one paragraph

For the 90-day window ending Sep 5 2026, the MrNasdog Pressure Framework reads BLIFE at −0.00% net, with −0.00% projected over the next 90 days. Our supply monitor reads −0.02% for the same trailing window — a gap of 0.02 percentage points, far inside the framework's half-point tolerance, so no ⚠ monitor gap chip is attached to the BLIFE overview page. That tiny residual is not issuance at all: the monitor infers supply from market value divided by price, and both of its endpoints are estimates of a number the chain shows to be the constant 1,000,000,000. We read the BinanceLife supply figure at both ends of the window and got the identical 256-bit word, and we read the burn address at both ends and in the middle and watched it climb from 428,029.6 to 433,078.0 BLIFE. A coin with no mint path is the cleanest possible reading in this framework, and BLIFE is a quiet, permanently capped memecoin whose supply story ended the day it launched.

Sell pressure: where new BLIFE comes from

Nowhere. Sell #1 — protocol inflation — is zero, and the proof is in the code rather than in a chart. A scan of the entire 3,822-byte deployed contract returns 35 callable functions, and not one of them creates a coin: there is no mint, no minter role, no cap function, and equally no burn. The only privileged entry point that exists is a transfer-mode switch, and when we simulated calling it this session from an arbitrary address the BinanceLife contract reverted with an owner check. It can never pass that check again, because the owner slot has read the null address since Oct 4 2025 — at both ends of this window and at every point we sampled between them. An independent contract-security surface read the same session agrees on every point: not mintable, no owner, no proxy, no hidden owner, no way to reclaim ownership, zero buy tax and zero sell tax.

Sell #2 — vesting unlocks — is zero for the same structural reason plus one more. BinanceLife launched on a BNB Chain memecoin launchpad with the whole supply created at deployment, so circulating supply, total supply and maximum supply are the same 1,000M figure both on the chain and on the market record. There is no non-circulating pocket for a cliff to come out of, and no mint path that could ever create one. Three separate surfaces checked this session report no vesting schedule, no funding round, no allocation table and no unlock calendar for BLIFE. Sell #4 — long-term locked or bankruptcy — is zero as well: no estate, trustee or court-administered pool holds BinanceLife, and the contract has no lock, escrow or vesting logic that could create one.

Sell #3 — foundation and unscheduled unlocks — is zero because there is nothing on the other side of BinanceLife to hold a reserve. There is no company, no foundation, no labs entity, no DAO treasury, no website, no whitepaper and no announcement channel; the coin is a Chinese-language community meme that grew out of a joke and was later listed on major venues. No public evidence of release in window — monitored.

Buy pressure: where new BLIFE goes

Buy #1 — programmatic buyback — is zero, and this is a clean zero rather than a number we could not see. BinanceLife transfers are untaxed, so the contract collects no revenue at all; there is no treasury, no multisig and no buyback wallet to fund one, and nothing published in this window claimed otherwise. Buy #2 — protocol fee burn — is zero for the matching reason: the BLIFE contract has no fee logic and no burn function, so its supply figure can never fall and no automatic destruction is possible. Buy #3 — foundation buy — is zero, because there is no entity in existence to do the buying.

Buy #4 — new long-term lock — is zero for this window, but the note behind it matters. The main PancakeSwap pool for BLIFE has 99.98% of its ownership certificates sitting at the burn address, which means that liquidity can never be withdrawn by anyone. That is a permanent lock in the strongest sense available on BNB Chain — but it was done at launch in Oct 2025, so it belongs to no 90-day window since and cannot be booked as fresh buy pressure.

The one live flow on the whole page is an extra row: 5,048 BLIFE sent to the burn address by holders across the window. We read it the only way it can be read. Because BinanceLife has no burn function, a burn here can never reduce the supply figure — a build that watched supply alone would have reported nothing at all and shipped a false zero on the coin's only real mechanism. So we read both surfaces at both ends: the supply figure held at 1,000,000,000, and the burn address rose by 5,048.4. That is roughly 0.0005% of the float per quarter — real, permanent, and far too small and too voluntary to call a mechanism. It is booked as a tracked extra rather than as a protocol fee burn, precisely so the fee-burn row can stay a truthful zero.

Foundation and overhang

BinanceLife has no team-controlled supply to enumerate — the deployer gave up the owner key a minute after launch and there is no entity that could hold a reserve. What replaces it is concentration, and on BLIFE the concentration is the story. Two exchange-custodial wallets held about 33.0% and 32.9% of the supply at the close of this window, roughly 66% between them. They also moved: the first went from 620,000,000 BLIFE at the start of the window to 330,000,000 at the end, while the second went from 0 to 329,348,766. That is an internal custody transfer between two wallets of the same exchange — about 290M BLIFE relocated with zero effect on supply — and under the framework's rules exchange custody belongs to depositors, not to an operator, so it stays out of Sell #3. Below those two, the largest identified wallets held exactly 29,500,000 BLIFE each at both ends of the window without moving a single coin; static for a full window leaves nothing to project from. We read these balances straight from the chain on each rebuild, and if any identified overhang's balance falls between refreshes, the outflow enters Sell #3 at the next refresh.

How BLIFE compares to other fixed-supply memecoins

BLIFE belongs to the class of fixed-supply memecoins with a renounced contract, and the useful comparison is mechanical rather than about price. Against a memecoin that keeps an active owner key — the common shape, where the deployer can still flip a tax, pause transfers or mint — BinanceLife has genuinely given that up, and we verified it by simulating the call rather than by trusting a claim. That is the difference between a project that says it is safe and one where the dangerous function does not exist in the compiled code at all.

Against a memecoin that runs a buyback-and-burn programme funded by a transaction tax, BLIFE is the opposite trade. A taxed memecoin buys back its own supply but leaves a treasury, a discretionary operator and a growing overhang behind it; BinanceLife has none of those, and pays for it by having no deflationary engine either. Its supply is simply frozen. And against a fee-burn chain, where every transaction destroys a slice of the native asset and the burn scales with usage, BLIFE has no usage-linked mechanism whatsoever — the 5,048 coins burned this window were sent by individuals, not by a protocol. The result is a coin that cannot dilute you and cannot compound for you: a hard 1,000M ceiling where the only variables left are demand and where the coins sit.

What to watch in the next 90 days

Four things would move this reading, and none of them is issuance. First, the two exchange wallets holding roughly 66% of BLIFE between them: another large relocation is harmless, but a sustained fall in the combined balance would be coins reaching the open float, and that is what we re-read from the chain on every rebuild. Second, the burn-address balance, currently 433,078 BLIFE — if voluntary burning ever accelerates into a published community programme with a stated quantum, the extra row is promoted into a real buy row. Third, the burned PancakeSwap liquidity certificates: they cannot be un-burned, but a large new pool with unburned certificates would introduce withdrawable liquidity that does not exist today. Fourth, the absence of a project surface itself — BinanceLife has no blog, forum or vote portal, so the appearance of any official channel after Sep 5 2026 would be the first thing this framework has ever had to read from the project rather than from the chain.

Summary

BinanceLife (BLIFE, 币安人生) is a fixed 1,000M memecoin on BNB Chain whose supply cannot change: the contract has no mint function and no burn function, and its owner is the null address, verified this session by scanning the deployed bytecode and by simulating the only privileged call it exposes. Across the 90 days to Sep 5 2026 the framework reads −0.00% net — nothing issued, and 5,048 BLIFE voluntarily burned by holders — against a monitor reading of −0.02%, a gap of 0.02 percentage points that is price-rounding noise rather than a conflict. The key risk is not dilution but distribution: roughly 66% of BLIFE sits in two exchange-custodial wallets, and one of them moved 290M coins inside this window. The ceiling is the strongest kind — 1,000M, enforced by the absence of a lever rather than by a promise — but a permanently flat supply is exactly that: flat, not shrinking.

MrNasdog Pressure Framework analysis of BLIFE, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 5 2026.

STABLE Inflation Analysis · September 2026 · Supply growing, projected to keep growing

MrNasdog — Thu, 27 Aug 2026 04:02:03 +0000

STABLE Inflation Analysis · September 2026 · Supply growing, projected to keep growing

Originally published at https://mrnasdog.com/research/stable/inflation

Stable cannot create a single new STABLE — all 100B STABLE were issued in one event on Dec 8 2025, the chain still reports exactly that number, and asking the token to mint one more unit comes back refused in the protocol's own words — and yet the Pressure Framework reads STABLE at +10.06% over the trailing 90 days and +10.06% over the next 90. All of it is one mechanism: the Stable Foundation letting its own ecosystem allocation out continuously, about 29.2M STABLE every day, 2,627.7M STABLE across 90 days, against a buy side of exactly zero on a circulating base of 26,107.5M STABLE. A published lock dated Oct 5 2026 would close that valve; it has not executed, so this page does not count it.

The verdict, in one paragraph

Against a circulating base of 26,107.5M STABLE, the framework books 2,627.7M STABLE of sell pressure and 0 of buy pressure over the trailing 90 days — a net of +10.06% — and projects +10.06% for the next 90 on the same unbroken daily release. The inflation monitor reads +11.36% for the same window, a gap of 1.29 percentage points, which is over the framework's 0.5pp tolerance and therefore ships with a monitor-gap warning on the overview page. That gap decomposes cleanly and completely: 1.17pp is base convention, because the monitor divides its supply change by the 90-day-old supply of 23,428.3M while the framework divides by today's 26,107.5M, and the remaining 0.12pp is the monitor's market-derived supply estimate running about 1% above the release schedule's own arithmetic. The label for STABLE is a zero-emission token diluting purely through one foundation's release valve: the token cannot inflate, but its tradable float does, every single day.

Sell pressure: where new STABLE comes from

It does not come from minting, and this is the rare row that can be settled outright. Sell #1, protocol inflation, is 0. The Stable whitepaper states that issuance was a single event on Dec 8 2025 covering the entire supply of 100,000,000,000 STABLE, both circulating and locked, and that no further issuance is possible. The chain agrees to the last decimal: the token's total supply read exactly 100,000,000,000 at block 38,492,583 on Sep 7 2026, identical to its maximum. A flat number proves nothing on its own, so this build went further and asked the token to mint one unit; the call came back rejected with the protocol's own message that minting the governance token is not allowed, while a transfer call answered as a live function that merely lacked a balance. A refused-but-recognised mint on a working write path is a real measurement, not a constant nobody can move. Staking does not change it either: validators on Stable secure the chain with delegated STABLE, but the reward they distribute is a share of the USDT0 gas revenue collected in the protocol treasury — denominated in a stablecoin, not in STABLE. A yield that pays in someone else's asset creates none of your own.

Sell #2, vesting unlocks, is 0 as well. The Team and the Investors & Advisors allocations are 25,000M STABLE each — half the entire supply between them — and neither has released a single token. The original terms opened a one-year cliff on Dec 8 2026, which lands two days past the end of this forward window, and the rewritten terms published in August replaced them with a first release floor on Dec 8 2027. Under either set of rules the answer for these 90 days is zero.

The entire supply story is Sell #3, the Stable Foundation's ecosystem release, at 2,627.7M STABLE. The Foundation holds the 40% ecosystem and community allocation. 8% of total supply was unlocked at mainnet launch, which together with the 10% genesis distribution set the day-one float at 18,000M STABLE. The remaining 32,000M has been coming out ever since across 36 months — about 29.2M STABLE a day, 2,627.7M per 90 days. It is worth being precise about the shape, because most coverage gets it wrong: this is a continuous drip, not a monthly cliff. The tradable float rose on 84 of the last 90 days, and the three dates widely reported as unlocks each added less than an ordinary day — Jun 8 2026 added 26.9M, Jul 8 2026 added 22.3M and Aug 8 2026 added 14.9M, against a 29.6M daily average. A monthly model would have counted two firings inside this window and produced 1,777.8M; the float actually grew 2,660.3M. The schedule arithmetic and the measured float agree to 1.2%, and the schedule is what ships. No STABLE is created by any of this — the coins already existed inside the 100,000,000,000 ceiling. What changes is that they stop being held back and become tradable float, which is exactly what the Pressure Framework measures and exactly what a fixed supply does not protect a holder from. Sell #4, long-term locked or bankruptcy, is 0: Stable launched in December 2025 and has no estate, no trustee and no expiring lock.

Buy pressure: where new STABLE goes

Nowhere, this window or next. Buy #1, programmatic buyback, is 0 — Stable runs no programme that spends treasury money repurchasing STABLE on the open market. Gas is charged in USDT0 and accrues to a smart-contract treasury which validators may pass to their delegators, still denominated in that stablecoin; none of it is ever converted into STABLE. A fee switch routing network revenue into buybacks or burns has been publicly discussed and no commitment has been made either way, so the row is watched rather than closed.

Buy #2, protocol fee burn, is 0, and it was checked on both surfaces rather than one. The burn addresses hold exactly nothing — and because a burn address can receive but never spend, a balance of zero today proves that nothing was ever sent to one, inside this window or before it. Total supply reads the same 100,000,000,000 as the day everything was issued, so nothing was destroyed by supply reduction either. The two surfaces agree, which is the outcome the framework wants and rarely gets. There is also no path for either to move: the token exposes no burn function at all, and transactions on Stable are paid for in a stablecoin, so STABLE is never consumed by using the network.

Buy #3, Foundation buy, is 0 — no dated open-market purchase of STABLE by the Stable Foundation or anyone acting for it landed inside the window. Buy #4, new long-term lock, is 0, and this is the one row on Stable that deserves an argument rather than a sentence. Stable's whitepaper version 2.0, dated Aug 14 2026, introduces a Universal Lock and states that all STABLE locked as of Oct 5 2026 — 82,000,000,000 STABLE — releases across seven scheduled floors beginning Dec 8 2027, and that Foundation tokens unlocked since launch above the 8% day-one figure are relocked on that same date. That is a real, dated commitment in the project's own primary document, and Oct 5 2026 does fall inside this forward window. It is still counted at zero, for three reasons. It has not executed. No lock contract has been published or deployed that anyone could read, so no surface the framework watches could confirm it. And the balance it would lock has been sitting still in Foundation hands rather than out in the market, which means relocking it takes nothing off any exchange and asks nobody to buy anything — it is a reclassification, not demand. The float has not reacted either: across the 21 days since the whitepaper was published it rose 28.8M a day, against a 29.6M full-window average. Because the commitment is not counted as a buy, it is also not used to cut the forward sell row — an unexecuted promise moves neither column, or it flatters one side for free.

Foundation and overhang

The overhang on STABLE is enormous, fully enumerated, and almost entirely undated. 73,892.5M STABLE sits outside the tradable float — about three quarters of everything that exists. The largest items are the Team allocation at 25,000M STABLE and the Investors & Advisors allocation at 25,000M STABLE, both entirely locked, neither with a release before Dec 8 2027 under the rewritten terms. The third is the Stable Foundation's own remaining ecosystem balance, roughly 23,900M STABLE still held back out of the original 32,000M, draining into the float at about 29.2M a day. A fourth item is unusual enough to name separately: the Foundation supply already released since launch — the roughly 8,100M STABLE that took the float from 18,000M to 26,107.5M — appears to be sitting in Foundation hands rather than dispersed to third parties, which is both why the announced relock is mechanically possible and why counting it as demand would be wrong.

None of these balances is readable directly. Stable publishes no Foundation wallet address, and the chain's public infrastructure serves only its most recent block — no historical state and no log history beyond about a thousand blocks — so these overhangs are tracked by disclosure and by the classified float, not by a wallet sweep. That limitation is stated rather than hidden, and it is why the release row is built from the project's own allocation arithmetic. The trigger sentence applies to every item above: if any of these balances falls between refreshes by more than the daily release accounts for, that outflow enters Sell #3 at the next refresh — and if the Oct 5 2026 relock executes and the float actually falls toward 18,000M, it enters Buy #4 at the next refresh instead.

How STABLE compares to other zero-emission chains

STABLE belongs to a small and strict class: tokens with a hard supply ceiling that never switched issuance on in the first place. That is a harder commitment than a halving schedule. A halving-model chain like Bitcoin still mints on every block, just at a decaying rate, so its inflation reading is positive but shrinking on a known clock. Stable mints nothing at all, and unusually it does not even need its own token to pay for blockspace — gas is charged in a stablecoin, so the classic staking-inflation loop that funds security on almost every proof-of-stake layer-1 simply does not exist here. On the pure issuance axis, STABLE is stricter than any proof-of-work chain and far stricter than an uncapped continuous-emission layer-1, where a staking-linked emission of 5% to 15% a year is normal.

And yet STABLE reads +10.06% while a mid-cycle Bitcoin reads a fraction of a percent. That is the whole lesson: a fixed supply constrains total supply, not tradable float, and the two move independently. In shape STABLE is far closer to a recently launched token working through its distribution than to a mature capped chain — it is nine months past a token generation event that put only 18% of supply into circulation, and the other 82% has to arrive somehow. The difference from a typical four-year investor vest is that STABLE's current release is continuous rather than cliff-based, so there is no single dated unlock to trade around; the release is smooth, predictable and relentless.

The sharpest comparison is to exchange tokens that run quarterly buybacks and burns. Those offset issuance with a demand-linked removal that scales with usage, and their inflation readings can go genuinely negative. Stable has the raw material for that — a chain settling real stablecoin volume, with fees pooling in a treasury — but the treasury collects USDT0, and none of it is converted into STABLE. Until a fee switch exists, network success accrues to stakers as stablecoin yield rather than as a bid under the token. That is the gap between a chain having revenue and a token having demand.

What to watch in the next 90 days

First and above everything, Oct 5 2026: the Universal Lock's effective date, on which the whitepaper says the Foundation's released supply is locked back up and the float returns toward 18,000M STABLE. If the classified float actually falls, this page's forward number reverses from +10.06% to roughly −31% in a single refresh — which is precisely why it is not being counted before it happens. Second, the daily release itself, at about 29.2M STABLE a day: if it simply continues past Oct 5 2026, the lock is prose and the forward reading stands as written. Third, any deployment of an actual lock contract — none is published today, and an address anyone can read would move this from a commitment to a measurement. Fourth, a fee switch: converting any part of the USDT0 gas treasury into STABLE would create the first buy row this coin has ever had. Fifth, the Dec 8 2026 anniversary, the date the original one-year cliff would have opened on 50,000M STABLE of team and investor supply — two days outside this window, and superseded on paper by the Dec 8 2027 first floor, but worth confirming rather than assuming.

Summary

The MrNasdog Pressure Framework reads STABLE at +10.06% over the trailing 90 days and +10.06% projected forward: supply growing, projected to keep growing. The mechanism is not inflation but distribution — Stable mints nothing, burns nothing, and holds a fixed ceiling of 100,000,000,000 STABLE proven by a refused mint call, while the Stable Foundation releases 2,627.7M STABLE per 90 days out of a 73,892.5M reserve that is still three quarters of the token. The key risk is that this is mechanical and runs every day regardless of price, with no burn and no buyback anywhere to offset it. The one genuine comfort is the ceiling — and the one genuine unknown is Oct 5 2026, a published date on which that release is supposed to stop for fourteen months. This page will count that the day the float falls, and not a day before.

MrNasdog Pressure Framework analysis of STABLE, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 7 2026.

LIT Inflation Analysis · September 2026 · Supply shrinking, projected to keep shrinking

MrNasdog — Thu, 27 Aug 2026 02:46:17 +0000

Originally published at mrnasdog.com/research/lit/inflation by MrNasdog.

LIT, the token of the perpetuals exchange Lighter, shrank −1.36% on the market in the 90 days to Sep 5 2026, because Lighter spends every dollar of its trading-fee revenue buying LIT back — 3.50M LIT across the window — while the only new LIT reaching holders was 0.10M of staking rewards drawn from the ecosystem reserve. Our supply monitor reads the same window at +0.12%, a gap of 1.48 percentage points, and that gap is the monitor's own denominator rather than a disagreement about LIT: the circulating-supply figure it is built on has been pinned at exactly 250,000,000 LIT all window, so it never saw the buyback or the 15,638,703 LIT burn of Jul 10 2026. Forward, the Pressure Framework reads LIT at −0.94% — still shrinking, on a buyback that has accelerated with exchange revenue — and the whole picture changes on Dec 27 2026, when a 500M LIT insider cliff falls due.

The verdict, in one paragraph

For the 90-day window ending Sep 5 2026, the MrNasdog Pressure Framework reads LIT at −1.36% net supply change and projects −0.94% forward. Total sell pressure on LIT was 0.10M LIT, all of it the staking payout Lighter now funds from its ecosystem reserve; total buy pressure was 3.50M LIT of fee-funded buyback, and every other row on both ledgers is a genuine zero. Our monitor reads +0.12% for the same window — a gap of 1.48 percentage points, well past the half-point tolerance, so a monitor-gap chip ships on the LIT overview. The deep walk located the cause precisely and it is not a missing flow: LIT's published circulating supply has been the flat constant 250,000,000 since the airdrop, so a supply series derived from it cannot register a buyback that removes LIT from the float, nor a burn whose units left a reserve that series never counted. The cite-able label for LIT is a fixed-supply exchange token that is deflationary on the traded float while three-quarters of its supply waits behind an undrawn reserve and a single insider cliff.

Sell pressure: where new LIT comes from

Sell #1, protocol inflation, is the only live sell row on LIT and it is small: 0.10M LIT. Lighter has no block reward and no emission curve — LIT is an ERC-20 on Ethereum whose 1,000,000,000 genesis reads back unchanged from the contract today. The one channel that puts new LIT into holders' hands is the staking payout, and in mid-2026 Lighter changed where that payout comes from: instead of pre-launch revenue, staking yield is now drawn from the 250M LIT ecosystem reserve, targeting roughly 6% a year on about 125M LIT staked, which is 7.5M LIT a year, or about 1.85M LIT per 90 days. On the chain, the reserve has drawn exactly 100,000 LIT for that purpose, on Jul 3 2026 — one top-up, not a run rate. The Pressure Framework books what the chain released rather than what the schedule entitles, so both columns carry the realised draw and the undrawn remainder is treated as overhang instead of as supply.

Sell #2, vesting unlocks, is zero for LIT, and it is zero for the plainest possible reason: nothing vests in this window. The Lighter team allocation of 260M LIT and the early-investor allocation of 240M LIT — 500M LIT together, half of all LIT — sit behind one cliff dated Dec 27 2026, twelve months after the token generation event, after which they release evenly across three years to late 2029. Every identified locked Lighter wallet was read on-chain at both ends of the window and not one of them moved a single token, so the row is zero on measured evidence and not by omission. That cliff is the single most important dated fact about LIT supply, and it is not in these numbers yet.

Sell #3, foundation and unscheduled unlocks, carries no value this window, but it carries the most watching. The enumerated LIT overhangs are the ecosystem reserve wallet, which still holds 234.26M LIT against no published release calendar; the 260M LIT team allocation; the 240M LIT investor allocation; the treasury router that carried the burn and the reward router that carries staking payouts, both of which read 0 LIT at both ends of the window; and a trading-incentive pool for a wallet-partner community that sits inside the reserve and pays out weekly. Neither that pool's weekly quantum nor its end date is published, and the payouts run inside the exchange rather than on-chain, so it is a watched item with no defensible number rather than a number rounded to zero. Sell #4, long-term locked or bankruptcy, is zero because Lighter is a running exchange with no estate, no trustee and no court-ordered distribution of LIT.

Buy pressure: where new LIT goes

Buy #1, the programmatic buyback, is the whole of LIT's buy side and the reason this page reads deflationary. Lighter routes 100% of exchange trading-fee revenue into open-market LIT purchases executed as rolling daily 24-hour orders. Over this window that is $8,005,179 of protocol revenue converted day by day into 3.50M LIT at a revenue-weighted average of $2.29 — the arithmetic is each day's revenue divided by that day's price, summed, not a single average applied to a total.

A tokenomics change in mid-2026 redirected the repurchased value from accumulation into permanent retirement, and the first retirement executed on Jul 10 2026 in two transfers totalling 15,638,703 LIT sent to an unspendable dead address. That figure settles Lighter's buying since launch rather than this window's buying: the same revenue-over-price arithmetic applied from the token generation event to the end of June returns 15.66M LIT, matching the burn to 0.14%. So the burn belongs in this analysis as proof of destination — evidence that Lighter's buybacks end in destruction rather than in a treasury — and not as 90 days of buy pressure. Booking it as this window's value would push six months of buying into a 90-day column.

The burn itself was verified on both supply surfaces rather than on either alone, because each one fails differently. The dead address balance rose from 0 to 15,638,703 LIT across the window, while LIT's total supply held at exactly 1,000,000,000 at both ends — the signature of a transfer-style burn rather than a supply-reducing contract call. A check watching total supply alone would have reported no burn at all. The router that carried the transfers held 0 LIT at both window ends and its inflows and outflows closed to the token, so nothing was quietly parked along the way: this is a burn, not a buy-and-hold dressed up as one.

Buy #2, protocol fee burn, is zero: Lighter collects trading fees in a stablecoin rather than in LIT, so there is no automatic LIT-denominated fee burn, and the destruction that does occur is the buyback's terminal step and is counted once. Buy #3, foundation buy, is zero — every inbound transfer to Lighter's treasury router came from Lighter's own wallets rather than from the market. Buy #4, new long-term lock, is zero as well: LIT staking carries no lock-up that removes float, and the staking contract's balance actually fell across the window rather than rising.

Foundation and overhang

Lighter's overhang is unusually concentrated and unusually legible. The ecosystem reserve is the largest identified team-controlled wallet, funded once at genesis on Jan 7 2026 with 250M LIT and now holding 234.26M LIT after the July burn and the July staking release. It has no published release schedule beyond a yield target it has been drawing far below, and it is refreshed by direct chain read on every rebuild. Alongside it sit the treasury router that carried the burn and the reward router that carries staking payouts — both read 0 LIT at both ends of the window, so neither is currently an accumulation sink. The remaining overhang is the locked team and investor allocation of 500M LIT behind the Dec 27 2026 cliff, plus the undrawn portion of the staking entitlement the reserve has not released.

The trigger is the same for all of them: if any of these balances falls between refreshes, the outflow enters the Foundation and unscheduled-unlocks row at the next refresh. Nothing about Lighter's current reading survives a reserve wallet that starts moving.

How LIT compares to other perpetual-DEX tokens

LIT belongs to the class of perpetual-DEX tokens that recycle exchange revenue into their own float. Within that class the meaningful split is what happens to the repurchased tokens. A venue that buys and parks its token in a treasury has not reduced supply at all; it has moved custody, and the parked balance is a standing overhang that a governance decision can redeploy. A venue that buys and burns has cancelled the supply irreversibly. Lighter moved from the first model to the second in mid-2026, and the Jul 10 2026 transfer to a dead address is the proof the change was executed rather than merely announced.

Where LIT differs from the fee-burn model used by high-throughput L1s is that Lighter has no LIT-denominated gas or fee sink. An EIP-1559-style chain burns a share of every transaction automatically, so its burn scales continuously with usage and needs no discretionary step. Lighter's burn is discretionary in timing even though it is revenue-linked in size — it fires in batches at a cadence the project has not contractually fixed. That makes LIT's buy side lumpier than a fee-burn chain's and far more sensitive to a single policy reversal.

The comparison that matters most is against tokens with a hard cap and an exhausted vesting schedule. LIT has the hard cap — 1 billion, fixed — but it is at the very beginning of its unlock life, with only 25% of supply circulating and 500M LIT of insider allocation yet to begin vesting. A halving-model chain with a fixed cap and no cliff ahead of it faces only its own emission curve. LIT faces a supply event an order of magnitude larger than anything on this ledger, and no burn cadence observed so far comes close to offsetting it.

What to watch in the next 90 days

First, whether Lighter's burn becomes a cadence or stays a one-off — only one burn has ever executed, on Jul 10 2026, weeks after the end of the second quarter, so a comparable retirement in mid-October 2026 would establish quarterly rhythm. Second, whether the ecosystem reserve's staking releases accelerate toward the published yield target; a step up from the 0.10M LIT released on Jul 3 2026 toward the entitlement-implied 1.85M LIT per 90 days would multiply the sell side several times over. Third, exchange revenue itself, since the buyback is revenue-funded and the forward figure of 2.50M LIT scales directly with it — that figure is built on the post-integration run rate of the trailing month, not on the slower blended average of the full window. Fourth, the balance of the ecosystem reserve, which sits at 234.26M LIT and has no published release schedule. Fifth, and dominating all of them, the insider cliff on Dec 27 2026 — it falls just outside this forward window, so the next rebuild after it is the one that will show what 500M LIT of vesting does to this page.

Summary

The MrNasdog Pressure Framework reads Lighter's LIT as deflationary by structural buyback: 3.50M LIT bought back with trading-fee revenue against 0.10M LIT of new supply gives a trailing 90-day net of −1.36% and a forward reading of −0.94%, both on a circulating base of 250M LIT. The mechanism is genuine and the burn was verified on both supply surfaces at both ends of the window, but its shape matters: the circulating-supply figure held at exactly 250,000,000 all window and the burned LIT left Lighter's non-circulating ecosystem reserve, so neither the buying nor the burning shows up in a circulating-supply series — that is the whole of the 1.48 percentage point gap against our supply monitor's +0.12%. The key risk is that Lighter's burn is discretionary in timing rather than protocol-enforced, and that 500M LIT of team and investor supply begins vesting on Dec 27 2026 against a supply hard-capped at 1 billion LIT and only 25% circulating today.

MrNasdog Pressure Framework analysis of LIT, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 5 2026.

BTW Inflation Analysis · September 2026 · Supply growing, projected to keep growing

MrNasdog — Thu, 27 Aug 2026 02:45:43 +0000

Originally published at mrnasdog.com/research/btw/inflation by MrNasdog.

Bitway created no new BTW in the last 90 days and still put 708.1M BTW into the market, because the Bitway escrow released it: 200.0M on Jul 22 2026 and 508.1M on Aug 8 2026. Against that, Bitway runs no buyback, no burn and no lock — the buy side of the Pressure Framework ledger is zero on all four rows. The framework reads BTW at +26.15% net over the trailing window and +26.15% forward, against a supply-monitor reading of +23.87%. BTW's 10B supply is permanently capped and nothing can mint more, but only 2.71B of it is out — the escrow still holds 7.29B, and it opens by hand, not by calendar.

The verdict, in one paragraph

For the 90 days to Sep 5 2026, the MrNasdog Pressure Framework reads BTW at +26.15% net. Sell pressure is 708.1M BTW, buy pressure is 0 BTW, and the circulating base is 2.71B BTW. Our supply monitor reads the same window at +23.87% — a gap of 2.28 percentage points, well outside the half-point tolerance, so the BTW overview page ships a data-conflict chip. The reconciliation walk closed the gap rather than leaving it open: the monitor's circulating series sat frozen at 2,200,000,000 every single day from May 9 2026 to Aug 9 2026 and then restated in one step to 2,708,142,280 on Aug 11 2026, while the Bitway escrow contract actually stood at 8,000,000,000 for most of that period. The monitor is measuring a catch-up restatement off a stale base; the framework is measuring the escrow itself. BTW is best characterised as a hard-capped token that is inflationary by discretion — nothing is minted, and the float still grew by a quarter in a single quarter.

Sell pressure: where new BTW comes from

It does not come from minting. Sell #1, protocol inflation, is 0, and that is a measurement rather than an assumption: the BNB Chain BTW contract reported a total supply of 10,000,000,000 at the start of the window and 10,000,000,000 at the end, identical to the last decimal, and the deployed code contains no mint function at all. Bitway Ledger — the sovereign proof-of-stake chain on which BTW would be the gas and staking asset, and the only thing that could ever create a BTW emission — is still a roadmap item in Bitway's own documentation. There is no staking emission, no block reward and no issuance curve for the Bitway token.

All of BTW's sell pressure is Sell #2, vesting unlocks, at 708.1M BTW, and it comes out of a single readable escrow. Every undistributed BTW sits in one BNB Chain lockbox, and that lockbox fell from 8,000,000,000 to 7,291,857,720 across the window — a realised release of 708,142,280 BTW in exactly two events, 200,000,000 on Jul 22 2026 and 508,142,280 on Aug 8 2026. The figure is not an estimate drawn from an unlock tracker. Bitway's Ethereum deployment is the mirror image of the same escrow, wired through a cross-chain bridge, and its own supply counter moved by the identical amounts on the identical days, closing to zero residual at both ends of the window. Two independent readings on two chains, agreeing to the token. Because the escrow is readable, the framework books what actually left it rather than what a calendar says should have left it.

Sell #3, foundation and unscheduled unlocks, is 0 — not because there is nothing to watch, but because the escrow drawdown is already counted in Sell #2 and booking it twice would double the ledger. Sell #4, long-term locked or bankruptcy, is 0: BTW has no bankruptcy estate, no trustee schedule and no court-ordered distribution. That leaves one row carrying the whole page, which is unusual and worth stating plainly — BTW's inflation is not a protocol property at all. It is a distribution decision.

Buy pressure: where new BTW goes

Nowhere. All four buy rows measure zero, and each was tested rather than assumed. Buy #1, programmatic buyback, is 0: Bitway's own documentation sets out what BTW is for — product access, fee discounts, governance voting, and eventually securing Bitway Ledger — and never commits any revenue to repurchasing the token. There is no buyback contract, no buyback dashboard and no dated purchase disclosure.

Buy #2, protocol fee burn, is 0, and this row was checked on both surfaces because either one alone can lie. The BNB Chain dead address moved by 0.1113 BTW across 90 days — dust, not a programme — and the total-supply counter never fell by a single unit. The Ethereum deployment does show BTW being destroyed, twice, for large amounts; those are the bridge leg of the escrow release, and the same tokens reappear from the BNB Chain lockbox in the same minute. Treating that as a burn would have invented 708.1M BTW of buy pressure that does not exist and flipped an inflationary page deflationary. The escrow is a pass-through, not a sink.

Buy #3, foundation buy, is 0 — no Bitway entity has disclosed buying BTW on the open market, and no identified wallet was seen accumulating during the window. Buy #4, new long-term lock, is 0, and here the movement ran the wrong way: Bitway's own BTW staking vault fell from 6,987,022 BTW to 166,874 BTW, so roughly 6.8M BTW came back out of the lock rather than into it. The incentivised staking campaign that drove the August headlines takes deposits in stablecoins and pays its yield in a stablecoin plus points; it locks no BTW whatsoever. One further item belongs on this side of the ledger only as a warning: the Bitway points programme states that points can later be converted into BTW at a ratio still to be announced. That is a future claim on the escrow, not a purchase.

Foundation and overhang

Two team-controlled overhangs sit behind the BTW float, and both are large. The first is the escrow itself, holding 7,291,857,720 BTW — 73% of every BTW that will ever exist, refreshed against the chain daily. Inside it sit the Bitway team's 2,000,000,000 and the backers' 1,633,000,000, both behind a twelve-month cliff to Mar 2 2027, which falls outside both framework windows but is the single biggest dated event on BTW's horizon.

The second is the release recipient wallet, an ordinary externally-owned address that took delivery of the Aug 8 2026 release and has held all 508,142,280 BTW of it ever since. That is 19% of the entire counted float sitting in one wallet that held nothing at all before that day, and it has not moved a token in 28 days. It is worth being precise about what that does and does not mean: an unmoved balance is capacity, not cadence, so it carries no value of its own in the ledger. But the contrast with the earlier release is sharp — the 200,000,000 BTW sent to the same wallet on Jul 22 2026 was distributed onward within about half an hour, while the August tranche has simply sat. If either of these overhangs falls between refreshes, the outflow enters Sell #3 at the next refresh.

How BTW compares to other capped-supply escrow tokens

BTW belongs to the class of hard-capped tokens whose entire supply was minted at genesis and whose inflation is therefore a release schedule rather than an emission curve. That class behaves nothing like a mined chain. Bitcoin's issuance is written into consensus code and steps down on a halving no one can reschedule; its next-90-day supply growth is knowable to four decimal places years in advance. BTW's next 90 days depend on when a team decides to open a contract. The cap is real and binding — the Bitway token can never exceed 10,000,000,000 — but a cap constrains the destination, not the speed, and BTW is travelling toward that cap fast.

It also behaves differently from the exchange tokens it now shares a market-cap band with. Those run a quarterly buyback or a continuous fee burn that pulls supply out against whatever is unlocking, so their ledgers have two live sides and can net deflationary in a strong quarter. BTW has one live side. Every mechanism that would offset an unlock — buyback, burn, foundation purchase, protocol lock — measures exactly zero, and the only staking product in the ecosystem takes stablecoins rather than BTW. Among vesting-driven Layer 1 and appchain tokens, the usual reassurance is that the release schedule is at least predictable, so the market can price it in. BTW does not offer that either: the published calendar claims a 101.6M BTW tranche on the second of every month, and the escrow has never once moved on the second of a month. Apr 2, May 2, Jun 2, Jul 2 and Sep 2 2026 all passed with the escrow balance unchanged, while two large unscheduled releases landed on Jul 22 and Aug 8 2026. This is the rarer and more awkward profile: capped, uninflatable, and still growing its float by a quarter a quarter on a timetable the public calendar does not describe.

What to watch in the next 90 days

First, the escrow balance itself, currently 7,291,857,720 BTW — it is the only number that decides BTW's inflation, and it changes without notice. Second, the published tranche dates of Oct 2 2026, Nov 2 2026 and Dec 2 2026, each nominally 101.6M BTW: the interesting question is no longer whether the tranche is large but whether the calendar is honoured at all, since it has not been so far. Third, the 508,142,280 BTW sitting unmoved in the release recipient wallet — the moment it distributes, a fifth of the float changes hands. Fourth, the announcement of a conversion ratio for Bitway points into BTW, which would turn an undated liability into a dated one. Fifth, the team and backer cliff on Mar 2 2027 releasing 3,633,000,000 BTW: it is outside this window, but any move to accelerate, defer or restructure it would be the largest single supply event in BTW's history.

Summary

The MrNasdog Pressure Framework reads Bitway at +26.15% net supply growth over the trailing 90 days and projects the same rate forward, against a supply-monitor reading of +23.87% whose base was frozen for three months and restated in a single day. BTW is structurally incapable of inflation in the ordinary sense — the supply is hard-capped at 10,000,000,000, the contract has no mint function, and the counter did not move a unit all window — yet its tradable float grew by 708.1M BTW because a single readable escrow opened twice. The key risk is that the escrow still holds 7.29B BTW, releases on no schedule the chain has ever honoured, and faces no offsetting mechanism at all: Bitway runs no buyback, no burn, no foundation bid and no BTW lock. The ceiling is fixed and only 27% of the way reached, which makes BTW a token whose scarcity is guaranteed in the long run and entirely discretionary in the short one.

MrNasdog Pressure Framework analysis of BTW, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 5 2026.

WBT Inflation Analysis · September 2026 · Mixed flows, supply roughly steady

MrNasdog — Thu, 27 Aug 2026 02:45:39 +0000

Originally published at https://mrnasdog.com/research/wbt/inflation

WBT Inflation Analysis · September 2026 · Mixed flows, supply roughly steady

WhiteBIT Coin's contract cannot create a coin. The instruction that would mint a WBT is not in its code at all, the contract cannot be swapped for one that has it, and no WBT was created anywhere in the last 90 days. Against that, a weekly revenue-funded buyback destroyed 583,391 WBT in eleven rounds, while a single identified holder released 250,000 WBT on Aug 6 2026. The MrNasdog Pressure Framework reads WBT at −0.28% over the trailing 90 days and −0.49% over the next 90 — a coin that only ever shrinks, but slowly, against a 400,000,000 ceiling it can never reach again.

The verdict, in one paragraph

Against a circulating base of 117.96M WBT, the Pressure Framework books 0.25M WBT of sell pressure and 0.58M WBT of buy pressure over the trailing 90 days — a net of −0.28% — and projects −0.49% for the next 90 days, because the WhiteBIT burn is continuous while the one release that fired has no schedule behind it. The inflation monitor reads −0.22% for the same window, a gap of 0.06 percentage points, comfortably inside the framework's 0.5pp tolerance, so no data-conflict warning ships on the WBT overview. The two agree because the framework's two flows account for almost the whole of the monitor's move: 583,391 WBT destroyed less 250,000 WBT released is 333,391 WBT against a measured float change of 262,136 WBT, leaving a residual of 71,255 WBT — six hundredths of one percent of the float. The label for WhiteBIT Coin is an exchange token whose supply has only one direction, and it is down.

Sell pressure: where new WBT comes from

It does not come from issuance, and this is the part worth reading the code for rather than the documentation. WhiteBIT Coin's ERC-20 contract on Ethereum carries no mint function: the selector for it is simply absent from the 8,392 bytes of runtime code, calling it reverts, and the burn selector is the only supply instruction the contract exposes to the outside world. It is also not a proxy — all three of the standard implementation and admin storage slots read zero, and an opcode scan of the whole runtime finds no delegate call, no contract creation and no self-destruct, so there is no route by which a mint could be added later. Across the window the contract emitted zero transfers out of the zero address, which is the flow-side confirmation of the same fact. Whitechain, the WhiteBIT network on which WBT is the native gas coin, adds nothing either: its blocks are produced under proof of authority and carry no base-fee field at all, so validators are paid from transaction fees rather than from newly created WBT. Whitechain does not publish a native supply figure that can be read directly, so we keep this row watched rather than closed on that leg alone. Sell pressure from protocol inflation is 0, and on the contract leg it is 0 structurally rather than incidentally.

Vesting unlocks are also 0. The staged release that shaped WBT's early years has run out — the last dated cliff was Mar 13 2026, before this window opens, and the two release trackers that cover WhiteBIT Coin both now describe the schedule as finished. Nothing was due between Jun 9 2026 and Sep 7 2026, and nothing arrived. The one real sell-side figure on the page sits in the unscheduled row instead. We read the eleven largest WBT wallets on Ethereum at both ends of the window; ten of them did not move a single coin, and one sent 250,000 WBT out on Aug 6 2026, falling from 4,899,999 to 4,649,999. Traced transfer by transfer, that wallet took nothing in and sent exactly 250,000 out, matching its balance change to the last decimal. There is no bankruptcy estate, no trustee and no court-ordered distribution attached to WBT, so that row is empty as well.

Buy pressure: where new WBT goes

The whole buy side is one mechanism, and it is the reason WhiteBIT Coin shrinks. WhiteBIT spends an amount equal to 33% of its trading-fee income plus 5% of its other exchange income buying WBT on the open market and destroying it on arrival, with a stated long-term aim of taking the supply down toward 200,000,000 WBT. Eleven rounds fired inside this window — Jun 14, Jun 22, Jul 2, Jul 3, Jul 9, Jul 15, Jul 28, Aug 6, Aug 11, Aug 12 and Aug 24 of 2026 — averaging 7.06 days apart and ranging from 44,810 to 58,836 coins, for 583,391 WBT in total.

A burn claim is worth checking two ways, because a project can destroy coins by calling a function that lowers the supply count, or by sending them to an address nobody holds the key to, and watching only one of those surfaces returns a confident wrong answer. Both were read at both ends of the window. The dead addresses held 0 WBT at the start and 0 at the end, so WhiteBIT does not burn by transfer. The count of WBT in existence fell from 166,189,408 to 165,606,017 — a drop of 583,391, exactly the eleven rounds, to the last decimal. One surface moved and the other did not, so this is one flow, and it is counted once. WhiteBIT's own published burn table matches the chain round for round on every entry it displays. The wallet that does the buying held nothing at either end of the window, which means the coins are destroyed on receipt rather than quietly parked. There is no separate protocol fee burn to add, and booking the exchange's market purchases again as a treasury buy would count the same flow twice, so both of those rows read 0 by design. Nothing new was locked away either.

Foundation and overhang

175.65M WBT is held back and no longer sits on any published release calendar — the difference between the project's 293.61M aggregate supply and the 117.96M the market treats as circulating. Two wallets on Ethereum hold 60.00M and 30.00M of it and neither moved a coin in 90 days; the remainder sits in a handful of similarly static holdings. That is the real risk on WhiteBIT Coin: the supply cannot grow, but a large, unscheduled reserve can still reach the market whenever its holders decide, and the Aug 6 2026 release is proof that it sometimes does. Separately, 25,000,000 WBT sits at an address nobody holds the key to. WhiteBIT counts that line apart from the 81,393,982 WBT it reports as burned, and it is right to: those coins are still inside the count of WBT in existence, so they were moved rather than destroyed, and the framework does not credit them as buying. Both surfaces are re-read every rebuild. If the balance of any of those wallets falls between refreshes, the outflow enters the unscheduled sell row at the next refresh.

How WBT compares to other exchange tokens

WhiteBIT Coin belongs to the exchange-token class, where the buy side is funded by the venue's own revenue rather than by a protocol fee. Within that class the mechanisms differ in two ways that matter more than size. The first is rhythm: some exchange tokens burn quarterly in one large tranche, which makes any 90-day window either capture a burn or miss it entirely and produces a reading that swings between deeply deflationary and flat. WBT burns roughly weekly — eleven times in this window — so the reading is stable and a quarter boundary changes almost nothing.

The second is finality. A large share of exchange tokens are minted by contracts that retain an owner-gated mint function or sit behind an upgradeable proxy, which means the burn is a policy rather than a constraint — the supply cap holds only while the operator wants it to. WBT's contract has neither: no mint selector in the bytecode, no proxy, no upgrade path. Compared with capped proof-of-work chains, whose scarcity comes from a halving schedule that still issues new coins every block, WhiteBIT Coin issues nothing at all, and compared with fee-burning smart-contract platforms, whose burn scales with on-chain congestion, WBT's burn scales with the exchange's trading revenue. That makes the buy side a bet on the venue rather than on the network — a genuinely different exposure from a base-fee burn, and one that shrinks in coin terms as the price rises, because the programme is denominated in revenue rather than in coins.

What to watch in the next 90 days

Four things would move this reading. The weekly burn rhythm is the first: the last round landed on Aug 24 2026, so a gap running much past the 7.06-day average would say the fee revenue funding it has fallen, and the rounds are already smaller in coin terms as the price climbs. The second is the 175.65M WBT of unscheduled reserve, and specifically the two static wallets holding 60.00M and 30.00M — either one moving would dwarf everything else on this page. The third is the announced move of Whitechain from a standalone network to a layer-2 design built on the OP Stack, targeted for later in 2026 with no published date; WBT stays the gas coin through it, but a layer-2 fee model could introduce a protocol burn that does not exist today. The fourth is the 25,000,000 WBT parked at the burn address, which the framework still counts as existing supply and which would only become a genuine removal if the project destroyed it outright.

Summary

WhiteBIT Coin is one of the few tokens whose supply ceiling is a property of the code rather than a promise: there is no mint function in the contract, no proxy behind it, and no route to add one, so the 400,000,000 maximum can only ever be approached from above — a claim we hold to the contract leg, because the network's own supply figure is not published anywhere we can read it. The buy side is a weekly revenue-funded buyback that destroyed 583,391 WBT in this window and was verified on both burn surfaces and matched to the project's own published figures round for round. Against it, one identified holder released 250,000 WBT on Aug 6 2026, leaving a net of −0.28% over the trailing 90 days and a projected −0.49% ahead. The key risk is not issuance, which cannot happen, but concentration: 175.65M WBT sits outside the float on no schedule at all, and the size of the burn depends on how much the exchange keeps earning.

MrNasdog Pressure Framework analysis of WBT, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 7 2026.

FORM Inflation Analysis · September 2026 · Mixed flows, supply roughly steady

MrNasdog — Sun, 23 Aug 2026 23:33:48 +0000

Originally published at https://mrnasdog.com/research/form/inflation

FORM Inflation Analysis · September 2026 · Mixed flows, supply roughly steady

Four's FORM put 30,330 units of supply onto the market over the last 90 days and destroyed nothing at all, a net of +0.01% against a circulating supply of 381.87M FORM, while our own monitor reads -0.05% — a gap of 0.06 percentage points, well inside tolerance, so there is no data conflict to flag. FORM is the rebranded BinaryX token on BNB Chain, and the migration from the old coin is only 51.4% finished: 280.42M units still sit on the ancestor contract with no release calendar. The FORM contract has a 580,000,000 cap compiled in and no burn function of any kind, so supply here can only sit still or creep up.

The verdict, in one paragraph

Over the 90 days to Sep 4 2026 the FORM sell ledger totals 30,330 units — 9,783 minted and 20,547 released from one allocation wallet — and the buy ledger is zero, for a net of +0.01% against a circulating supply of 381,867,255 FORM. Our inflation monitor, measuring the same asset from the opposite direction, reads -0.05%; the gap of 0.06 percentage points is far inside the half-point tolerance, so no warning chip is shown on the overview. Getting that agreement required counting the right thing. The FORM contract's own supply counter rose 71,677 units across the window, which looks like inflation and is not: every one of those units was minted against an old BinaryX coin retired to a dead address, one for one, and the two readings match to the fourth decimal on two different contracts. Strip the swap out and Four is a near-static float with no downward lever and half its supply parked outside the token everyone reads.

Sell pressure: where new FORM comes from

Barely anywhere, and that is the finding. The FORM contract can only be minted through its migration entry point — the function that burns the ancestor BinaryX coin and issues FORM one for one — and the contract's minter registry is empty, so no other issuance path is live at all. Genuinely new units are therefore created on the ancestor contract, not on FORM, and reading that supply counter at both ends of the window gives 9,783 new units in 90 days: about 0.0026% of the float, or one unit for every thirty-nine thousand already outstanding. That is Sell #1, and it is about a third of the sell side.

The mint does not follow a curve. Ten readings across the window show two mints in June, one of five units in early August, one of 6,617 on Aug 15 2026, and long flat stretches in between. There is no published emission schedule, no halving and no staking subsidy behind it, which is why the forward column carries the same 9,783 rather than an invented rate — the quarter just measured is the only defensible guide to the next one. Sell #2, vesting unlocks, is zero: no vesting or escrow contract appears among the holders of either token, the project publishes no unlock calendar, and the two vesting aggregators that cover this market carry no FORM schedule at all. Sell #4 is zero because there is no bankruptcy estate and no trustee distribution attached to the asset.

Sell #3 is the rest of it, and it is the row that separates this build from a careless one. One allocation wallet — a Safe holding 75.92M units — stepped down three times by an identical 6,849.02 each time, once in each of the Jun 21 to Jun 29, Jul 21 to Jul 29 and Aug 13 to Aug 20 buckets, for 20,547 across the window. Thirteen interior readings resolve those steps individually, so this is a monthly firing rule rather than an average, and the forward column carries three more firings for the same 20,547. The temptation is to call that migration and book nothing, because the swap is running at the same time. It is not migration: the wallet holds 0.0000 FORM at both ends of the window, and the migration function mints FORM to whoever calls it, so those coins went to somebody else. The other seven allocation wallets did not move a single unit in 90 days.

Buy pressure: where new FORM goes

Nowhere. FORM cannot be destroyed, and that is a property of the code rather than a policy choice: the live contract exposes 42 functions and not one of them burns — no burn, no burnFrom, and no proxy or upgrade path through which one could be added. We checked the other surface a burn can hide on as well, because a token can be retired by transfer without the supply counter ever moving. The unspendable address holds 0.00059 FORM, up by four hundred-thousandths of a unit across the window — dust, not destruction — while the supply counter rose at all thirty-one interior readings. Both surfaces agree, so Buy #2 can only be zero.

Buy #1 is zero as well. The launchpad Four operates does offer a buyback-and-burn fee mode, but that mechanism buys the meme tokens created on the platform, not FORM itself, and no contract, wallet or disclosure points at open-market FORM purchases. There is no buyback destination to track. Buy #3 is zero because no Foundation, Labs or treasury entity has disclosed a FORM purchase programme and no entity wallet set is published to sweep — the two largest FORM holders are exchange custody wallets, which belong to depositors rather than to the project. Buy #4 is zero because no lockup or staking contract for FORM was deployed in the window, and none appears among the holders of either contract.

Foundation and overhang

The identified overhang for Four is the un-migrated BinaryX supply held by its allocation wallets: 277.90M units across eight addresses, the largest holding 75.92M, then 63.06M and 61.61M. Total un-migrated is 280.42M, so all but 2.52M of it sits in that set. These holdings are unscheduled by definition — no calendar is published for any of them — and only one has ever paid out, at 6,849 a month. Their balances are read directly from the ancestor contract at every rebuild rather than estimated, which is the only way to see them: a build that reads the FORM contract alone sees a 296.57M supply and misses 48.6% of the claim entirely. If any of those balances falls between refreshes, the outflow enters Sell #3 at the next refresh.

Two ceilings bound the whole thing. FORM's cap is a compiled constant of 580,000,000, and the BinaryX claim outstanding is 576,987,597 — all of it convertible one for one — which leaves just 3,012,403 units of headroom before the cap binds. The ancestor contract, however, carries its own maximum of 2.1B and still has one live minter, so the discipline is not that new units cannot be created; it is that beyond three million more of them, they could not be converted into FORM.

How FORM compares to other exchange-adjacent platform tokens

The obvious comparison class is platform tokens that fund a buy side out of platform revenue — the exchange and launchpad tokens that run quarterly buyback-and-burn programmes. Those assets shrink: revenue is converted into open-market purchases and the tokens are destroyed, so their supply counters fall and the framework reads them as deflationary. FORM sits in the same product category and behaves nothing like them, because it has no burn function to call. Four's launchpad generates fees, and the buyback-and-burn mode it offers is pointed at the tokens launched on it rather than at FORM, so the platform's success does not translate into FORM supply reduction by any mechanism currently in the code.

Against continuous-emission chains — the proof-of-stake networks that mint a staking subsidy every block — FORM looks unusually quiet. It has no consensus to pay for, no validator set and no emission curve, so its 9,783 units a quarter is not a rate at all, just a discretionary mint that happened four times. That makes FORM more like a fixed-supply token than an inflating one, but with a mint authority still live rather than renounced: the FORM owner can register a minter, and the ancestor contract already has one, so the quiet is a fact about the last 90 days rather than a guarantee about the next.

The comparison that matters most is with other mid-migration tokens. A rebrand that swaps one contract for another splits the supply story in two, and aggregators reconcile it inconsistently: the published circulating supply of 381.87M exceeds the FORM contract's entire minted supply of 296.57M, which only makes sense if the classified float already counts un-migrated BinaryX as the same asset. We measure the numerator on that same combined basis, which is why the swap nets to zero here and why the allocation outflows count even though they are denominated in the old coin. Read the FORM contract in isolation and the denominator falls 22.4% while the swap gets counted as issuance — the same quarter would print +0.024% instead of +0.01%, a difference produced entirely by which contract you point at.

What to watch in the next 90 days

First, the monthly firing from the paying allocation wallet. Three landed inside this window and three more are expected before Dec 4 2026; a change in the 6,849 quantum, or a second wallet starting to pay, is the single most likely thing to move this reading. Second, the migration rate itself. It has moved from nothing to 51.4% complete, and the pace over the last quarter was 71,677 units — at that speed the remaining 280.42M would take centuries, so any acceleration signals that large holders are preparing to do something with the balance.

Third, the ancestor mint. It fired four times in the window, most recently on Aug 15 2026 for 6,617 units, and with a 2.1B maximum and one live minter it is the only mechanism that can add real supply. Fourth, any announcement that gives FORM a buy side — a revenue-funded buyback, a staking lock, or a burn address the project commits to — none of which exists today, and the first of which would change the reading immediately. Fifth, the cap itself: once the BinaryX claim outstanding passes 580,000,000, further ancestor mints become unconvertible, and how the project resolves that is a governance question with no published answer.

Summary

The MrNasdog Pressure Framework reads Four (FORM) as effectively flat and one-directional by construction: 30,330 units reaching the market over 90 days, zero destroyed, a net of +0.01% of a 381.87M circulating supply, projected at the same +0.01% for the next 90 days. The mechanism underneath is a migration rather than an emission — FORM is minted only against BinaryX retired to a dead address, one for one, so the 71,677 units the FORM counter gained add nothing to the float. The key risk is custody, not issuance: 277.90M units sit un-migrated across eight allocation wallets with no release calendar, invisible to anyone reading the FORM contract alone, and only one of them has ever paid a unit out. The ceiling of 580,000,000 is real and nearly reached; the floor is that nothing in this token can ever remove a unit from the market.

MrNasdog Pressure Framework analysis of FORM, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Sep 5 2026.

VIRTUAL Inflation Analysis · August 2026 · Mixed flows, supply roughly steady

MrNasdog — Sun, 02 Aug 2026 08:07:14 +0000

Originally published at https://mrnasdog.com/research/virtual/inflation

VIRTUAL Inflation Analysis · August 2026 · Mixed flows, supply roughly steady

Virtuals Protocol's VIRTUAL cannot be created and cannot be destroyed. Over the 90 days to Aug 29 2026 the origin contract on Ethereum held supply at exactly 1,000,000,000 to the last decimal place, so the entire sell side of the ledger is one on-chain vesting escrow that released 1.40M VIRTUAL — against buy pressure of zero, because the famous Virtuals buyback-and-burn destroys each AI agent's own token and never VIRTUAL. On a circulating base of 658.4M VIRTUAL the Pressure Framework reads +0.21% net against our supply monitor's +0.49% — a gap of 0.27 percentage points, inside tolerance, so no monitor-gap flag ships. VIRTUAL is a hard-capped token whose last vesting escrow runs dry on Oct 24 2026.

The verdict, in one paragraph

For the 90-day window ending Aug 29 2026, the MrNasdog Pressure Framework reads VIRTUAL at +0.21% net: sell pressure of 1.40M VIRTUAL from a single vesting escrow, against buy pressure of zero, on a circulating base of 658.4M VIRTUAL. Our supply monitor reads +0.49% for the same window, so the gap is 0.27 percentage points — inside the half-point tolerance, and no flag is raised on this build. The two agree because the VIRTUAL ledger closes to the wei rather than approximately: total supply of 1,000,000,000 minus the ecosystem-treasury multisig at 340,652,950.21 minus the vesting escrow at 961,207.96 gives 658,385,841.83, which is the classified circulating figure exactly. Virtuals Protocol is best labelled flat by design — a fully issued cap with one nearly-spent escrow and no offsetting burn.

Sell pressure: where new VIRTUAL comes from

Sell #1, protocol inflation, is zero, and it is zero twice over. The origin VIRTUAL contract on Ethereum is an ERC-20 with a hard cap of 1,000,000,000 written into its constructor, and that cap is already fully issued — supply reads 1,000,000,000.000000000000000000 at both ends of the window, bit-identical, so the mint function cannot issue another unit even if someone called it. It could not be called anyway: the owner slot reads the zero address, meaning ownership was renounced and the only key that could mint VIRTUAL was thrown away. Virtuals Protocol therefore has no emission curve, no staking subsidy and no liquidity-mining programme to measure. The Base, Solana and Robinhood-chain versions of VIRTUAL do not change this. Base VIRTUAL is a bridge representation whose supply fell from 497,474,141 to 496,995,104 in lockstep with the Ethereum lockbox that backs it, the two differing by the same constant 11,020.21 at both ends; the Solana mint is issued by a cross-chain pool against VIRTUAL locked on Base. Every chain is a claim on the same fixed one billion, so the legs are never summed.

Sell #2, vesting unlocks, is 1.40M VIRTUAL — the only non-zero row on this page, and the one every data source gets wrong. Every major unlock tracker reports VIRTUAL as fully unlocked with no scheduled unlock in this window or the next. The chain says otherwise: an on-chain vesting escrow holding team and contributor allocations fell from 2,361,022.57 to 961,207.96 over the window, a realised release of 1,399,814.61 VIRTUAL, with nothing flowing back in. The escrow's own transfer log sums to the same figure month by month — 99,307 in June, 433,986 in July and 866,521 in August. The framework reads what actually left the contract rather than what a calendar entitles, and here that distinction reverses the answer entirely: a page built from the unlock trackers would have shown a flat 0.00% and missed the only supply reaching the market.

The August spike is not a trend — it is the mechanism ending. Three of the largest vesting streams inside that escrow, holding 2,500,000 VIRTUAL between them, terminated during this very window on Aug 7 2026, Aug 8 2026 and Aug 19 2026, and were drawn down in full. Projecting the trailing rate forward would forecast a vesting flow that no longer exists, so the forward figure is taken from the escrow's own remaining balance instead: 961,207.96 VIRTUAL, spread across exactly six live streams that end on Sep 9 2026, Oct 22 2026 and Oct 24 2026 or have already finished vesting and merely sit unclaimed. That gives a next-90-day sell figure of 0.96M VIRTUAL, or +0.15% of circulating — and after Oct 24 2026 the vesting mechanism is finished for good.

The remaining sell rows are zero, each for a checked reason. Sell #3, Foundation and unscheduled unlocks, is zero — no public evidence of release in window. That was not read off a calendar and not read off two end balances alone, because a multisig can show the same figure at both ends and still have carried a quarter's largest flow in between. The ecosystem-treasury multisig holding 340,652,950.21 VIRTUAL read identically at both ends of the window and identically again a full year earlier, on Aug 28 2025 — static for over a year, which is the framework's own disqualifying pattern for projecting a discretionary release. Sell #4, long-term locked or bankruptcy, is zero: VIRTUAL has no bankruptcy estate, no trustee and no court-ordered distribution.

Buy pressure: where new VIRTUAL goes

Buy #1, the programmatic buyback, is zero, and this is the single most misunderstood fact about Virtuals Protocol. The protocol does run a real, funded buyback-and-burn out of agent trading fees — but what it buys and burns is each AI agent's own token, never VIRTUAL. Every agent token on the launchpad is paired against VIRTUAL, and the 1% trading tax on agent trades is collected in VIRTUAL and split 70% to the agent creator and 30% to the Virtuals treasury. VIRTUAL is therefore the money being spent, not the asset being removed; the coins used to buy agent tokens are paid into that agent's liquidity pool and stay inside the tradable count. The destination test that decides this row is arithmetic rather than editorial: total supply minus circulating supply resolves exactly to the treasury multisig plus the vesting escrow and nothing else, so there is no VIRTUAL accumulation wallet anywhere in the system for bought-back coins to sit in.

Buy #2, protocol fee burn, is zero, and the framework checks a burn two ways because many projects burn by sending coins to an unspendable address without total supply ever moving. Both surfaces were read at both window ends. On the issuing chain the total-supply figure was bit-identical at 1,000,000,000; the unspendable dead address held 1,498.00 VIRTUAL at both ends and the zero address held 0; on Base the dead address moved by 0.12 VIRTUAL over ninety days, which is two hundred-millionths of a percent of supply. These two surfaces are genuinely independent here — with no burn function in the verified contract, total supply can never fall, so a transfer to a dead address would move one surface alone — and both read flat. Nothing was destroyed.

Buy #3, Foundation buy, is zero: no project entity has disclosed or been observed making open-market purchases of VIRTUAL. Buy #4, new long-term lock, is also zero, and for two reasons rather than one. Holders can lock VIRTUAL for up to two years to receive vote-escrowed veVIRTUAL, but the lock contracts were read at both ends and netted rather than counted gross: the main vote-escrow contract fell from 23,596,697.32 to 21,880,621.88, a net 1,716,075 unlocking, while the time-lock staking contract was flat at 23,560,304.38. Even a positive figure would not have counted: locked VIRTUAL sits inside the classified circulating supply, as the wei-exact identity above proves, so locking removes nothing from the float.

Foundation and overhang

VIRTUAL has exactly two team-controlled overhangs, and together they account for the entire non-circulating bucket. The first is the ecosystem-treasury multisig holding 340,652,950.21 VIRTUAL, the 35% ecosystem allocation, governed by DAO vote with a policy ceiling of 10% emission a year and no published release calendar. It is refreshed by chain read every day. It has not moved a coin in over a year. The second is the vesting escrow, holding 961,207.96 VIRTUAL undrawn at the close of the window, refreshed the same way and draining on a schedule that ends Oct 24 2026.

Two live governance items sit against the treasury but fired nothing in this window: a Sniper Defense and Yield Fund allocating 1% of supply, approved in July 2025, and a performance grant to the core contributor entity of up to 6% of supply that streams only if VIRTUAL trades at $10, $20 and $40 — thresholds far above the current price, so no milestone is in reach inside the next 90 days. If either overhang's balance falls between refreshes, the outflow enters Sell #3 at the next refresh.

How VIRTUAL compares to other launchpad and AI-agent tokens

Most launchpad tokens carry a supply problem VIRTUAL does not have. The standard design mints an ongoing emission to bootstrap liquidity or reward stakers, so the token faces a permanent headwind its buy side must out-run. VIRTUAL has no emission at all: the cap is reached, the mint key is burned, and the only new float is one contractual vesting escrow with a known end date. On a mechanism basis that puts VIRTUAL closer to a fully-vested fixed-supply ERC-20 than to a typical AI-agent or launchpad token — the supply question is a countdown rather than a curve.

Where VIRTUAL differs from exchange tokens with quarterly buybacks is on the other side of the ledger. An exchange token routes revenue into buying and destroying its own token, so revenue growth compounds into deflation; VIRTUAL routes its 1% agent trading tax into paying creators and the treasury, and its buyback destroys agent tokens instead. The result is a token whose economics are genuinely productive — every agent launch needs VIRTUAL as the pairing asset — but whose supply is flat by design rather than deflationary. More activity on Virtuals Protocol raises demand for VIRTUAL without ever reducing the number of coins that exist.

Against uncapped continuous-emission chains the contrast is sharper still. Those tokens can never reach a state where the sell side goes to zero, because issuance is written into consensus. VIRTUAL reaches that state in October 2026. Once the escrow empties, the only thing that can add float to VIRTUAL is a DAO vote to deploy the treasury — a discretionary decision with a published 10%-a-year ceiling, not a mechanical one.

What to watch in the next 90 days

The first watch item is Sep 9 2026, when a vesting stream holding roughly 25,000 VIRTUAL completes. The second and third are Oct 22 2026 and Oct 24 2026, when the last two streams — around 40,000 and 103,000 VIRTUAL — finish and the escrow's scheduled vesting ends permanently. The fourth is the unclaimed backlog: roughly 793,000 VIRTUAL inside the escrow has already finished vesting and is simply sitting unwithdrawn, so it can reach the market on any day its recipients choose, with no calendar to warn anyone. The fifth is the ecosystem-treasury multisig: it has been static for more than a year, and any governance vote that deploys part of it — the Sniper Defense fund or a new grant — would be the first genuine supply event VIRTUAL has had outside the escrow.

Summary

The MrNasdog Pressure Framework reads Virtuals Protocol (VIRTUAL) at +0.21% net supply over the 90 days to Aug 29 2026 and +0.15% projected forward, against a supply monitor reading of +0.49% — a gap of 0.27 percentage points, inside tolerance and unflagged. The structural mechanism is a hard cap of 1,000,000,000 that is already fully issued with the mint key renounced and no burn function in the contract, which means the token can neither grow nor shrink by protocol action; the only supply reaching the market is one vesting escrow that released 1.40M VIRTUAL and holds just 0.96M more. The key risk is not inflation but discretion: an ecosystem-treasury multisig holding 340.7M VIRTUAL, static for over a year, that a DAO vote could begin deploying at up to 10% a year. The ceiling is absolute — no VIRTUAL beyond one billion can ever exist.

MrNasdog Pressure Framework analysis of VIRTUAL, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 30 2026.

TRUMP Inflation Analysis · August 2026 · Supply growing, projected to keep growing

MrNasdog — Sun, 02 Aug 2026 08:06:40 +0000

Originally published at mrnasdog.com/research/trump/inflation by MrNasdog.

Official Trump cannot create a single new TRUMP — the Solana mint authority is renounced and the cap of 1,000,000,000 is permanent — and the supply still grew. Over the last 90 days the creator vesting escrow released 13.45M TRUMP, in two claims on Jul 25 2026 and Aug 22 2026, while the buy side of the Pressure Framework ledger read zero on all four rows: no buyback, no burn, no foundation purchase, no lock. That is +5.36% net over the trailing window against a supply-monitor reading of +5.62%, and +3.26% projected forward. The constraint that matters is not the cap. It is the 749.13M TRUMP — 74.9% of everything that will ever exist — still sitting in one escrow the creators draw from at will.

The verdict, in one paragraph

For the 90 days to Aug 30 2026, the MrNasdog Pressure Framework reads TRUMP at +5.36% net. Sell pressure is 13.45M TRUMP, buy pressure is 0 TRUMP, and the circulating base is 250.87M TRUMP. Our supply monitor reads the same window at +5.62% — a gap of 0.25 percentage points, comfortably inside the half-point tolerance, so the TRUMP overview page ships no data-conflict chip. The two readings agree because they are looking at the same object from two directions: the classified circulating figure for TRUMP is exactly the 1,000,000,000 cap minus the escrow balance, so when the escrow pays out, the float rises by the same number the framework books. Official Trump is best characterised as a hard-capped token that is inflationary by discretion — nothing is minted, nothing is burned, and the supply reaching the market is whatever the creators decide to claim this month.

Sell pressure: where new TRUMP comes from

Not from issuance, and this is a measured zero rather than a marketing claim. Sell #1, protocol inflation, is zero for Official Trump because the Solana mint at 6p6xgHyF7AeE6TZkSmFsko444wqoP15icUSqi2jfGiPN returns a null mint authority and a null freeze authority when read directly on-chain. On Solana a renounced mint authority cannot be restored by anyone, including the issuer — the ability to create TRUMP was destroyed, not switched off. The on-chain supply reads 999,999,021 against the 1,000,000,000 minted at launch on Jan 17 2025, so in nineteen months the total has moved by 979 TRUMP and only ever downward. There is no emission curve, no staking reward, no fee switch and no treasury mint to model, because Official Trump is a bare SPL token with no protocol behind it.

Sell #2, vesting unlocks, is 13.45M TRUMP and it is the entire ledger. The 800,000,000 creator allocation held by CIC Digital LLC and Fight Fight Fight LLC sits in a single readable escrow token account, whose authority is owned by the Magna vesting program. Because that escrow is readable, the Pressure Framework's rule is that a realised release beats a scheduled one, so this build read the escrow balance at both ends of the window rather than trusting the calendar. It fell from 762,585,959.66 to 749,131,651.71 — a realised outflow of 13,454,307.95 TRUMP in two batches: 10.84M across Jul 24 2026 and Jul 25 2026, split three ways into custody addresses, and 2.62M on Aug 22 2026. The window-start figure is exact, not interpolated: every signature on the escrow account was enumerated, and the balance did not move between May 11 2026 and Jul 24 2026.

The scheduled and realised figures are logged side by side because they disagree badly. Unlock trackers quote a linear drip of roughly 28M TRUMP a month — about 82M across this window, with one tracker naming an Aug 18 2026 event of 28,695,652 TRUMP. The escrow paid 13.45M, roughly a sixth of that, and paid it on none of the dates the calendars name. Booking the calendar would have invented sell pressure that never left the contract. The tokens that did leave genuinely reached the market: all three claim recipients read 0 TRUMP today, the July batch was forwarded within a day into custody addresses and then consolidated and dispersed to nothing, and the August batch drained to 784 TRUMP within six days. Nothing was re-locked and nothing is sitting still in a team wallet, so none of the released TRUMP qualifies as a parked overhang.

Sell #3, foundation and unscheduled unlocks, is zero, and Sell #4, long-term locked or bankruptcy, is zero as well. Nothing discretionary fired beyond the escrow claims already counted in Sell #2, and Official Trump has no foundation, no DAO treasury and no insolvency estate — there is no trustee schedule or court-ordered TRUMP distribution anywhere to book.

Buy pressure: where new TRUMP goes

Nowhere, and that is the sharpest structural fact about this token. All four buy rows read zero. Buy #1, programmatic buyback, is zero because there is no buyback contract and no buyback programme; the treasury vehicle announced in late 2025 to raise $200M and buy TRUMP on the open market has never closed and has never bought a coin, and the 90-day sweep found no purchase. Buy #3, foundation buy, is zero for the same reason: no entity behind Official Trump has disclosed an open-market TRUMP purchase, and no wallet was observed accumulating during the window.

Buy #2, protocol fee burn, is zero, and this build verified it on both surfaces rather than one, because a burn does not always show up in a supply reading. The dead-address read comes first: the Solana incinerator account holds 0 TRUMP and the system-program account holds 23 TRUMP. The supply read comes second: 999,999,021 TRUMP against 1,000,000,000 at launch, so at most 979 TRUMP have ever been destroyed by any route. That is a hard arithmetic bound rather than an assumption — any burn inside this window is capped below a thousandth of a percent of the float. On Solana the two surfaces are genuinely independent, since a burn call cuts total supply without crediting any address while a transfer to a dead address does the reverse, so both were checked separately and neither moved.

Buy #4, new long-term lock, is zero, and here the row is not merely empty but impossible by construction. Official Trump has no staking contract, no lock contract, no vault product and no governance escrow. There is no mechanism by which a TRUMP could be taken off the market even if someone wanted to. A token whose entire buy ledger is zero has no shock absorber: every coin the escrow releases is a coin the open market has to hold.

Foundation and overhang

The TRUMP overhang is the largest, in proportional terms, on any coin the Pressure Framework tracks. The dominant holding is the creator vesting escrow at 749,131,651.71 TRUMP — 74.9% of everything that will ever exist and about 3x the entire tradable float. It is refreshed from the chain on every rebuild. Crucially it is not schedule-limited in the way an ordinary cliff is: most of the escrow has already passed its vesting date, so what throttles the next release is a decision, not a calendar. In nineteen months the creators have claimed only 50.87M of the 800M allocation, which means the undrawn backlog has been accumulating rather than draining.

Two smaller overhangs are enumerated alongside it. The first is the set of claim-recipient and consolidation wallets that route each release onward; they hold 0 TRUMP, 0 TRUMP, 0 TRUMP and 784 TRUMP today and function as pure pass-through, which is why the framework treats a claim as supply reaching the market rather than supply moving between pockets. The second is the deployment allocation the issuers disclosed on Jul 15 2026: up to 96,000,000 TRUMP, 9.6% of total supply, earmarked for partnerships, acquisitions, entrepreneurship grants, a holder club and a mobile game. It carries no tranche dates and no tranche sizes, so it is an amount they could reach for rather than a dated plan, and it books at zero — but it is monitored on every rebuild. If the escrow balance, either recipient wallet, or that deployment allocation falls between refreshes, the outflow enters Sell #3 at the next refresh.

How TRUMP compares to other hard-capped tokens

Against halving-model chains with hard caps, Official Trump looks superficially stricter and is materially looser. A proof-of-work coin with a fixed cap still issues: its subsidy is positive, known years in advance, and shrinks on a published schedule that nobody can accelerate. TRUMP issues nothing at all, which sounds better, but its float grows from a stock of already-minted supply released at the discretion of two private companies. Predictability, not the cap, is the axis that separates them — a halving chain's next 90 days of new supply can be calculated to the coin, while TRUMP's next 90 days depend on whether a claim transaction is signed.

Against uncapped continuous-emission layer ones, the comparison inverts. Those chains mint every block and are genuinely inflationary at the protocol level, but the mechanism is transparent, gradual and usually partly absorbed by staking, which locks a large share of the float and takes it off the market. TRUMP has no staking to lock anything, so its releases land in full. And against exchange tokens with quarterly buybacks or fee burns, the gap is structural rather than one of degree: those tokens convert business revenue into permanent supply reduction, so a rising float is offset by a real bid. Official Trump earns fees for its issuers rather than for the token, and routes none of them back. On the sell side it resembles a venture-backed token unlock; on the buy side it resembles nothing at all, because the buy side does not exist.

What to watch in the next 90 days

First, the escrow balance itself, currently 749,131,651.71 TRUMP — it is the single number that determines this page, and every claim from it is visible on-chain the moment it happens. Second, the pace of the claims, which has tightened: the two most recent batches were Jul 25 2026 and Aug 22 2026, twenty-nine days apart, against gaps of a hundred days and seventy-five days earlier in the year. A third monthly claim would confirm a run rate; a skipped month would cut the forward number roughly in half. Third, the 96M TRUMP deployment allocation disclosed in Jul 2026 — the first dated tranche announcement moves it from a zero-value watch item into Sell #3. Fourth, the dormant treasury vehicle: a closed raise that actually buys TRUMP on the open market would be the first non-zero buy row this token has ever had. Fifth, whether anything is ever locked — a staking or club programme that escrows TRUMP, rather than merely rewarding holders with it, would change the ledger's shape rather than just its size.

Summary

The MrNasdog Pressure Framework reads Official Trump at +5.36% net supply growth over the 90 days to Aug 30 2026 and +3.26% over the next 90, driven entirely by vesting-escrow releases against a buy side of exactly zero. The structural mechanism is unusual: TRUMP is permanently capped at 1,000,000,000 with the mint authority destroyed, so no coin can ever be created, yet the float grows because three quarters of the supply sits in one escrow whose release pace is a private decision rather than a published schedule. The key risk is that nothing offsets it — no buyback, no burn, no staking, no lock — so every claim lands on the market in full. The ceiling is real and it is close in one sense and distant in another: TRUMP can never exceed 1,000,000,000, but the path there runs through 749.13M TRUMP still behind the escrow, most of it already vested and one signature from the open market.

MrNasdog Pressure Framework analysis of TRUMP, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 30 2026.

TIA Inflation Analysis · August 2026 · Supply growing, projected to keep growing

MrNasdog — Sun, 02 Aug 2026 08:06:07 +0000

Originally published at mrnasdog.com/research/tia/inflation

Celestia added roughly 37.6M TIA to the market over the last 90 days against a buy side of exactly zero, which puts the MrNasdog Pressure Framework at +3.91% net for the trailing quarter and +3.42% forward, against a supply-monitor reading of +4.14%. The striking part is where that supply comes from: Celestia's staking inflation is now only 2.33% a year after two protocol-level cuts, contributing just 6.62M TIA, while 31.01M TIA — five times as much — is old genesis supply still draining out of vesting. TIA has no maximum supply, no burn, and no buyback, so the only thing that changes this picture is the vesting calendar running out.

The verdict, in one paragraph

Over the last 90 days the MrNasdog Pressure Framework reads Celestia at +3.91% net: 37.63M TIA of sell pressure against zero buy pressure, on a circulating base of 961.72M TIA. The supply monitor reads the same window at +4.14% — a gap of 0.23 percentage points, comfortably inside the half-point tolerance, so this build ships no monitor-gap flag. Both readings agree because there is nothing subtle to disagree about: TIA is not burned, not bought back, and not locked away, so the counted supply and the framework's float move together. The forward quarter improves slightly, to +3.42%, but only because a vesting cohort expires on Oct 30 2026 — not because anything starts absorbing TIA. Celestia is structurally inflationary on unlock schedule, not on issuance, and that is the single most important sentence in this analysis.

Sell pressure: where new TIA comes from

Sell #1 — protocol inflation — is 6.62M TIA, and it is the row most likely to be mis-stated elsewhere. Celestia launched with 8% annual inflation decaying 10% a year; CIP-29 slowed that decay in 2025, and CIP-41 then halved the rate outright in the v6 "Matcha" upgrade. This build dated that activation on the chain rather than trusting the announcement: Celestia's yearly issuance allowance stepped from 53.76M TIA to 26.87M TIA in a single block on Nov 24 2025, an exact halving. Struck against the supply at the last mint anniversary, that allowance is a live rate of 2.33% a year — not the 6.48% the original schedule implied and not the 2.5% headline. Measured directly, the Celestia supply counter moved from 1,169,630,626 TIA to 1,176,250,506 TIA across the window, and that measured delta agrees with the issuance allowance to 0.009%.

Sell #2 — vesting unlocks — is 10.22M TIA, and this build read the escrow rather than an unlock tracker. Celestia's mainnet genesis file, parsed in full this session, carries 231 delayed-vesting accounts holding 140.16M TIA that all released on Oct 30 2024, plus 229 continuous-vesting accounts split across seven dated cohorts. Six of those cohorts are finished. Exactly one is still paying: 82.87M TIA across 20 accounts, releasing evenly at 113,516 TIA a day until Oct 30 2026. Because a Cosmos continuous-vesting account makes the vested portion spendable automatically, there is no claim transaction that can lag behind the calendar — scheduled and realised are the same number here by construction, and no unclaimed backlog can build up behind the schedule.

Sell #3 — foundation and unscheduled unlocks — is 20.80M TIA, the largest row in the ledger, and it exists because Celestia's published release rules are bigger than its on-chain locks. The project's own tokenomics states that the R&D and Ecosystem allocation releases 200.93M TIA continuously from Oct 30 2024 to Oct 30 2027 — 183,493 TIA a day — and that the Initial Core Contributors allocation releases 117.6M TIA over two years, or 161,096 TIA a day. The genesis census shows only 113,516 of that core-contributor rate is actually escrowed on-chain. The remaining 47,580 TIA a day sits in Foundation-administered accounts with no readable lock contract, which is precisely why it belongs in Sell #3 rather than Sell #2. Sell #4 — long-term locked or bankruptcy — is zero and structurally so: Celestia is a going concern with no estate and no trustee distributing TIA on a court schedule.

Buy pressure: where new TIA goes

Nowhere. All four buy rows are zero, and each was measured rather than assumed. Buy #1 — programmatic buyback — is zero because Celestia operates no buyback contract and no repurchase mandate; the Proof-of-Governance proposal that would fund open-market buying and burning out of data-availability revenue has been discussed for more than a year and has still never reached an on-chain vote. Buy #2 — protocol fee burn — is zero, checked on both of the surfaces a burn can appear on. There is no burn address and no destroy instruction on Celestia; transaction fees are paid out to stakers with a 2% community tax routed to the on-chain community pool, and the total supply counter rose monotonically at every sample and never fell. The decisive test is arithmetic rather than an absence of documentation: the measured 90-day supply delta equals the issuance allowance times elapsed time to 0.009%, which leaves no room in the counter for anything to have been destroyed.

Buy #3 — foundation buy — is zero for the window, though Celestia is one of the few projects where this row has ever fired. On Jul 24 2025 the Celestia Foundation purchased 43.45M TIA from Polychain Capital for $62.5M and reallocated it to new investors on a phased release that ran to Nov 14 2025. That is a single event thirteen months before this window opened, and Celestia has published nothing since to suggest it repeats, so this row records the last firing rather than a rate. Buy #4 — new long-term lock — is zero, and the window argues the other way: bonded TIA fell from 508.66M to 480.29M while unbonding supply rose from 16.35M to 39.68M. Stake was leaving the lock, not entering it.

Foundation and overhang

Celestia's team-controlled overhang is unusually large and only partly lit. The on-chain vesting escrow holds about 7.04M TIA still unvested across its 20 accounts, readable from the chain and dead on Oct 30 2026. The R&D and Ecosystem tranche has roughly 78.37M TIA left to release and runs a full year longer, to Oct 30 2027, with no lock contract published — it is tracked by the release rule and a bi-weekly walk rather than by a chain read. The un-escrowed core-contributor slice adds about 2.95M TIA on the same Oct 30 2026 end date. The on-chain community pool, governance-gated and spendable only by a passing vote, grew from 3.40M TIA to 3.53M TIA across the window. And the largest single item is a residual rather than a wallet: Celestia's own release rules imply far more TIA has technically unlocked than the market counts as circulating, a difference of roughly 126M TIA that needs no vesting event to reach the market. If any of these balances falls between refreshes, the outflow enters Sell #3 at the next refresh.

How TIA compares to other uncapped proof-of-stake L1s

Against the class it is usually grouped with — uncapped continuous-emission Layer 1s such as Solana, Cosmos Hub or Sui — Celestia now looks unusually restrained on the mechanism everyone measures. Its 2.33% annual issuance sits below most of the class after two protocol-level cuts, and the mint is time-indexed rather than block-indexed, which matters more than it sounds: Celestia's block interval roughly halved inside this very window, from about 6.09 seconds to about 2.85 seconds, and issuance did not move by a single token. On a chain that paid a fixed reward per block, that same acceleration would have doubled the emission. Celestia pays per unit of elapsed time, so it did not.

Where Celestia parts company with that class is the second tap. A mature L1 like Ethereum or Bitcoin has essentially finished distributing its genesis allocation, so issuance is the whole story and a burn or a halving can flip the sign. Celestia is still three years into a four-year distribution, and the vesting stream is five times larger than the issuance stream. That makes TIA structurally closer to a recently-launched token mid-unlock than to a settled monetary chain, and it means the honest comparison is not "Celestia versus Solana on inflation" but "Celestia versus its own calendar." It also explains why cutting inflation twice barely moved the reading: halving 6.62M TIA would save about 3.3M, while the vesting rows contribute 31.01M.

The third comparison is the one Celestia has not yet earned. Exchange tokens and revenue-sharing chains that run a programmatic buyback-and-burn out of real fee income can go deflationary while still issuing. Celestia has the design on paper — Proof-of-Governance would route data-availability revenue into buybacks and burns — but no vote, no contract, and no dead address exist today. Until one does, every comparison that treats TIA as a deflationary candidate is describing a proposal, not a mechanism.

What to watch in the next 90 days

The dated events are few and both fall in the same week. On Oct 30 2026 the last on-chain vesting cohort empties and the un-escrowed core-contributor slice ends with it, removing roughly 161,096 TIA a day of unlock pressure and leaving only the R&D and Ecosystem stream at 183,493 TIA a day through Oct 30 2027. On Oct 31 2026 the mint anniversary applies the 6.7% disinflation step, taking the rate from 2.33% to about 2.18% and the daily issuance from 73,554 TIA to roughly 70,326 TIA. Beyond those, three watch lines: any on-chain governance proposal after id 9, which is where a Proof-of-Governance vote or a fee-burn mechanism would first appear; the bonded-supply trend, which fell 28.37M TIA this quarter and would need to reverse hard before staking counted as absorption; and the roughly 126M TIA classification residual, which needs no vesting event to reach the market and would show up in Sell #3 the moment it moves.

Summary

The MrNasdog Pressure Framework reads Celestia at +3.91% net over the trailing 90 days and +3.42% forward, with the supply monitor agreeing at +4.14% and no data conflict to flag. The structural mechanism is vesting, not issuance: staking inflation has been cut twice to 2.33% and contributes only 6.62M TIA, while 31.01M TIA of genesis allocation drains out of schedules that mostly have no lock contract behind them. The key risk is that the largest of those streams, the R&D and Ecosystem tranche, runs a full year past the others to Oct 30 2027, and sits alongside a roughly 126M TIA unlocked-but-uncounted residual that could reach the market at any time. There is no ceiling to lean on either — TIA has no maximum supply, no burn and no buyback, so nothing in the protocol removes a single token.

MrNasdog Pressure Framework analysis of TIA, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 30 2026.

ZBCN Inflation Analysis · August 2026 · Mixed flows, supply roughly steady

MrNasdog — Tue, 21 Jul 2026 00:09:38 +0000

Originally published at https://mrnasdog.com/research/zbcn/inflation

ZBCN Inflation Analysis · August 2026 · Mixed flows, supply roughly steady

Zebec Network's ZBCN is a Solana payments token whose supply is finished: the SPL mint authority on the ZBCN mint reads null and cannot be restored by any vote or upgrade, the vesting calendar closed with a final unlock on Mar 16 2026, and the 99,998,774,146 ZBCN in circulation is now the entire on-chain supply with zero non-circulating headroom left. With issuance impossible, the whole Pressure Framework reading for ZBCN comes down to two internal flows in the 90 days to Aug 22 2026: the Zebec distribution wallet paid 588.3M ZBCN to market across eleven dated transfers, and Zebec's staking pools absorbed 847.1M ZBCN on balance into one-to-four-month locks. The framework reads −0.26% net supply pressure and −0.26% forward. Our supply monitor reads +2.05%, a gap of 2.31 percentage points, because its supply base stepped up in a single day on Aug 4 2026 and because both ZBCN flows move coins its float already counts.

The verdict, in one paragraph

Over the 90 days to Aug 22 2026 the framework reads ZBCN at −0.26% net supply pressure: 588.3M ZBCN reaching the market on the sell side against 847.1M ZBCN locked away on the buy side. Forward it projects the same −0.26%, since both mechanisms are running rather than dated events. Our supply monitor reads +2.05% for the same window, so the gap is 2.31 percentage points and the ZBCN overview carries a data-conflict flag. The gap is mechanical and has two parts. First, the monitor's supply base for ZBCN was pinned to the old fully-unlocked figure of about 97.95B every day from mid-May until it jumped to the full chain supply of about 100.0B on Aug 4 2026 and held there — a one-step catch-up by the classifier, not two billion new coins, which is impossible on a mint whose authority is destroyed. Second, ZBCN now has no non-circulating bucket at all, so both the distribution wallet and the Zebec staking pools sit inside the counted float and moving coins between them cannot shift the monitor's number in either direction. ZBCN is best labelled a fully-issued token whose float is redistributed, not expanded.

Sell pressure: where new ZBCN comes from

Nowhere — and for ZBCN that is provable rather than inferred. Sell #1, protocol inflation, is 0 because the ZBCN mint account on Solana, ZBCNpuD7YMXzTHB2fhGkGi78MNsHGLRXUhRewNRm9RU, returns a mint authority of null and a freeze authority of null. A null mint authority on an SPL token is irreversible: there is no owner to reinstate it, no proxy to upgrade and no governance path back. Zebec Network is a payments and payroll platform rather than a chain, so there is no block reward and no staking emission either. Sell #2, vesting unlocks, is 0 because the ZBCN release calendar has physically expired — the final scheduled unlock landed on Mar 16 2026, well before this window opened, and the vesting aggregators now publish ZBCN as fully unlocked at the same 99,998,774,146 the chain reports. The framework's own supply arithmetic confirms it from the other side: total supply minus circulating supply is 0, so there is nothing left in any locked bucket to release.

All of ZBCN's sell pressure therefore sits in Sell #3, at 588.3M ZBCN, and it is a drawdown of already-minted coins rather than issuance. The Zebec distribution wallet 71LxiE4PvxdZxLmtGcoKAJEWKofPqYw5Wdn6PSpXHodV was walked transfer by transfer this session, and eleven dated outflows fall inside the window: 15.0M on Jun 2 2026, 151.5M and 55.0M on Jun 15 2026, 58.8M on Jun 21 2026, 30.7M on Jun 25 2026, 30.0M on Jul 15 2026, 40.0M on Jul 20 2026, 25.0M on Jul 26 2026, 75.0M on Aug 15 2026, and 92.3M plus 15.0M on Aug 21 2026. Both payout routers the Zebec distribution wallet feeds end the window nearly empty against that 588.3M, so the coins passed through rather than resting, and left Zebec custody. Sell #4, long-term locked or bankruptcy, is 0: Zebec Network is a going concern with no estate and no trustee, and stakes reaching the end of their term are already netted inside the buy side, so counting them here would count them twice.

Buy pressure: where new ZBCN goes

Buy #4, new long-term lock, carries 847.1M ZBCN and is the largest single number on the ZBCN ledger. Zebec staking runs through the on-chain program zSTKzGLiN6T6EVzhBiL6sjULXMahDavAS2p4R62afGv, and the check that mattered was refusing to read only the obvious vault. The program owns 35,449 accounts, none of them token accounts, which proves stakes are pooled rather than individually vaulted — so every ZBCN pool the program controls was enumerated instead. Four carry balance, and they did not move together: the headline pool grew from 3,721.2M to 4,678.4M, a second pool drained from 358.2M to 228.7M, a third fell slightly and a fourth grew from almost nothing to 27.2M. Together they went from 4,099.9M to 4,947.0M, a net absorption of 847.1M ZBCN. Reading only the headline pool would have reported 957.3M and overstated the entire ZBCN buy side by 13%. The lock is genuine: Zebec staking terms are fixed one-to-four-month lock-ups paying 8% to 15%, early exit is not possible, and the per-wallet cap is 5,000,000 ZBCN, so those coins cannot reach the market for the term.

Buy #1, the programmatic buyback, is 0 — opaque rather than absent. Zebec Network genuinely runs a revenue-funded ZBCN buyback, financed by payroll processing, Zebec Card fees and partner contracts and consolidated quarterly, but it publishes no on-chain address, no 2026 quantum, and part of the acquired position is held with an outside institutional custodian rather than on Solana. Three candidate accumulation wallets were tested by portfolio breadth this session and all three were rejected: their authorities hold 618, 220 and 102 unrelated tokens, which is custodial behaviour, and the 220-token one settles a fixed weekly beat against a single counterparty. With nothing measurable, nothing is booked. Buy #2, the protocol fee burn, is 0 because the Zebec DAO's ZIP-4 proposal paused the ZBCN burn in early 2024 and kept the buyback running instead, so bought coins are held rather than destroyed — and the chain agrees with the vote, since roughly 1.23M ZBCN have ever been burned against the 100B cap, about 0.001%, none of it in this window. Buy #3, foundation buy, is 0 because no purchase programme exists separately from that same buyback; booking one would double-count it.

Foundation and overhang

ZBCN has no unscheduled-unlock pool left, because there is no non-circulating supply at all — total and circulating are the same number. What remains is wallet overhang, and it is large. The Zebec cold reserve CZMwajZAkdtPtDC3EfPokkzWmmoQo6jmZJPzDXG3DHR3 holds 5,500,000,100 ZBCN and is demonstrably live: on Aug 21 2026 exactly 500,000,000 ZBCN was traced same-day from that reserve, through a router, through the feeder wallet GXD2FnXi718y9tPUd6CW1CW6khZ14DGtQc5cBpYkjm5J, and into the distribution wallet — which is why the distribution wallet ended the window at 889.1M ZBCN despite paying out 588.3M. A second identified project wallet, H8Hr964ApEP3ie1rwRTT7wkSrgvUqJQb8oNAKspkDDfR, holds 7,318,217,587 ZBCN, about 7.3% of all ZBCN, and has not moved since Sep 10 2025. Finally, the buyback accumulation destination is an overhang of unknown size, since Zebec has never published the address and part of it sits off-chain. Every one of these balances is re-read on each rebuild, and the undisclosed one is chased through Zebec's own published statements. If any of them falls between checks, the outflow enters Sell #3 at the next check.

How ZBCN compares to other fully-issued payment tokens

ZBCN belongs to a small class: tokens that have finished issuing entirely. Most tokens the framework tracks still have an engine running — an uncapped Layer 1 minting a block reward every few seconds, a monthly investor cliff stepping onto the market for another year, or a staking curve paying rewards out of new supply. ZBCN has none of those. Its mint authority is destroyed at the SPL level, which is a stronger guarantee than a hard cap written into a smart contract, because a cap can sometimes be raised by an upgradeable proxy while a null mint authority cannot be undone at all. That puts ZBCN closer to a fair-launch fixed-supply token than to a typical venture-backed payments token, even though ZBCN did have a seed round, a private round and a four-year vesting schedule — the difference is only that the schedule has now run out.

Where ZBCN differs from exchange tokens with quarterly buybacks is the destination of the bought coins. An exchange token that buys back and sends the coins to a burn address genuinely shrinks its float, and both the framework and any supply monitor will see it. Zebec's ZIP-4 vote deliberately went the other way: the buyback continues but the burn is paused, so acquired ZBCN accumulates in a treasury rather than disappearing. That is a treasury decision with a real trade-off — it preserves optionality and funds development, but it means the ZBCN buyback removes nothing permanently and could in principle be reversed. Against tokens whose deflation comes from a base-fee burn, ZBCN also has no fee sink at all, because it is not a gas token on Solana.

The closest structural analogue is a token whose entire supply is issued and whose float is governed by lock-ups rather than issuance. For ZBCN the read then turns on one comparison: whether the staking pools absorb faster than the distribution wallet pays out. Over this window they did, by 258.8M ZBCN, which is why the framework reads slightly negative rather than slightly positive. But a one-to-four-month lock is short, and it rolls: the 4,947.0M ZBCN currently staked matures continuously, so this row can flip to the sell side within a quarter if new staking slows while maturities continue — which is exactly what one of the four pools did during this window.

What to watch in the next 90 days

First, the Zebec distribution wallet, which ended the window at 889.1M ZBCN after its Aug 21 2026 refill: the refill is the single most important new fact on this page, because it restarted a reserve pipeline that had been idle since Mar 17 2026, and it means the sell row is no longer capped by an emptying wallet. Second, the Zebec cold reserve at 5.5B ZBCN — it has now released 1.0B on Apr 27 2026 and 500.0M on Aug 21 2026, and a third release would make it a pattern rather than a pair of events. Third, the four Zebec staking pools: net absorption of 847.1M ZBCN is the only thing holding the reading negative, and because the lock terms are one to four months, a slowdown in new stakes shows up as a reversal within weeks. Fourth, the ZIP-4 burn pause — the Zebec DAO has said it will review reinstating the ZBCN burn, and any reinstatement would move real buyback volume from an invisible treasury into a measurable Buy #2. Fifth, the dormant 7.32B ZBCN project wallet, silent since Sep 10 2025, which is the largest single overhang on the page.

Summary

ZBCN is a fully-issued token: the Zebec Network mint authority on Solana is destroyed, vesting closed on Mar 16 2026, and circulating supply now equals total supply exactly, so not one new ZBCN can enter the market by any mechanism. What remains is redistribution, and over the 90 days to Aug 22 2026 the redistribution ran slightly in holders' favour: 588.3M ZBCN out of the Zebec distribution wallet against 847.1M ZBCN into Zebec staking locks, for −0.26% net and −0.26% forward. The key risk is that neither side is structural — the staking lock runs only one to four months and rolls continuously, while the distribution wallet was just refilled with 500.0M ZBCN from a 5.5B cold reserve, so the balance between them can invert inside a single quarter. The ceiling, by contrast, is absolute: 100,000,000,000 ZBCN, already reached, and permanently unmovable.

MrNasdog Pressure Framework analysis of ZBCN, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 22 2026.

XTZ Inflation Analysis · August 2026 · Supply growing, projected to keep growing

MrNasdog — Tue, 21 Jul 2026 00:06:21 +0000

Originally published at https://mrnasdog.com/research/tezos/inflation

XTZ Inflation Analysis · August 2026 · Supply growing, projected to keep growing

Tezos minted 8,218,269 XTZ of staking rewards over the last 90 days under adaptive issuance — a mechanism that recomputes the chain's own yearly issuance rate every cycle from how much XTZ is staked — and cut that rate from 3.195% to 2.970% a year while doing it. Against that mint, only 59,329 XTZ was destroyed, and the largest part of the burn was not fees at all but 30,000 XTZ of forfeited Etherlink rollup dispute bonds. The MrNasdog Pressure Framework reads Tezos at +0.75% net over the trailing quarter and +0.74% forward, against a supply-monitor reading of +0.76%. XTZ has no maximum supply and no buyback of any kind.

The verdict, in one paragraph

Over the last 90 days the MrNasdog Pressure Framework reads Tezos at +0.75% net: 8,222,857 XTZ of new supply against 59,329 XTZ destroyed, on a circulating base of 1,094,741,523 XTZ. The supply monitor reads the same window at +0.76%, a gap of 0.02 percentage points — comfortably inside the half-point tolerance, so no monitor-gap flag is raised. That agreement is structural rather than corroborating: both readings ultimately measure the same circulating counter, and the framework's contribution here is the decomposition, not the total. Two things only the decomposition surfaces are the 30,000 XTZ burned by lost rollup bonds and the 16,391,567 XTZ that flowed into staking and removed nothing at all. Tezos is structurally inflationary with a self-damping rate: the more XTZ that gets staked, the less the protocol issues, and the staked share is still climbing.

Sell pressure: where new XTZ comes from

Sell #1 — protocol inflation — is the entire new-supply story for Tezos, because the chain has exactly one issuance path. New XTZ exists only as baking, attesting and data-availability rewards, minted under adaptive issuance, and there is no maximum supply to run into. Adaptive issuance is unusual enough to be worth stating plainly: the protocol looks at the fraction of supply that is staked, compares it to a roughly 50% target, and moves its own yearly issuance rate inside a fixed band accordingly. This build read that rate straight off the node at both ends of the window — 3.195% a year on May 31 2026 and 2.970% on Aug 29 2026 — and it fell because the staked share of Tezos rose to 30.8%. What actually shipped in the ledger is not either of those rates but the chain's own mint counter, which moved 8,218,269 XTZ across the 90 days. Annualised, that realised figure is 3.01%, sitting inside the band the two rate reads bracket — a clean cross-check between the published parameter and the measured flow.

A protocol upgrade landed inside this window, so the framework tested it rather than assumed it. Ushuaia, the twenty-first Tezos upgrade, activated on Jun 30 2026 at block 13,857,889. Comparing protocol constants either side of the switch shows every monetary field unchanged — the same six-second block target, the same 14,400-block cycle — and the upgrade's actual content was a fifteenfold rise in data-availability bandwidth, dynamic attestation for that layer, rollup governance, and liquid staking shipped to testnet only. No issuance parameter moved, so the trailing quarter is not a blend of two mechanisms and needs no re-basing. The measured block interval was 6.027 seconds against a six-second target, meaning a nominal calculation would over-state the mint by 0.45%; because the shipped figure is the realised counter, that measurement stays a cross-check and is never applied twice.

Sell #2 — vesting unlocks — is zero and permanently so: the four-year vesting schedule that released the Tezos Foundation and early-team allocations finished on Sep 17 2022, the contracts it ran through are empty, and the allocation is physically spent. Sell #3 — foundation and unscheduled unlocks — is also zero, proven on the transfer log rather than on a balance comparison: this build swept every transaction touching all fourteen identified Tezos Foundation wallets across the window, and thirteen of them had no transactions at all while the fourteenth had a single 8.54 XTZ payment coming in. Sell #4 — long-term locked or bankruptcy — is zero structurally, since Tezos has no bankruptcy estate and no trustee distributing XTZ on a court schedule. The one extra sell row, Sell #5, is a genuine oddity of this chain: 19,981,067 XTZ of 2017 fundraiser allocations have still never been claimed, they can be claimed at any time with no expiry, and one claim of 4,588 XTZ landed on Jul 28 2026.

Buy pressure: where new XTZ goes

Buy #1 — programmatic buyback — is zero, and it is zero by design rather than by neglect. Transaction fees on Tezos are baker income, not funding for a repurchase contract, and no governance proposal exists to change that. Buy #3 — foundation buy — is zero on the same wallet sweep that cleared Sell #3: no identified Foundation address bought XTZ on the open market during the quarter, though the four Foundation bakers did grow about 1,010,350 XTZ from reward accrual, which is not buying. Buy #4 — new long-term lock — is zero despite staking absorbing 16,391,567 XTZ across the window, because unstaking on Tezos takes days rather than years and staked XTZ is still counted as circulating supply. That is custody, not a lock, and booking it as buy pressure would invent an offset roughly twice the size of the entire quarterly mint.

The burn is where Tezos gets interesting, and it had to be checked on both surfaces. The dead-address route is nearly empty: the public burn address held 283 XTZ at the open and 458 XTZ at the close, a rise that rounds to nothing and belongs to NFT burns rather than to supply policy. The protocol counters are where the real destruction happens, and they moved 59,329 XTZ in total. Splitting that by time rather than by differencing surfaces gives three distinct mechanisms. Buy #2 — protocol fee burn — is 17,992 XTZ, the fixed price-per-byte charge that storing data on Tezos destroys, running at roughly 200 XTZ a day. Buy #5 is 30,000 XTZ of forfeited rollup bonds: Etherlink operators post a 10,000 XTZ bond to publish, lose it if a dispute proves them wrong, and half of each lost bond is burned — six disputes were lost inside this window. Buy #6 is 11,337 XTZ sent to an unspendable address, every single transfer of it originating from the protocol's own liquidity-baking exchange contract. The ranking is the finding: lost dispute bonds out-burned the entire fee mechanism by roughly five to three, on a channel that appears in no tokenomics page and on no calendar.

Foundation and overhang

Three overhangs are tracked on Tezos. The Tezos Foundation runs four bakers holding 32,800,555 XTZ between them, and ten labelled delegator wallets holding a further 50,312,181 XTZ — about 83,112,736 XTZ in total, close to 7.6% of the float, on no published release plan. Those balances are read straight off the chain and re-checked on every rebuild. Alongside them sits the unclaimed 2017 fundraiser pool of 19,981,067 XTZ, which is not team-controlled but is real supply sitting outside the tradable float, claimable at any time by the original participants with no expiry and no schedule. Over the last twelve months that pool released eleven claims totalling 82,913 XTZ — regular enough in occurrence to project forward, erratic enough in size that the trailing-year average is the honest number. There is no buyback accumulation wallet to watch, because there is no buyback. If any of these balances falls between refreshes, the outflow enters Sell #3 — or Sell #5 for the fundraiser pool — at the next refresh.

How XTZ compares to other liquid proof-of-stake chains

The obvious comparison class is uncapped continuous-emission layer ones, and Tezos sits at the quiet end of it. Chains with a flat per-block subsidy mint the same amount whatever the network does, which is why several of them run materially above 4% a year with nothing dampening them. Tezos is one of the few production chains whose issuance rate is a live function of participation rather than a constant: the rate genuinely fell from 3.195% to 2.970% inside a single quarter, without a vote, purely because more XTZ was staked. That is a structurally different shape from a halving-model chain with a hard cap, where the schedule is fixed years in advance and participation changes nothing, and a different shape again from an exchange token running quarterly buybacks, where the buy side is a discretionary corporate decision that can be paused.

Where Tezos looks weaker than its peers is the offset. Layer ones that added a base-fee burn destroy a meaningful fraction of what they mint, and in strong quarters some of them tip net-negative outright. Tezos returns roughly one XTZ for every 457 it creates through ordinary chain use, so the burn is not a supply lever in any practical sense — it is a rounding line. The absence of any buyback means there is no discretionary counterweight either: the only thing that moves the net figure meaningfully is the mint, and the only thing that moves the mint is the staked ratio. That makes Tezos unusually predictable to model and unusually dependent on one variable. The other structural note worth carrying across the comparison class is that the biggest single burn of the quarter came from a rollup dispute mechanism, which is a channel that will exist on every chain hosting bonded rollup operators and is currently classified by nobody.

What to watch in the next 90 days

The first watch line is the staked ratio, currently 30.8%. Adaptive issuance targets roughly 50%, so every further point of staking pulls the yearly rate down and pulls the framework's forward reading with it — this is the single variable that moves the number. The second is the governance vote on protocol-native liquid staking, shipped behind a flag in the Ushuaia upgrade of Jun 30 2026 and switched off pending approval: it would remove no supply directly, but it would likely raise the staked share and therefore lower issuance. The third is the Etherlink rollup dispute channel, which burned 30,000 XTZ across six lost bonds in this window and carries forward at zero because nothing schedules it — a repeat would be a genuine surprise on the buy side. The fourth is the unclaimed fundraiser pool of 19,981,067 XTZ, where a single large claim can arrive on any day with no warning. The fifth is the Tezos Foundation's 83,112,736 XTZ, which has not moved a coin outward this quarter and would change the reading materially if it started to.

Summary

The MrNasdog Pressure Framework reads Tezos at +0.75% net over the trailing 90 days and +0.74% forward, matching the supply monitor to within 0.02 percentage points. The structural mechanism is adaptive issuance: staking rewards are the only way a new XTZ can exist, and the protocol lowers its own yearly rate as the staked share rises — from 3.195% to 2.970% in this quarter alone. The key risk is that there is no offset worth the name: no buyback exists, the fee burn returns about one XTZ in every 457 minted, and the largest destruction of the quarter came from six forfeited rollup dispute bonds that nothing schedules and no tracker classifies. And the ceiling is that there is no ceiling — Tezos has no maximum supply, so the only brake on issuance is the staked ratio itself.

MrNasdog Pressure Framework analysis of XTZ, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 30 2026.

ZRO Inflation Analysis · August 2026 · Supply growing, projected to keep growing

MrNasdog — Tue, 21 Jul 2026 00:04:41 +0000

Originally published at https://mrnasdog.com/research/zro/inflation

ZRO Inflation Analysis · August 2026 · Supply growing, projected to keep growing

LayerZero released roughly 77.13M ZRO from its vesting calendar over the last 90 days against a buy side of 0.43M, which puts the MrNasdog Pressure Framework at +21.71% net for the trailing quarter and +21.71% forward, against a supply-monitor reading of +40.50%. The striking part is that not one ZRO was created: the token is capped at 1,000,000,000, and we proved it by reading the supply on all seven networks LayerZero deploys ZRO to at both ends of the window, where it summed to exactly that figure twice. LayerZero's dilution is a calendar, not a printer — and the calendar runs to June 2027.

The verdict, in one paragraph

Over the last 90 days the MrNasdog Pressure Framework reads LayerZero at +21.71% net: 77.13M ZRO of sell pressure against 0.43M of buy pressure, on a circulating base of 353.31M ZRO. The supply monitor reads the same window at +40.50% — a gap of 18.79 percentage points, far outside the half-point tolerance, so this build ships a monitor-gap flag. The gap has a single dated cause and it is not a chain flow: the counted circulating figure sat near 252.3M ZRO every day from Jun 1 2026 to Jul 7 2026, jumped 100.9M in one day on Jul 8 2026, and has been flat at 353.31M every day since, straight through the Jul 20 and Aug 20 unlocks. That is a classifier restating what it counts, catching up on ZRO unlocks that had already happened in earlier quarters. LayerZero is capped by protocol and diluting by contract, and that is the single most important sentence on this page.

Sell pressure: where new ZRO comes from

Sell #1 — protocol inflation — is 0, and it is the row worth understanding before any other. ZRO is an omnichain fungible token, one asset deployed at a single address on Ethereum, Arbitrum, BNB Chain, Base, Optimism, Polygon and Avalanche. Moving ZRO between two of those networks destroys it on the sending side and recreates it on the receiving side, so the seven-network total never changes. Read at both window ends, the legs summed to 1,000,000,000.000000 on Jun 1 2026 and 1,000,000,000.000000 on Aug 30 2026, with four legs growing and three shrinking and the deltas netting to zero. Landing on the cap twice is also the proof that the legs are not mirrors of each other — a mirrored deployment would sum above the cap. LayerZero has no block reward, no staking yield and no mint path, and this is what that looks like measured rather than asserted.

Sell #2 — vesting unlocks — is the whole page: 77.13M ZRO. LayerZero's locked allocations release in 24 equal monthly steps, and three of those steps fell inside the window, on Jun 20 2026, Jul 20 2026 and Aug 20 2026. Each step is 25.71M ZRO, and it splits three ways with each part exactly one twenty-fourth of its bucket: 13.42M to strategic partners out of 322M, 10.63M to core contributors out of 255M, and 1.67M from the 40M pot LayerZero repurchased from early backers. Nothing on-chain enforces any of it. Every large allocation holder was re-classified for this build by the implementation behind its address, and they are custody multisigs — no vesting logic, no cliff function, no release call. The tokens already sit in their owners' wallets and the date only lifts a contractual restriction. That divergence is worth naming: measured movement out of those custody wallets was 17.73M ZRO over the same 90 days, so 59.39M of released ZRO is being held rather than sold. It is released supply either way, which is why the calendar governs this row.

Sell #3 — Foundation and unscheduled unlocks — is 0, because nothing fired. The two largest custody multisigs on the Ethereum leg held 106.06M and 69.55M ZRO, and both were identical to the token at both window ends. Sell #4 — long-term locked or bankruptcy — is 0: there is no estate and no trustee releasing ZRO on a court schedule. The 40M ZRO once tied to a collapsed trading firm's claim was bought back before the token launched and folded into the strategic-partner allocation, where it now vests on the ordinary LayerZero calendar already counted in Sell #2.

Buy pressure: where new ZRO goes

Buy #1 — the programmatic buyback — is 0.43M ZRO, and it is real but small. LayerZero directs all of the bridge protocol's fee revenue into open-market ZRO purchases, and we read the destination rather than the announcement: the accumulation wallet at 0x6ac55E733dFF03A54251670df0667774E8f7D28f went from 1,765,166.57 to 2,191,568.53 ZRO across the window. The published monthly purchases of 124,574, 141,557 and 160,271 ZRO for May, June and July 2026 reproduce that climb, and the lifetime total of 2,191,453 ZRO matches the live balance to about a hundred tokens — which is the proof that nothing has ever left. The bought ZRO is parked, not destroyed, so it is off the market only while the wallet stays shut.

Buy #2 — the protocol fee burn — is 0, and this is where the widely-repeated version of the LayerZero story is simply wrong. The protocol fee that would fund a ZRO burn is switched off. An unchangeable contract forces a holder referendum every six months, and all four have resolved off: Dec 27 2024, Jun 27 2025, Dec 27 2025 and Jun 27 2026. The fourth of those fell inside this window. We verified the row on both surfaces the framework requires rather than on the vote alone: the seven-network total is unchanged at the cap, and the dead-address balances across all seven legs rose 0.06 ZRO in 90 days. The next referendum lands in late December 2026, outside the forward window. Buy #3, a discretionary LayerZero Foundation purchase, is 0 — the last firings were a 50M repurchase in Sep 2025 and a one-off $10M open-market buy in Nov 2025, with no published plan since. Buy #4, a new long-term lock, is 0: there is no ZRO staking contract yet, because staking arrives only with LayerZero's own network.

Foundation and overhang

About 646.69M ZRO — two thirds of everything that exists — sits outside the counted float, and the Pressure Framework watches it in four pieces. The first is the pair of custody multisigs at 0x8F6449530606A9EFddaC42e05612427dDeBA449C and 0x744Dbc48D11415ec5cB2f78609DeA5E1E738DA24, holding 106.06M and 69.55M ZRO, both flat to the token across the window and read from the chain at each rebuild. The second is the investor cluster: eleven wallets holding exactly 8.55M ZRO each, every one unchanged except a single wallet that fell from 8.55M to 4.10M. The third is the buyback accumulation wallet at 2.19M ZRO, which has never had an outflow. The fourth is the largest and the least defined: of the 646.69M, only about 246.80M is still on the published release calendar, and the remainder has no schedule at all. If any of these balances falls between refreshes, the outflow enters Sell #3 at the next refresh.

How ZRO compares to other omnichain and messaging-layer tokens

ZRO belongs to the small class of hard-capped infrastructure tokens whose supply cannot grow but whose float can — the opposite shape from an uncapped Layer 1. A proof-of-stake chain with continuous issuance typically prints two to five percent a year and has finished its unlock calendar; ZRO prints nothing and is releasing roughly 21.71% of its float every quarter. Judged on issuance alone, LayerZero is one of the tightest assets we track. Judged on supply reaching the market, it is among the loosest. Both statements are true, and only the second one moves a price.

Against the exchange tokens that run quarterly buyback-and-burn, the contrast is sharper still. Those coins retire a slice of supply every quarter and their vesting is long finished, so their net reading is negative by construction. LayerZero has the machinery for the same outcome — a fee switch written into an unchangeable contract, and a revenue-funded buyback that is already running — but the switch has been voted off four times and the buyback parks its ZRO instead of destroying it. A buyback that accumulates removes supply only for as long as the wallet stays shut; a burn removes it permanently. That distinction is the entire difference between a Buy #1 row and a Buy #2 row, and LayerZero currently has only the former.

Against other omnichain tokens, LayerZero is unusually clean in one respect that matters for measurement. Many multi-chain assets lock collateral on a home chain and mint mirrors elsewhere, so adding up the networks double-counts the supply. ZRO burns on send and mints on receive, which is why its seven legs sum to the cap exactly rather than exceeding it — the arithmetic itself tells you which kind of bridge you are looking at, and on LayerZero it says there is no hidden supply anywhere.

What to watch in the next 90 days

Three dated releases carry the forward window and each is 25.71M ZRO: Sep 20 2026, Oct 20 2026 and Nov 20 2026. The launch of LayerZero's own network, guided to autumn 2026 with no committed date, is the single event that could change the shape of this page — it would turn ZRO into a stake and gas token and open a Buy #4 row for the first time. The aggregated trading engine LayerZero announced on Aug 25 2026 would route 75% of post-rebate venue fees into buying and burning ZRO, which is the first genuine burn path the token has ever had, but it is guided only to "later this year" and contributes nothing until it ships. The fifth fee-switch referendum falls in late December 2026, just past this window; a first "on" result would move Buy #2 off zero. And the counted circulating figure has been pinned at 353,313,325 ZRO since Jul 8 2026 — the next restatement, whenever it lands, will move the monitor sharply again without any ZRO changing hands.

Summary

The MrNasdog Pressure Framework reads LayerZero at +21.71% net over the last 90 days and +21.71% forward, driven entirely by a vesting calendar that released 77.13M ZRO in three monthly steps against a 0.43M buyback that accumulates rather than burns. The mechanism is a hard cap of 1,000,000,000 ZRO, verified across all seven omnichain deployments at both ends of the window, paired with a release schedule that is contractual rather than on-chain — the allocations sit in custody multisigs with no lock logic, so an unlock date lifts a restriction rather than moving a token. The key risk is the 646.69M ZRO still outside the float, most of which has no published schedule, and the fact that 59.39M of already-released supply is being held rather than sold. The ceiling is the one piece of genuine comfort here: LayerZero can never issue a 1,000,000,001st ZRO, and the calendar that is diluting it ends in June 2027.

MrNasdog Pressure Framework analysis of ZRO, Metric 1 — Inflation. Data + explanation only. Not financial advice. Updated Aug 30 2026.