Season 2 - Network Growth & Developer Tooling
October 2022 - January 2023 - More cars online, more things to do with them: Functional IDs, New Device Categories, and Node Operators, Marketplace Rewards
This is a future season of DIMO, so everything listed here is subject to change.
You can join the discussion on Discord to provide feedback or ideas.
​Apps - Launching features to help DIMO users save money and time on vehicle finance, retail, and insurance.
​Hardware - Fulfilling according to the schedule published in Hardware & Shipping, and securing more supply to keep Shop.Dimo.zone open. Adding accessories and additional SKUs.
​Governance - Scaling up grant and bounty programs to drive additional integrations and hardware development on DIMO. Adjusting to needs that arise from network launch.
​Platform - Upgrading core smart contracts, adding scaling features to DIMO web services.


⏹S2E1 Mobile App Release - Document and Vehicle Condition Verification, allowing users to prove ownership and current status of a vehicle, opening up more transaction possibilities.
⏹S2E2 Mobile App Release - Trips, fuel, and charge tracking will launch in the DIMO mobile app, making it easy for users to track & share driving habits with developers who can build some awesome new apps with this building block.
⏹S2E3 Release - Get error codes from your DIMO hardware devices, improved notifications, and unlock some other secret hardware features 🀫
⏹ Explorer S2E1 Release - Enable users to view and improve DIMO device definitions for vehicles.
⏹ Explorer S2E2 Release - More data from more cars! Adding classic vehicles and rankings based on real-world DIMO data.


⏹ DIMOxAutoPi - OTA updates to deliver improvements to initial customers
⏹ Shop.Dimo.Zone - Re-launch to include additional hardware OEM presales
⏹ Add additional device supply and new accessories for AutoPi units.
⏹ V0 Open Device Integration Spec Published - Allowing hardware vendors to apply for licenses that grant them the ability to produce DIMO-compatible devices. Grants will also be available to support early development.


⏹ DIMO Improvement Proposals (DIPs)for dispute resolution, integrations, and hardware ecosystem are implemented.


The following contracts will be added / upgraded, and additional capabilities will be added to DIMO core to support new functionality.
⏹ Proof of Movement (Trip NFTs) - Enabling users to combine telematics data from their vehicles into an on-chain asset that can be consumed by apps and services, unlocking ridehailing, social apps, and other experiences on DIMO.
⏹ Roles and Rights V0 - Enabling more advanced permissions and fleet management behavior
⏹ Device minting NFT & rebate contract - As outlined in DIMO Improvement Proposals (DIPs)for hardware device manufacturers
⏹ DIMO Name Service - Human Readable Names for DIMO-connected devices
⏹ Existing Vehicle ID (NFT) contract will be upgraded, allowing additional functionality and transfers
Building on the existing Open Vehicle ID spec, DIMO will open-source the verified credentials framework and SDKs for 3rd party application developers. This will enable any entity to sign data about the vehicles and users, attaching it to Vehicle IDs as Verifiable Credentials.
This will allow existing utilities like title, insurance, and DMV transactions to move from the paper world into a wallet controlled by the user.
Decentralized ride hailing/carsharing, automated parking, dynamic energy resources and more can be built on this platform as devices can transact more autonomously with the outside world.
⏹ Node Operators
Any node operator will be able generate demand signals for data and create products that access and resell data per predefined terms (specifying pricing, revenue splits, permissible uses and more). This is outlined in DIMO Improvement Proposals (DIPs), and is under active development.
The initial Node Operator will be the team behind Explorer They're responsible for producing datasets that are (1) desired by data consumers, and (2) aligned with the interests of their members (data providers). Explorer (and future operators) will need to stake $DIMO in order to operate a node, which can be slashed and distributed to impacted users if terms of service are violated.
The dataset can be produced in two formats. (1) A stream of live data coming from the user’s vehicles with minimal delay. (2) A specific data set to answer a direct question, such as battery health across different geographic regions.
To complete a transaction from data collection to utilization a variety of parties with different interests and specializations need to interact. Data must make its way from devices to the Data Union(s), then to data consumers and app developers. We’ve established roles and interfaces to remove as much friction as possible throughout the process.
Copy link
On this page