There is a major upgrade to DIMO that is currently being tested with the first developers: Oracles. This is not only a crucial step towards decentralizing the process of building on the DIMO protocol, it means that there is more data available for developers building on DIMO, and most importantly, more value that can be created through new apps and services that build on the platform.

Let's talk about what DIMO Oracles are and what this change means. Here’s the TL;DR, and keep reading for all the important details:

• Any 3rd party can now bring their data to DIMO, eg. a vehicle OEM or a developer with access to a unique stream.

• End users can then activate this new data source. Data flows to their secure vault.

• Developers can access this data through DIMO APIs.

What is an Oracle with DIMO?

An Oracle is a method through which data enters the DIMO network. This can include hardware devices or API connections with companies like Tesla, SmartCar, or any OEM. Think of the connection like a highway that has been laid to connect a data source to DIMO. Since data payloads are slightly different from each connection, DIMO handles normalizing the data so that applications don’t have to worry about this messy part.

Today, six oracles exist: DINC’s Tesla integration, DINC’s Smartcar integration, the three hardware devices launched so far (LTE R1, Macaron, and AutoPi), and a new integration in progress with CompassIoT to support fleet APIs.

Importantly, this highway starts off empty; no data flows by default, a user must activate the data stream, as one does when they connect a DIMO hardware device or their Tesla through the DIMO mobile app. Once the connection has been activated, the data enters the user’s secure vault, and from there, users can choose to share that data with more apps.

Since DIMO’s inception, Digital Infrastructure Inc. has been the sole creator of these oracles, connecting the data sources to DIMO. Our engineers, on behalf of the DIMO Foundation, have done the work of integrating each API, mapping data to a standardized format, and making that data available through DIMO Developer tools like the DIMO APIs and SDKs. It is this workstream that is transforming and unlocking greater accessibility.

With Oracles, we're opening the doors for other companies, individuals, and developers to bring their data connections to DIMO. For example, let’s say a developer has access to a specific data stream that would benefit the DIMO ecosystem like FordPass, a dash camera, or an RTK antenna. The added data to the ecosystem will benefit drivers who connect their vehicles (they'll be able to access more data) and developers (they’ll have more data to work with) and thus can build better products for drivers.

Oracles mean that any developer can 1) build a connection 2) map it to the existing DIMO spec and 3) make that data available to developers. The best part is, those who perform a connection will in the future earn revenue when developers leverage that connection.

Expanding DIMO Beyond Telematics Data

The best part about Oracles is that this paves the way for many other types of data to become available. DIMO was built as an agnostic IoT platform from the beginning, but we started with cars because cars are the largest category of IoT devices in the world. However, other sensors can be integrated into DIMO to complement the data that is already here. We are working with teams that will add EV Charger Connections and other types of data.

Imagine you're a developer with access to data from electric vehicle chargers, video feeds, or telematics that align with DIMO's data structure. You can now connect your data stream to DIMO, enabling other DIMO users to integrate their cars through your method. To put it in a driver’s perspective, in the near future you will be able to stream not just your car’s data to DIMO, but your EV charger data and potentially even video data from an EV.

This evolution is extremely important to DIMO growth. The types and amounts of data within the DIMO Ecosystem are set to expand rapidly. Developers will gain access to new data types, allowing for innovative applications and advanced AI model training. Ultimately, the value for users will skyrocket as their mobile apps become passports to an entire ecosystem of data connections.

Compensating Connection Providers

One question remains, why would a developer want to add a connection to DIMO? There are three reasons.

First, as a developer building, for example, an app for EV charging, you may want to piggyback off of the infrastructure (DIMO SDKs and APIs) already built by DIMO to get a headstart developing your app. Data storage, streaming, and more are all out of the box. All you need to do is add your new connection to DIMO (more details on the process soon) and then you can get back to focusing on the user facing elements.

Second, you help grow the pie within the DIMO Ecosystem. Rather than starting to recruit drivers or developers to a new platform, you can join an ecosystem where there are already over one hundred thousand cars connected and dozens of developers building. It’s another way to leap forward for growth.

Third, the DIMO Foundation is considering future tokenomics proposals to compensate for Oracle creation and maintenance as a means to incentivize the addition and upkeep of reliable and useful data connections. More research is needed, but this is in the works.

Getting Started

Technical documentation for those interested is on the way. We’re working with the first external teams now to work out the kinks in the process so that this can become as frictionless and open as possible. Stay tuned for updates and to watch as this important upgrade helps DIMO grow in utility and network value.

Do you have an oracle that DIMO developers and users would love? Get in touch with [email protected].