Data in the network is validated by a series of validations that check a few conditions on the data sent within the network, guaranteeing the data is genuine. By utilizing an alternate source of truth, we can be sure that the data is unique and valid.

Proof of Movement

Each compatible device with a 0x address signs data as it is generated. The data payload and the summary(trip) is sent to the data validators who perform several checks on the data. After it’s connected, the wallet will sign outgoing data payloads, which includes the vehicle ID and trip data, using its private keys.

The next step is to cross-reference cellular connectivity, GPS, accelerometer, and other trip data to identify inconsistencies. In other words, did the car report driving 10 miles, but it never hit another cell tower? That data is SUS!

While this isn’t a flashy feature that drivers will notice immediately, it’s a key part of making the DIMO protocol scalable, credible, and effective for developers and data consumers. As the world gets more confident in the open, trustless, and verifiable way DIMO generates, stores, and shares data, more and more companies will want to build on DIMO. And the more companies building on DIMO, the more other companies can plug into what those companies build, the more users show up to join DIMO, and the flywheel continues to spin.


By utilizing RADIUS data from cell networks, validators can confirm or deny whether a certain vehicle was in a specific area, connected to a specific tower. This data cannot be faked unless you compromise 4G cellular.


As an alternative to cellular, or in addition to, helium broadcast data can be used in a similar way to check the location of the vehicle and against location of helium hotspots that were used for data transmission.


As DIMO network grows, we expect to move to devices validating each other in a way similar to helium proof of coverage operation. This requires significantly more density to be successful.

Last updated