Diem

The contract that defines this asset is Base 0xf4d97f2da56e8c3098f3a8d538db630a2606a024. It is a Venice.ai compute-access token and has no technical, corporate or reserve relationship to the former Libra/Diem payment network.

Blockscout recorded 37,047.748869510756325984 DIEM across 5,891 holder addresses at review. That supply can move because a role can mint and burn; CoinGecko correctly lists no finite maximum.

The market price reflects the present value and risk of a repeating service benefit. “$1 per day” describes API credit generated by staking, not a peg, reserve value or redemption of one token for one dollar.

Before tokenization, VVV stakers received a changing share of Venice’s daily inference pool. DIEM separated a fixed daily service allowance from the capital token so a developer could buy access without first taking a proportional VVV stake.

A holder stakes DIEM directly in the token contract. Venice’s billing API then reports DIEM balance and epoch allocation, and API usage consumes that day’s credit according to model prices.

This is a hybrid claim: staking is onchain, while model delivery, metering and authorization are offchain. The chain can prove a balance but cannot force a GPU or third-party model provider to answer.

Only sVVV derived from VVV 0xacfE6019Ed1A7Dc6f7B508C02d1b04ec88cC21bf is described as the source of DIEM. StakingV2 locks sVVV, calls privileged mint, and later burns equivalent DIEM to release it.

The launch curve used 90 sVVV per DIEM as its base, adjustment power 2 and a target of 38,000. The rate grows exponentially as supply approaches the target, so marginal creation becomes costlier rather than mechanically impossible.

Venice explicitly controls the target and scheduled a rise toward 40,000 in 2026. A target is a policy input, not a cap: the verified token contract places no ceiling on MINTER_BURNER_ROLE.

DIEM includes stake, initiateUnstake and unstake instead of delegating custody to a separate vault. Staked balances sit at the token address and qualify the wallet for daily API capacity.

Unstaking moves an amount into cooldown. The initial duration is one day, but DEFAULT_ADMIN_ROLE can set any uint256 duration; there is no coded upper limit or timelock in this contract.

The code has no pause or blacklist, so ordinary transfers stay simple. Yet admin can appoint minter/burners, and that role can change any account’s supply through mint or burn without the holder’s approval.

A VVV holder may mint DIEM, sell it, and keep earning 80% of ordinary staking emissions on the locked sVVV. To recover the principal, the system requires the same quantity of DIEM to be burned.

If DIEM’s market price rises after sale, buying back the burn amount can cost more than the original proceeds. The position behaves like a liability tied to an access asset, even though there is no liquidation engine forcing closure.

The stated 80% is a share of variable VVV emissions. It is not a dollar yield, and risks in VVV price, DIEM price, contract roles and Venice service economics accumulate rather than cancel.

Venice says one staked DIEM supplies $1 of API credit every day and does not expire. The contract can preserve a token indefinitely, but credit creation and model access occur in systems controlled by Venice.ai, Inc.

Current terms allow the company to set prices, restrict API behavior and revoke access for violations or provider demands. They describe Venice Credits separately; the reviewed terms do not turn DIEM into cash, legal tender or an unconditional debt claim.

DIEM on Base could outlive the company, but its usefulness for calling models is renewed only while Venice recognizes accounts, sets prices and runs servers. The gap between token persistence and service persistence is the design’s central dependency.