Diem

What is Diem?

Diem is an ERC-20 token on Base that turns Venice.ai inference capacity into a transferable on-chain asset: one staked DIEM entitles the holder to $1 of renewing daily Venice API credit, rather than a balance that is consumed once and disappears.

The protocol’s stated problem is the unpredictability and permissioning of conventional AI API billing, where developers and agents rent model access from centralized providers and pay variable per-request charges; DIEM’s claimed advantage is that inference capacity can be owned, transferred, staked for usage, or integrated into DeFi-like systems while remaining tied to Venice’s model-access layer.

Venice describes the unit as “tokenized intelligence” in its DIEM launch material, and its API documentation states the practical accounting convention that 1 Diem equals $1 per day of compute.

Diem is not a general-purpose Layer 1 or a decentralized compute marketplace in the same category as Akash, Render, Bittensor, or Filecoin; it is a narrow application token for access to Venice’s hosted inference product.

As of early June 2026, public market trackers placed DIEM in the small-to-mid-cap crypto range, with CoinGecko showing it around the mid-400s by market capitalization within its broader crypto ranking and second inside the small Venice ecosystem category, while the asset information supplied for this report indicated a market capitalization near $63 million and a price in the roughly $1,600 range.

That market size should be interpreted cautiously because DIEM’s float is unusually small, supply is created through a mint-and-burn mechanism rather than conventional emissions, and the token’s economic reference point is Venice compute capacity rather than a broad monetary or governance claim.

Who Founded Diem and When?

Diem was created by Venice.ai, the privacy-oriented AI platform founded by Erik Voorhees, best known for ShapeShift, with Teana Baker-Taylor serving as another senior founding executive according to contemporaneous coverage of the company’s 2024 launch.

Venice itself launched in May 2024 as a private and “uncensored” alternative to mainstream AI applications, then released the VVV token on January 27, 2025, with the company’s own VVV launch post describing more than 450,000 registered users, more than 50,000 daily active users, and an API beta released in November 2024.

DIEM as a tokenized version of Venice compute emerged later, with market-data and security pages listing the Base token in 2025 and Venice’s own materials framing it as the next stage of VVV’s token economics.

The project’s narrative has evolved from private AI access into a two-token capital-and-compute model. Initially, Venice positioned VVV as a utility token that allowed stakers to claim a pro-rata share of daily inference capacity while also earning token emissions.

In July 2025, Venice renamed its earlier Venice Compute Unit concept into Diem and changed the unit denomination so that each Diem represented $1 of daily API credit rather than $0.10 under the old unit system, as explained in its VCU-to-Diem update.

The later tokenized DIEM design separated the compute right from the VVV capital token: VVV holders could lock staked VVV to mint DIEM, while DIEM holders could stake DIEM directly for fixed daily API credits.

How Does the Diem Network Work?

Diem does not operate an independent consensus network. It is an ERC-20 contract deployed on Base at 0xf4d97f2da56e8c3098f3a8d538db630a2606a024, and therefore its transaction ordering, settlement, fees, and finality are inherited from Base rather than from a DIEM validator set.

Base is an Ethereum Layer 2 rollup, and the official Base protocol overview describes it as a rollup built on Ethereum; in practical terms, DIEM’s on-chain transfers and staking operations rely on Base’s execution environment and Ethereum-adjacent rollup security assumptions, while the actual AI inference service is provided off-chain by Venice’s infrastructure.

The technical core is not sharding, proof-of-work, proof-of-stake, or a DAG, but an application-specific mint, burn, and staking system connected to Venice API accounting.

Venice’s materials state that DIEM is minted only by locking sVVV, meaning VVV that has already been staked, and that the holder can later burn the same DIEM amount to unlock the backing sVVV. The mint-rate documentation says the amount of sVVV needed to mint one DIEM rises algorithmically as DIEM supply approaches or exceeds the target supply; the stated launch parameters included a base mint rate of 90, an adjustment power of 2, a target DIEM supply of 38,000, and an initial Venice mint of 10,000 DIEM.

Security therefore has two layers: the smart-contract layer on Base, where the token contract is verified on BaseScan, and the centralized service layer, where Venice must continue honoring staked DIEM as daily API credit.

What Are the Tokenomics of diem?

DIEM has no conventional fixed max supply schedule comparable to Bitcoin and no regular inflation stream comparable to many proof-of-stake assets. Its supply expands when sVVV is locked to mint DIEM and contracts when DIEM is burned to unlock the backing sVVV, making supply endogenous to demand for tokenized compute and to the VVV mint-rate curve.

As of early June 2026, token explorers and market trackers showed supply in the high tens of thousands of DIEM, with BaseScan displaying roughly 37,000 DIEM and more than 4,000 holders at the time its page was accessed.

The relevant dilution question is therefore less “how many DIEM are emitted per year” and more “how much VVV must be immobilized to create new DIEM, and whether the implied compute yield justifies the opportunity cost of locking sVVV.”

The value-accrual design is indirect. DIEM itself accrues utility because staked DIEM grants a fixed $1 per day of Venice API credit per token, while VVV accrues economic relevance because all DIEM creation requires locked sVVV.

