DIEM Mint Rate History

What you're looking at

Venice's DIEM token uses an exponential bonding curve to set the mint rate (sVVV that must be locked to mint 1 DIEM). The formula is published, but the deployed contract does not charge it directly: it reads a 256-entry lookup table of supply thresholds and rates, and charges the rate at the top of the current 500-DIEM bucket. Everyone minting between 37,000 and 37,500 DIEM supply pays the 37,500 rate. Just after a bucket boundary, the paid rate sits up to ~7% above the smooth curve.

So this page records what was paid, not what the formula predicts. Each mint's rate comes from the staking contract's own event log (sVVV locked divided by DIEM minted), the headline rate is the contract's live quote (the same number the Venice app shows), and the supply trajectory is replayed from every mint and burn in order. Rebuilding from events also surfaces the burn history (sVVV unlocks via DIEM burn), which is invisible on a price chart.

Methodology

1. Pull every Transfer(0x0, _, _) (mint) and Transfer(_, 0x0, _) (burn) event on the DIEM contract, sort in on-chain order, and walk through tracking the running supply.
2. Pull every DiemMinted(svvvLocked, diemMinted) and DiemBurned(svvvUnlocked, diemBurned) event on the sVVV staking contract and pair each with its DIEM transfer by transaction. The rate paid is svvvLocked / diemMinted, an observed price rather than a modelled one.
3. Pull every DiemMintRatesUpdated event to reconstruct the exact rate table in force at any moment (used for weekly snapshots and as fallback for the rare mint with no staking log).
4. Read getDiemAmountOut() for the current headline rate, the contract's own quote.
5. Reconcile the reconstructed final supply against on-chain totalSupply() at the same anchor block (current run: zero drift).
6. Aggregate weekly snapshots for the chart and milestone crossings for the threshold table.

Dust events of 0.001 DIEM and under (deployer test mints + rounding artefacts) are filtered from the displayed event log but remain in the on-chain supply reconciliation. Before 31 August 2026 this page computed rates from the published continuous formula at exact supply, which understated actually-paid rates by up to one bucket step (~3-7%); a reader comparing our number to the Venice app's quote caught it, and the entire history has been rebuilt from paid amounts.

A few things this dataset shows

• Launch day was a frenzy. On 20 August 2025, supply rocketed from zero to over 33,000 DIEM in hours, pushing the mint rate from 90 sVVV through 100, 150, 200 and 300 in a single day.
• The post-launch unwind was real. For weeks after launch, supply actually shrank as users burned DIEM to unlock their sVVV. That mechanism is invisible if you only look at price.
• Bucket pricing reached the at-target rate two months before supply did. The first mint to pay 665 sVVV (the formula's rate at the then-38,000 target) landed on 16 February 2026, with supply still at ~37,600, because the last bucket below target already charges the target-bound rate. Supply itself first crossed 38,000 on 15 April 2026, and the paid rate peaked at ~809 sVVV in early May before the net-burn unwind.
• Net flow is the right indicator of escrow direction. Today the supply lock is filling, but in the past it has been net-negative for stretches.

Effective float (the supply that can actually trade)

Total VVV supply growing tells you almost nothing on its own. What matters for price is the tradeable supply: total minus what's been permanently burned, minus what's locked in DIEM escrow. The chart below stacks all three and shows free float over the same window as the mint history above. Since DIEM launched in August 2025, free float has actually shrunk slightly even as new emissions added millions of VVV, because escrow plus burns more than absorbed the new issuance.

Sources and reproducibility

• DIEM contract: 0xf4d97f2da56e8c3098f3a8d538db630a2606a024 (Base mainnet)
• sVVV staking contract (escrow, rate table, paid-amount events): 0x321b7ff75154472b18edb199033ff4d116f340ff
• Formula: published by Venice in 7 Days to DIEM. It generates the on-chain table entries; the contract charges the table, not the continuous curve
• Pipeline: scripts/refresh-diem-mint-history.ts in the OYM repo. Fully reproducible against any Alchemy Base RPC endpoint.
• Refresh cadence: daily via GitHub Actions. Last refreshed: 2026-09-16.

If you want to use this dataset in your own research or writing, please attribute Own Your Mind and link back to this page. We rebuild the entire history each refresh, so the JSON is always consistent end-to-end.