• The DIMO Developer Platform launched and is growing, meaning more useful apps are coming to drivers.

• Alongside that, tokenomics updates are coming that will formally introduce a mechanism for driving protocol revenue and network value from developer activity. Drafts to be shared this week.

• DIMO Town Halls will be instituted to share more consistent updates, as well public roadmaps for all DIMO products and initiatives.

Over roughly the last 6 months since DIMO launched and shipped +8,000 DIMO Macarons, we’ve been busy building some foundational pieces for growth and value. We haven’t spent enough time talking about what’s being built, why it all matters, and how our users and community will benefit. Time to do something about that.

I’ll start with the DIMO Developer Platform. A few months ago we released what is really the first version of the platform, including the DIMO Developer License (11 developers are already licensed), which enables other applications to start building on DIMO. We’re working with companies that do insurance, maintenance, fleet products, AI, and more who will use these developer tools and infrastructure.

Why does this matter? Two reasons. First, that means more products will be available to drivers using DIMO today, increasing the utility of the apps and services we have created. A network where any automotive need is accessible to any driver from an app is immensely valuable, and not something automakers can compete with today. We believe this utility is the key to bringing DIMO to tens of millions of people.

Second, there are Tokenomics proposals coming within a week that will finally set the rules for protocol revenue by laying out how developers pay to the protocol when they access vehicle data. We’ll be borrowing from the Helium data credit model.

Here’s a summary of what that governance will look like in a nutshell: let’s say you want to share your data with a company that will remotely diagnose an issue or sell you dynamic insurance — that company will pay in dollars for data credits, and the dollars are used to burn an amount of $DIMO. There will be a public draft available for comment by the community by the end of this week, so keep your eyes peeled for the numbers.

When will this all be in place? Several smart contracts already are! The DIMO Developer License and the DIMO Data Credits are ready. The DIMO Developer Console is launching at the end of June. These pieces need to be stitched together, but this all means that later this summer, protocol revenue will formally start accruing. We have dozens of companies that are lined up to start working with the APIs, and our BD team is bringing those teams on so that utility of the network and network revenue increase constantly.

As a commitment to our community, we’ll publicize formal roadmaps for all products, including the token (the token is a product after all) and we’ll start a monthly DIMO Town Hall to discuss these updates. Announcements coming this week on the schedule.

• The DIMO Developer Platform launched and is growing, meaning more useful apps are coming to drivers.

• Alongside that, tokenomics updates are coming that will formally introduce a mechanism for driving protocol revenue and network value from developer activity. Drafts to be shared this week.

• DIMO Town Halls will be instituted to share more consistent updates, as well public roadmaps for all DIMO products and initiatives.

Over roughly the last 6 months since DIMO launched and shipped +8,000 DIMO Macarons, we’ve been busy building some foundational pieces for growth and value. We haven’t spent enough time talking about what’s being built, why it all matters, and how our users and community will benefit. Time to do something about that.

I’ll start with the DIMO Developer Platform. A few months ago we released what is really the first version of the platform, including the DIMO Developer License (11 developers are already licensed), which enables other applications to start building on DIMO. We’re working with companies that do insurance, maintenance, fleet products, AI, and more who will use these developer tools and infrastructure.

Why does this matter? Two reasons. First, that means more products will be available to drivers using DIMO today, increasing the utility of the apps and services we have created. A network where any automotive need is accessible to any driver from an app is immensely valuable, and not something automakers can compete with today. We believe this utility is the key to bringing DIMO to tens of millions of people.

Second, there are Tokenomics proposals coming within a week that will finally set the rules for protocol revenue by laying out how developers pay to the protocol when they access vehicle data. We’ll be borrowing from the Helium data credit model.

Here’s a summary of what that governance will look like in a nutshell: let’s say you want to share your data with a company that will remotely diagnose an issue or sell you dynamic insurance — that company will pay in dollars for data credits, and the dollars are used to burn an amount of $DIMO. There will be a public draft available for comment by the community by the end of this week, so keep your eyes peeled for the numbers.

When will this all be in place? Several smart contracts already are! The DIMO Developer License and the DIMO Data Credits are ready. The DIMO Developer Console is launching at the end of June. These pieces need to be stitched together, but this all means that later this summer, protocol revenue will formally start accruing. We have dozens of companies that are lined up to start working with the APIs, and our BD team is bringing those teams on so that utility of the network and network revenue increase constantly.

As a commitment to our community, we’ll publicize formal roadmaps for all products, including the token (the token is a product after all) and we’ll start a monthly DIMO Town Hall to discuss these updates. Announcements coming this week on the schedule.