Venice’s DIEM explainer states that staked DIEM can be used for access to model inference, while the VVV overview says only VVV stakers can mint DIEM and that DIEM is created from VVV. Venice also reduced VVV emissions after introducing DIEM, with the DIEM launch post saying annual emissions dropped from 14 million to 10 million VVV, while later Venice materials and community notices indicated further reductions and a growing burn program.

In April 2026, Venice introduced programmatic VVV buy-and-burns, where new subscriptions trigger automatic VVV purchases and burns, adding a revenue-linked supply sink around the VVV side of the system rather than a direct DIEM burn from API usage.

Who Is Using Diem?

The economically relevant distinction is between DIEM as a thinly traded crypto asset and DIEM as an API-access instrument.

Trading activity on Coinbase, Aerodrome, Uniswap, PancakeSwap, and other venues can reflect speculation on Venice’s growth or on the scarcity of tokenized compute, but actual utility requires DIEM to be staked and consumed as Venice API credit. Venice’s own January 2025 VVV launch post reported more than 450,000 registered users and more than 50,000 daily active users at that time, but that figure predates the fully tokenized DIEM structure and should not be treated as proof that all Venice users are DIEM users.

The strongest current use case is developer and agent access to AI inference, not DeFi lending, gaming, or real-world assets; however, because DIEM is a Base ERC-20, it can theoretically be held by wallets, DAOs, agent frameworks, or applications that want predictable AI budget exposure.

Legitimate adoption evidence is strongest inside the Venice and Base ecosystems rather than among traditional institutions. Venice’s VVV airdrop explicitly targeted AI-agent and Base communities, including Virtuals-linked participants and other crypto-AI accounts, according to the VVV launch announcement.

In April 2026, Venice added x402 support, allowing wallet-native agents to pay for inference without API keys or conventional billing accounts; the x402 announcement says Venice first checks staked DIEM credits and then falls through to USDC on Base when credits are exhausted.

That is a meaningful infrastructure integration for autonomous agents, but it is not the same as institutional adoption by banks, public companies, or regulated asset managers.

What Are the Risks and Challenges for Diem?

Diem’s regulatory profile is unresolved. There is no spot DIEM ETF, no widely recognized commodity classification, and no public SEC settlement or enforcement action specific to DIEM identified in the reviewed sources, but that absence should not be mistaken for legal certainty.

The token’s utility framing may reduce some securities-law arguments, yet the ecosystem includes staking yield, VVV emissions, revenue-linked VVV burns, secondary-market trading, and a company-operated inference service, all of which increase interpretive complexity. Venice’s own airdrop terms restrict prohibited jurisdictions and sanctioned persons, reserve broad compliance powers, and state that Venice may modify, cancel, or terminate token-related obligations if it believes legal or regulatory developments require it.

Separately, a civil case captioned Uncensored AI, Inc. v. Venice AI, Inc. et al. appeared in U.S. federal court records, but the available Justia court order concerns business-tort and jurisdictional issues involving multiple defendants, not a securities classification dispute over DIEM.

Centralization is the more immediate structural risk. DIEM’s on-chain token can move permissionlessly on Base, but the asset’s economic promise depends on Venice continuing to operate the API, price models in Diem terms, maintain sufficient inference capacity, and honor staked DIEM credits.

Contract risk is also nontrivial because the verified token contract includes role-based minting and burning functions, while the off-chain service layer is governed by company policy rather than decentralized consensus.

Competitively, Venice faces centralized AI platforms with larger model budgets, enterprise distribution, and procurement relationships, as well as crypto-native compute networks that offer broader infrastructure primitives.

The economic threat is that DIEM’s fixed $1/day utility is only valuable if Venice’s model catalog, reliability, privacy posture, and pricing remain competitive against direct subscriptions to OpenAI, Anthropic, Google, xAI, open-source self-hosting, or decentralized compute alternatives.

What Is the Future Outlook for Diem?

Diem’s future depends less on a hard-fork roadmap and more on whether Venice can turn tokenized inference into a durable procurement primitive for developers and autonomous agents. Verified recent milestones include the 2025 Diem denomination change, the tokenized DIEM mint/burn system, the emission reductions around VVV, the launch of programmatic VVV burns in April 2026, and x402 support for wallet-native agent payments.

Venice’s programmatic burn post states that the company intends to add more qualifying burn triggers and migrate more discretionary burns into automatic mechanisms, while the x402 integration points toward a model in which agents can use DIEM and USDC balances programmatically without API-key distribution.

The structural hurdle is proving that DIEM is more than a high-priced claim on a niche API.

For the model to remain viable, Venice must keep expanding usable inference capacity, maintain privacy and uptime claims, support competitive proprietary and open models, and avoid regulatory or platform-policy disruptions that could weaken the token’s service backing.

DIEM is analytically closer to a perpetual service-credit instrument than to a base-layer cryptoasset; its infrastructure viability will therefore be measured by API usage, staked DIEM utilization, sVVV locked to back minted DIEM, retention of developers and agents, and the credibility of Venice’s service-level execution, not by short-term token price movements.