DIMO (Digital Infrastructure for Moving Objects) is a decentralized infrastructure network for connecting vehicles and managing automotive data. The project uses a DePIN model in which drivers connect their vehicles through compatible hardware or software integrations, control permissions for data access, and may receive rewards in DIMO tokens. For developers, the network provides a unified layer for accessing telemetry, vehicle identity, and user-authorized data across dozens of automotive brands. Unlike DePIN projects focused on wireless coverage or computing resources, DIMO builds distributed vehicle data infrastructure connecting car owners, applications, devices, and service providers.
Contents
- What Is DIMO and How Does Automotive DePIN Work?
- Connecting a Vehicle: AutoPi, R1, Macaron and Software Integrations
- DIMO Token, Rewards and the Vehicle Data Economy
- Vehicle ID, Permissions and DIMO Data Infrastructure
- DIMO Ecosystem and the Future of Automotive DePIN
1. What Is DIMO and How Does Automotive DePIN Work?
DIMO is being developed as an open protocol for vehicle data. In the traditional model, information about a car is distributed across the manufacturer, the brand's mobile application, insurance companies, service centers, and other platforms. Access depends on proprietary APIs and the policies of individual companies. DIMO aims to create a common layer where a vehicle has a digital identity and its owner controls permissions for the use of its data.
The core infrastructure is developed by Digital Infrastructure Inc., while the development of the open protocol and its governance is associated with the DIMO Foundation. Users connect compatible vehicles, after which data can be supplied through a hardware device or software integration. Depending on the connection method, the system can receive information about mileage, fuel or battery level, location, trips, diagnostic trouble codes, and other supported parameters.
DIMO's DePIN model differs from networks where participants install hardware to provide services to other users. Here, the primary physical object is the vehicle itself, while the resource generated by the network is verifiable vehicle telemetry. Drivers must grant an application the appropriate permissions before it can access their data, so connecting a car does not automatically make all information available to every developer.
DIMO is positioned as an infrastructure layer for automotive applications. It can support services related to diagnostics, maintenance, insurance, fleet management, EV charging, and trip analytics. This approach allows developers to work through a unified interface instead of building separate integrations for individual automakers.
2. Connecting a Vehicle: AutoPi, R1, Macaron and Software Integrations
The connection method depends on the capabilities of the vehicle. Modern connected cars can use software connections through automaker APIs or automotive data aggregators. DIMO supports infrastructure for dozens of brands, including Tesla, Ford, BMW, Toyota, and Hyundai. When suitable telematics cannot be accessed through software, dedicated hardware devices can be used.
Supported solutions include AutoPi x DIMO, the R1 device from Ruptela, and the compact Macaron. They differ in the type of data they collect, connectivity methods, and level of integration. Hardware devices can interact with a vehicle's diagnostic interface and transmit telemetry to DIMO infrastructure, allowing cars without suitable built-in APIs to participate in the network.
| Component | Type | Role in the DIMO Ecosystem |
|---|---|---|
| AutoPi x DIMO | Hardware connection | Collects extended vehicle telemetry through a physical device |
| R1 | LTE hardware | Connects a vehicle to DIMO and transmits data through cellular networks |
| Macaron | Compact hardware | Provides an alternative hardware method for connecting a vehicle |
| Software Connection | API integration | Retrieves data from compatible connected cars without dedicated hardware |
| Vehicle ID | On-chain identity | Represents the digital identity of a connected vehicle |
| DIMO Developer Platform | API infrastructure | Provides applications with access to authorized vehicle data |
A separate licensing system applies to integration providers. Hardware manufacturers and developers of software connections must obtain the appropriate protocol authorization and comply with applicable governance requirements. This structure is intended to limit unverified telemetry sources and establish rules for participants supplying data to the network.
Different connection methods do not necessarily provide the same value to the protocol. A dedicated hardware device may supply a broader and more continuous stream of telemetry, while a software integration depends on the automaker's API and the signals it exposes. These differences can also affect the reward system, where connection quality is one of the factors used to determine user rewards.
3. DIMO Token, Rewards and the Vehicle Data Economy
DIMO is the protocol's native utility and governance token. Its maximum supply is set at 1 billion tokens. The asset is used for incentives, participant licensing, governance, and economic coordination within the infrastructure. Owners of connected vehicles may receive DIMO through Baseline Issuance when their vehicles provide eligible data and meet the current requirements of the program.
Rewards are not fixed. The system considers connection quality, participation history, and other parameters, with more capable connections generally receiving greater weight. A vehicle must also provide valid data during the relevant period; simply having a registered Vehicle ID does not automatically guarantee token rewards.
Key Features of the DIMO Economy:
- automotive DePIN based on connected vehicles;
- DIMO as the primary protocol token;
- maximum supply of 1 billion DIMO;
- Baseline Rewards for providing eligible vehicle data;
- different reward weights for hardware and software connections;
- on-chain identification of connected vehicles;
- permission-based application access to user data;
- DCX for developer access to vehicle data;
- licensing for hardware and software integration providers;
- protocol governance through DIMO Improvement Proposals.
Another part of the economy concerns developers. Applications use DIMO Credits, or DCX, to access data from connected vehicles. Under the described model, the base access cost is 1,250 DCX, equivalent to $1.25 per vehicle per month. Once used, DCX is burned and cannot be spent again.
Funds associated with DCX purchases are distributed between data infrastructure and the protocol according to established rules. This creates a model in which economic activity can come not only from token issuance to drivers but also from actual developer demand for automotive data. The market value of DIMO remains variable, however, so token rewards should not be interpreted as guaranteed or fixed income from connecting a vehicle.
4. Vehicle ID, Permissions and DIMO Data Infrastructure
One of DIMO's core concepts is programmable vehicle identity. When a car is connected, it receives a Vehicle ID associated with the blockchain infrastructure. This serves as a persistent identifier within the protocol and allows applications to interact with the vehicle through standardized mechanisms instead of maintaining separate proprietary identity systems.
Most continuously generated telemetry is not written directly to the blockchain. Speed, coordinates, battery level, and other vehicle signals create a large and potentially sensitive stream of information. DIMO therefore separates on-chain identity and permissions from the off-chain infrastructure used to store and transmit telemetry.
Vehicle owners control the permissions granted to individual applications. The DIMO Developer Platform provides separate permissions for telemetry, trips, attestations, and other data categories. Once authorization has been granted, a developer can use the API to access the required information. Permissions may have expiration periods and can be revoked by the owner.
This architecture is particularly important for privacy. Vehicle telemetry can reveal location, routes, travel schedules, and patterns of vehicle usage, making the publication of complete datasets on a public blockchain undesirable. DIMO primarily uses blockchain technology for identity, permissions, settlement, and coordination rather than as a public database containing a vehicle's complete movement history.
5. DIMO Ecosystem and the Future of Automotive DePIN
DIMO is gradually evolving from a vehicle monitoring application into infrastructure for third-party developers. The DIMO Developer Platform provides APIs for accessing telemetry, location, mileage, fuel or battery levels, tire pressure, and diagnostic information when the relevant signals are available and the vehicle owner has granted permission. Integration tools include SDKs for TypeScript, Python, and C#.
This approach addresses the fragmentation of automotive data. Manufacturers use different APIs, formats, and authorization systems, while DIMO aims to provide a common interface for working with vehicles from multiple brands. This can reduce the number of individual integrations required to build applications that support a broad range of connected cars.
The project's blockchain infrastructure is also evolving. DIMO initially operated on Polygon PoS and later announced plans to move toward Base, with expanded availability of the DIMO token on the network forming part of this transition. Protocol migration is a broader, multi-stage process and should be distinguished from simply making the token available on another blockchain.
The main risks extend beyond the market value of DIMO. The ecosystem depends on reliable hardware, automaker APIs, secure telemetry infrastructure, permission management, privacy protections, and continued developer adoption. As more applications gain access to vehicle information, transparent consent and access controls become increasingly important.
DIMO represents a DePIN model in which the vehicle serves as the physical source of data while blockchain infrastructure coordinates identity, permissions, and economic incentives. The network's long-term value will depend not only on the number of connected cars or distributed tokens, but also on actual demand for vehicle data from applications, fleets, insurance services, and other participants in the mobility market. If a common infrastructure can support vehicles from different manufacturers while preserving user control over data, DIMO could function as a programmable layer connecting vehicles with digital services.
