TL;DR
- Venice runs programmatic VVV buy and burns on every new subscription, scaled by tier: $2 for Pro, $5 for Pro+, $10 for Max.
- This is additive to ongoing discretionary burns (180k VVV / ~$1.35M removed from circulation since November). Both run in parallel.
- Every burn is verifiable at venice.ai/token/burns with onchain transaction links.
- Part of Venice's strategy to make VVV a net deflationary asset.
What's New
Venice has built an engine that automatically buys and burns VVV based on specific qualifying events.
Every new Venice subscription triggers an automatic VVV buy and burn, scaled by tier:
| Tier | Burn per new subscription |
|---|---|
| Pro | $2 |
| Pro+ | $5 |
| Max | $10 |
The transaction executes and shows up on the burn tracker within seconds.
This is part of Venice's strategy to make VVV a net deflationary asset, where the amount of VVV burned exceeds new emissions over time.
How the Burn Works
The buy and burn cycle:
- Earn: Venice generates revenue from subscriptions and API usage
- Buy: A portion of that revenue triggers USDC-to-VVV swaps on the open market
- Burn: The purchased VVV is transferred to a burn address, permanently removing it from supply
Discretionary burns (existing)
Venice has been conducting discretionary burns since November 2025: periodic buybacks funded by a portion of revenue. To date, 180k VVV (~$1.35M) has been removed from circulation through discretionary burns.
In March 2025, Venice also burned approximately one-third of the total VVV supply consisting of unclaimed airdrop tokens, the single largest burn event in the token's history.
Programmatic burns
Programmatic burns add an automatic channel on top of what already exists. When a qualifying event occurs, the engine immediately buys VVV and burns it. Both discretionary and programmatic burns run in parallel.
Every new subscription is a qualifying event. The burn amount scales with the subscription tier:
| Tier | Burn per new subscription |
|---|---|
| Pro | $2 |
| Pro+ | $5 |
| Max | $10 |
Total burns to date
Including the airdrop burn and all subsequent burns, Venice has burned over 33.7 million VVV, approximately 42.9% of the original 100 million token supply. For live totals, visit venice.ai/token/burns.
The Burn Tracker
The burn tracker makes the entire process transparent and verifiable:
- Real-time transaction feed with onchain verification links for each burn
- Period statistics: daily, weekly, monthly, and yearly burn totals
- Volume and rate charts showing historical burn activity
- Live VVV supply breakdown: burned, staked, locked for DIEM, circulating
- Supply-over-time chart showing how VVV supply composition has shifted
The Venice Token Economy
For readers new to VVV and DIEM, here is a short overview of how they fit together.
VVV is Venice's native token on Base and the capital asset of the ecosystem. Holders can:
- Stake VVV to earn a share of token emissions (or when staking 100 VVV get access to Pro)
- Lock staked VVV to mint DIEM, tokens that generate $1/day of AI inference credit, perpetually
DIEM turns AI compute into an ownable, tradeable asset. It works across Venice's full model catalogue, is composable onchain as an ERC-20 on Base, and can be used by developers, AI agents, and DeFi protocols.
Burns reduce VVV supply permanently. DIEM minting locks sVVV for as long as the DIEM exists (unlock your sVVV by burning the DIEM). Emissions decline on a fixed schedule.
Together, these forces work toward making VVV a net deflationary asset.
What's Next
As the programmatic burn engine matures, Venice plans to continue increasing the per-event burn amounts and adding more qualifying triggers beyond new subscriptions. The long-term goal is to migrate most discretionary burns into the programmatic engine, making the deflationary mechanism fully automatic and transparent.
Track every burn in real-time: venice.ai/token/burns
Questions or feedback: join us on Discord
Learn more:
- VVV overview
- DIEM overview
- Token dashboard (live supply, staking, DIEM data)
- DIEM Technical Breakdown
- VeniceStats (community-maintained, not managed by Venice)

Venice.ai