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

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

Venice is doing almost everything a token holder could ask of an issuer — it has cut the VVV mint four times in five months, from 6M a year to 2.5M, and it spends real revenue buying VVV on the open market and destroying it — and the Pressure Framework still reads Venice Token at +2.79% over the trailing 90 days and +3.26% over the next 90. The reason is a mechanism Venice does not control on a quarterly clock: a straight-line team lockup on Base that released 1.27M VVV into the tradable float this quarter, more than the 0.74M the mint added and nearly double the 0.68M that the burn and Venice's own wallets took back out between them. VVV has no supply ceiling at all.

The verdict, in one paragraph

Against a circulating base of 47.9M VVV, the framework books 2.011M VVV of sell pressure and 0.675M VVV of buy pressure over the trailing 90 days — a net of +2.79% — and projects +3.26% for the next 90 days. The inflation monitor reads +1.95% for the same window, a gap of 0.84 percentage points, over the framework's 0.5pp tolerance and therefore shipping with a monitor-gap warning on the overview page. That gap has only two terms and no residual: 0.92pp is the monitor's market-derived supply estimate running below the chain's own account state, working against 0.08pp of base convention, because the monitor divides its supply change by the 90-day-old float while the framework divides by today's. The framework's own side of that comparison is not an estimate: the four booked flows sum to 1,335,346 VVV against a float change read independently from chain state at both ends of 1,335,346 — a residual of 0.005 VVV. The forward column being higher than the trailing one is worth naming, because it is the opposite of what the schedule alone would do. The mint is falling and the burn is rising; what changes is the buy side losing a one-off. The trailing quarter contained 554,179 VVV of sporadic treasury absorption and the forward quarter projects only the 53,494 that recurs. On mechanism alone the reading would fall from +3.94% to +3.37%. The label for Venice Token is an uncapped token with a shrinking mint and an unfinished unlock.

Sell pressure: where new VVV comes from

Some of it really is minted. VVV is a plain ERC-20 on Base whose verified source is fifteen lines long: it has exactly one state-changing supply function, mint, callable only by the owner, and no burn function at all. The framework measured the emission by counting the mints rather than by trusting a published rate — a complete sweep of the token's own transfer log across all 3,888,000 blocks in the window returned 241,299 separate mint transactions creating 785,411 VVV, and the count of VVV in existence rose from 114.03M to 114.81M by exactly that amount, to the eighth decimal. The measured rate reproduces Venice's published ladder without being told it: 10,960 VVV a day before Jul 2 2026 (a 4M-a-year pace), 8,219 a day through Sep 3 2026 (3M a year), and 6,849 a day since (2.5M a year). Of every minted VVV, 94.7% lands in the staking contract, which sits inside the tradable float; the remaining 5.3% goes to a Venice wallet that does not. Sell #1, protocol inflation, books the in-float share at 0.74M VVV.

The larger leg is Sell #2, vesting unlocks, at 1.27M VVV — and none of it is newly created. Venice's team and contributor allocation sits in two readable on-chain lock contracts, which held 3.36M VVV when the window opened and 2.10M when it closed. The framework books the realised outflow rather than the calendar entitlement, because the contracts are readable: 1,266,348 VVV stopped being locked and became tradable, about 14,070 a day, in a straight line with no cliff. Monthly draws on the larger contract read 400,583, 395,200 and 398,363 — a metronome. At that pace the remaining 2.10M runs out around Jan 2027, which lines up with a 24-month stream opened at the token's launch. Sell #3, Foundation and unscheduled unlocks, is 0: every Venice-side wallet grew across the window rather than releasing. Sell #4, long-term locked or bankruptcy, is 0 as well — Venice Token has no bankruptcy estate, no trustee and no court-ordered distribution attached to it.

Buy pressure: where new VVV goes

Buy #1, the programmatic buyback, is 0.12M VVV and it is the row worth reading closely. Venice earns revenue from subscriptions and inference credits, swaps a share of it into VVV on the open market, and sends what it buys to a dead wallet. That wallet took in 120,982 VVV over the window, and the framework closed the figure two ways: the dead wallet's balance moved from 33,749,883 to 33,870,865, and a complete sweep of every transfer into it returned 217,245 events summing to the same number to within a hundred-millionth of a token. Of those, 54,078 VVV arrived in 217,242 tiny transfers routed straight out of a trading pool — the per-purchase burn — and 66,904 VVV arrived in three large lots from an executor wallet that bought every one of its 73,810 VVV through an on-chain settlement contract. The pace is climbing steeply: 204 VVV a day in the first month of the window, 1,430 in the second, 1,929 in the third and 3,535 in the final week, after Venice added a burn on credit purchases on Jul 17 2026 on top of the per-subscription burns running since Apr 26 2026. Cumulative destruction now stands at 33.87M VVV.

