DIMO is an open protocol for vehicle identity, consent, and telematics data; DIMO is its fungible token, not a promise that every connected driver will earn rewards.
| Metric | Value |
|---|---|
| Ticker | DIMO |
| Price | — |
| Market Cap | — |
| 24h Change | — |
CoinGecko identity and widget fields checked 22 October 2026. The table contains live market fields only; supply notes follow dated official token documentation and approved governance changes.
Overview
DIMO’s developer platform lets applications request permissioned access to vehicle data and build on identity and attestation primitives. A car owner or fleet controls consent over what information is shared and with whom. This is different from saying that vehicle data is automatically sold or that every vehicle receives a transferable ownership NFT. The protocol’s current direction emphasizes builders using verified vehicle records and access permissions; actual consumer services depend on the applications built on top.
Tokenomics and Supply
DIMO’s original token model allocated 450 million of its 1 billion total supply (45%) to driver rewards, according to the Foundation’s deployed DIP-2. DIP-12 is approved and ends baseline weekly issuance when enacted; official support material confirms those rewards have ended. The proposal also approves a one-time 150 million DIMO treasury burn and authorizes discretionary future fee-revenue burns, but approval alone does not prove a burn transaction executed. Check on-chain records before treating it as completed or using it to calculate supply. It also authorizes moving vehicle-session records to Ethereum without setting a migration date. The Foundation’s DIP-10 defines DIMO as the ecosystem token for governance, staking, and payments; market data is not a supply audit.
Use and Risks
The former weekly issuance rewarded connecting a vehicle and sharing data; that incentive should not be described as ongoing after the approved change. The protocol’s longer-term token demand depends on actual use of its fee, governance, and staking mechanisms, and on whether builders create services people choose to use. DIMO’s technical documentation describes permission controls and data queries, but it does not establish that every driver can monetize data or that a particular buyer will purchase it. Vehicle telematics can be sensitive, so consent and access scope matter.
Social Media Sentiment
- A September 2026 r/dimo_network thread (15 votes at retrieval) discusses the end of weekly rewards and the proposed treasury burn. Several replies question whether new product use will replace the incentive; this small, self-selected discussion records concern but is not a representative measure of token holders. Open discussion
Last updated: 2026-10
Related Terms
See Also
- Real World Asset Tokenization: What It Actually Is
- NFTs and Digital Game Ownership: What Actually Changes
- What Is Tokenomics — And Why It Determines Whether a Crypto Project Survives
- ChangeNOW — crypto exchange option
Sources
- DIMO Developer Docs — describes permission management, telematics queries, and developer integrations.
- DIMO DIP-12: The Protocol Direction — records the approved issuance change, proposed one-time burn, and authorized but unscheduled Ethereum record migration.
- DIMO Support: Changes to DIMO Rewards — confirms that baseline weekly token rewards have ended.
- CoinGecko: DIMO — identifies the DIMO asset and reports its market data and supported networks.
- DIMO DIP-2: Baseline Issuance — documents the original driver-reward allocation and schedule.
- DIMO DIP-10: Network Tokens — defines DIMO’s ecosystem role in governance, staking, and payments.