VVV automatic burns: what it means for token governance

TL;DR: Each new subscription now triggers a programmatic VVV buy and burn of $2, $5, or $10 depending on tier, alongside discretionary burns that have removed 180,000 VVV since November and more than 33.7 million VVV overall, according to Venice. The mechanics matter because automated supply changes create governance, transparency, and verification requirements that look more like identity and lifecycle controls than simple tokenomics.

NHIMG editorial — based on content published by Venice: automatic VVV buy-and-burn mechanics and token supply tracking

By the numbers:

• Every new Venice subscription triggers an automatic VVV buy and burn scaled by tier: $2 for Pro, $5 for Pro+, and $10 for Max.
• To date, 180k VVV, or about $1.35M, has been removed from circulation through discretionary burns since November 2025.
• Including the airdrop burn and all subsequent burns, Venice says it has burned over 33.7 million VVV, about 42.9% of the original 100 million token supply.

Questions worth separating out

Q: How should teams govern event-triggered supply changes in onchain systems?

A: Teams should treat event-triggered supply changes as controlled lifecycle events, not as simple automation.

Q: Why do parallel manual and automated controls create governance risk?

A: Parallel controls create governance risk because they can produce the same outcome through different paths, which makes reconciliation and accountability harder.

Q: What do organisations get wrong about transparency in automated token systems?

A: Organisations often treat transparency as a dashboard problem when it is really an evidence problem.

Practitioner guidance

• Map every trigger to one authoritative control path Document which subscription events qualify for a burn, how tier values are assigned, and which system is the source of truth when programmatic and discretionary burns both exist.
• Reconcile automatic burns against onchain evidence Verify that each burn tracker entry matches a transaction hash, token amount, and timestamp so reporting cannot drift from execution.
• Separate governance for discretionary and event-driven actions Treat manual buybacks and programmatic burns as distinct controls with separate approval logic, audit trails, and exception handling.

What's in the full article

Venice's full post covers the operational detail this post intentionally leaves for the source:

• The exact burn tracker behaviour, including how live transaction links are displayed for each burn event.
• The full subscription tier mapping and how burn amounts are scaled across Pro, Pro+, and Max.
• The supply dashboard views for burned, staked, locked, and circulating VVV, which matter once you need to reconcile totals.
• The DIEM relationship and how locked VVV, emissions, and burns interact across the broader token economy.

👉 Read Venice’s overview of automatic VVV buy-and-burn mechanics →

VVV automatic burns: what it means for token governance?

Explore further

View Full Forum →  |  NHI Foundation Course →