Buy #2, protocol fee burn, is 0 — not because nothing is destroyed, but because everything destroyed already runs through Buy #1 and must be counted once. This is the case where reading one surface alone would have produced the wrong page: both were read at both ends and they disagree in sign, because the count of VVV in existence rose while the dead wallet also rose. A build watching total supply alone would have booked Venice Token's entire buy side at zero. Buy #3, Foundation buy, is 0, because none of the movement into Venice's wallets is an open-market purchase. Buy #4, new long-term lock, is 0 by mechanism: 35.32M VVV sits staked, up from 33.53M, but staked VVV is already inside the 47.9M float this reading divides by, so staking removes nothing — and locking it to mint Venice's compute-credit token does not change that, because the locked balance never leaves the same contract. That leaves a fifth row the canonical four do not cover. Venice's three wallets pulled a net 554,179 VVV out of the float across the window and sold none of it back: 264,804 arrived from one holder, 200,000 and 75,000 in round transfers into a second, 40,493 through a settlement contract in 250 fills, and 75,093 as pool fee income. It is not demand and it is not booked as a purchase, but the coins left the float this page measures, so the framework carries it as a tracked removal — which is the only structure under which the ledger closes against the chain. Only the recurring fee legs, 53,494 over 90 days, are carried forward; the round transfers have no schedule behind them.

Foundation and overhang

The overhang on Venice Token is large, and it is fully enumerated because the arithmetic forced it to be. Five addresses make up the entire non-circulating side: a Venice treasury holding 20.76M VVV, a second Venice wallet holding 8.64M, a third holding 1.57M, and the two lock contracts holding 1.80M and 0.30M. Those five sum to 33.07M VVV against a classified non-circulating bucket of 33.07M — a residual of 572 VVV, or 0.0017%. That closure is what proves the staking contract is not in the bucket, and therefore that staked VVV is tradable float. All three Venice wallets are read from the chain at every rebuild and all three grew across the window; if any of those balances falls between refreshes by more than the schedule accounts for, that outflow enters Sell #3 at the next refresh. The lock contracts are different — their fall is the schedule, already booked in Sell #2.

How VVV compares to other uncapped emission tokens

Venice Token belongs to a class that has become common in AI and infrastructure crypto: a token with no supply ceiling at all, whose issuer manages dilution by discretion rather than by code. A halving-model chain like Bitcoin mints on a clock nobody can move; Venice Token's mint is a single owner-only function, cut four times in five months by announcement. That cuts both ways — it is why the emission reads 4M a year at the start of the window and 2.5M at the end, and why the same authority could raise it again without asking anyone.

The closer comparison is to exchange tokens that run revenue-funded buybacks and burns. Those chains offset issuance with a demand-linked removal that scales with usage, and their readings can go genuinely negative. Venice Token has exactly that shape of mechanism, and unlike many projects it is visibly firing — 120,982 VVV destroyed in 90 days, accelerating month over month. The problem is scale relative to the other side of the ledger. For the burn to flip this page's sign, Venice would need to destroy more than 1.76M VVV a quarter, roughly twelve times the current rate and about 3.7% of circulating supply. At today's price that is on the order of $45M a quarter of revenue routed to burns, against a company that disclosed a $100M annualised revenue run rate in Aug 2026. The mechanism exists and is growing; it is not yet the size of the problem.

The third comparison is the one that actually explains the number: a recently-launched token still working through its team vest, where the unlock is the dominant term — 1.27M against a 0.74M mint. The difference from a typical vest is that this one is continuous rather than cliff-based, so there is no single dated unlock to trade around, and it is the one part of the supply picture Venice cannot cut by announcement.

What to watch in the next 90 days

First, Oct 1 2026, when the mint falls from 2.5M to 2M VVV a year — the last announced step, and the one already priced into the +3.26% forward reading. Second, the burn rate, which is the only line that could change the sign of this page: it ran at 3,535 VVV a day in the final week of the window against a 1,639-a-day average since Jul 17 2026, and the dead wallet is read at every rebuild, so any acceleration shows up immediately. Third, the two lock contracts, which drain to roughly Jan 2027 at the current pace and are the single largest term in the sell column; new streams have been opened into the smaller of the two before, so the balance can go up as well as down. Fourth, Venice's three treasury wallets at 20.76M, 8.64M and 1.57M VVV — together 30.97M, about 65% of circulating supply, with a spender rather than a schedule behind them. Fifth, the mint function itself: it is owner-controlled with no ceiling in the contract, so the emission ladder is a policy, not a constraint.

Summary

The MrNasdog Pressure Framework reads Venice Token at +2.79% over the trailing 90 days and +3.26% projected forward: supply growing, projected to keep growing. The structural mechanism is a split one — a mint that is being actively retired, from 6M VVV a year to 2M by Oct 1 2026, sitting alongside a team lockup that released 1.27M VVV into the float this quarter and keeps doing so until roughly Jan 2027. The key risk is that the one offsetting force, a revenue-funded open-market buy-and-burn, is real and accelerating but still an order of magnitude too small: 120,982 VVV destroyed against 2.011M arriving, with the rest of the trailing offset coming from a one-off 554,179 VVV of treasury absorption that does not repeat. And there is no ceiling to fall back on — the contract has one owner-only mint function, no cap and no burn function, so the count of VVV in existence can only rise, and the discipline that is currently shrinking it is a decision rather than a rule.

---

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