Venice Token (VVV)

$VVV three drive pattern https://t.co/Yejc7uqXYn

Why I am bearish on VVV (Venice Token), Retail get out.

The contract is remarkably minimal — the protocol-specific logic is approximately 15 lines of Solidity, inheriting the remainder from the Solmate ERC20 and Owned libraries. This minimalism is a deliberate design pattern and results in a small attack surface from a code-correctness perspective. However, it concentrates substantial economic power in a single externally owned account, creating systemic centralization risk that is not mitigated at the contract level.

The most significant is the presence of an uncapped, ungoverned `mint()` function callable exclusively by the owner with no delay, no supply ceiling, and no on-chain safeguards. Combined with the single-owner access model and the confirmed post-deployment use of this function — the live supply of approximately 113,973,199 VVV already exceeds the deployed initial supply of 100,000,000 VVV by 13.97% — the risk profile for token holders is materially elevated.

The `mint()` function allows the co

Erik Voorhees explains how Venice's dual token model actually works

"You can stake 100 VVV to get pro access to Venice. We take a bunch of our revenue, buy the token, and burn it"

"We want to take that to its extreme and try to buy every last token we can and burn it all"

"You lock up VVV to mint DIEM. Each DIEM you hold gives you $1/day to use on any AI model you want"

"We built it so AI agents could hold an asset and get marginally free inference"

"It changes the economic calculation. We thought that'd be an interesting design space to explore"