Private AI inference (text, image, code) with a token-gated API: revenue funds VVV buybacks and burns; staked VVV mints DIEM, which grants daily API credit.
Target user
Privacy-conscious consumers and developers who want unfiltered model access.
Product loop
Subscriptions/API revenue → buyback-and-burn → stake VVV → mint DIEM → $1/day API credit (DIEM must itself be staked).
Token / revenue model
VVV + DIEM on Base. 33.75M VVV verifiably burned at the null address; ~$100K/month discretionary buybacks per third-party tracking; emissions stepping down to 3M/year per announced schedule.
Distribution
Privacy/censorship-resistance brand plus exchange listings (Upbit, Crypto.com, Coinbase).
Verifiable strengths
Burns and buybacks are externally observable onchain — the most credible token-economic loop among the projects reviewed.
Evidence gaps & weaknesses
User counts are self-reported and the circulating "3M+" figure runs ahead of Venice's own "2M+" marketing page; burn percentage uses the most favorable denominator.
Whitespace it reveals
Venice proves onchain numbers build trust — but no one applies that standard to usage metrics across the ecosystem.
“33.75M VVV burned, with an ongoing revenue-funded buy-and-burn.”
The null address (0x000...000) holds 33,749,674.7 VVV onchain, matching Venice's dashboard. The March 2025 burn of ~32.6M unclaimed airdrop tokens was independently reported by The Block. Third-party tracker VeniceStats corroborates ongoing buybacks of roughly $100K/month.
The 42.05% figure is internally consistent but uses Venice's post-burn total supply (80.27M) as denominator. Against the 100M genesis supply the burn is ~33.75%; against Basescan's max supply field (~114M) it is ~29.6%. The burn is real; the percentage depends on a denominator choice that is the most favorable available framing.
Methodology note: Methodology-limited: percentage claims require a stated denominator to be comparable across projects.
Venice's own marketing page stated "over 2 million users" as of June 2026, and its changelog announced the 2M milestone in late January 2026. Independent traffic data (Semrush: ~12.07M visits in April 2026, 74% direct) is consistent with an active base in the low millions but does not verify a 3M registered-user figure. The 3M+ claim, as circulated, runs ahead of Venice's own primary source.
Methodology note: Disputed because the claim conflicts with the claimant's own current primary source, not because usage is small.
“Major exchange listings including Upbit and Crypto.com.”
Upbit listed VVV with KRW/BTC/USDT pairs on May 12, 2026 (multiple independent outlets). Crypto.com App listing the same day. VVV also trades on Coinbase.
Venice announced a stepped schedule (May 1: 6M→5M; June 1: 5M→4M; July 1: 4M→3M), the fourth cut in under a year. The announcement is confirmed; execution of the final step postdates this check and is not yet verifiable.
“DIEM: each Diem provides $1/day of API credit, mintable only by locking staked VVV.”
Mechanism confirmed in Venice's documentation and observable onchain (DIEM ERC-20 on Base, ~37K supply). One caveat: the $1/day credit requires the DIEM itself to be staked (min 0.1), a condition the marketing shorthand omits.
Represent Venice? If any label here is wrong, we want to know. Send evidence to corrections@basis.watch. Substantiated corrections are applied, versioned, and logged publicly — see the correction process.