DIP-4 & 5: Amendment 2

Headline: Rebasing deposits and using DIMO Credits for device minting and developer licensing

Author: The DIMO Foundation

Submitter(s): The DIMO Foundation [0xCED3c922200559128930180d3f0bfFd4d9f4F123]

Status: Deployed

Voting URL: Snapshot

Discussion Forum: Discord #🗳️governance forum

Vote Type: Level 3

Abstract

This amendment

1. Introduces rebasing events for the deposit amounts for licenses that are paid in $DIMO.

2. Introduces the DIMO Credit (DCX), a stable token always worth $0.001 in the DIMO ecosystem, created by burning $DIMO based on its market price. Today 100% of the $DIMO used to mint DCX is burned. DCX will be used as the new token for developer licensing and device minting.

3. Switches the device integration cost to use DCX.

4. Simplifies the category formally known as Data Subscriber and replaces the $DIMO license deposit with a one-time DCX payment.

Motivation

Today, the deposits necessary to acquire any DIMO license, as well as device minting costs, are denominated in $DIMO, making their cost highly variable. Already, the market price of $DIMO has changed by an order of magnitude from when the first pricing was set. By allowing for rebasing and/or using the stable DCX token, we can provide a predictable and fair price for builders without undermining alignment and the role of the $DIMO token.

Specification

// If passed, this proposal would edit the following section within the DIP-4 Abstract section:

This proposal outlines the method by which hardware manufacturers (like AutoPi) who produce compatible devices, as well as software developers (like Digital Infrastructure Inc.SmartCar) who build digital integrations (collectively referred to as integration providers) bond $DIMO and receive a license.

The requirements for any integration providers are that they must:

1. Pass a DIP that approves their license application;

2. Bond 100,000 $DIMO tokens as a security deposit;

3. PayTransfer the applicable amount of DIMO Credits (DCX)$DIMO for each integrations they enable; and

4. Remain in good standing with the community.

// And would make the following changes to DIP-4 Specification section.

Integration Providers & Device Licenses

In order to connect to DIMO users, their vehicles, and their data, integration providers must agree to various obligations, receive a license by passing a DIP, bond the required amount of 100,000 $DIMO, and pay DCXdeposit $DIMO for each device they sell.

...

Integration Types

All integrations methods must be categorized as one of the following device types. New device types may be added by token holders with a valid governance vote.

Device Type	Concept Image	Description	Typical Price Point
Software Only	N/A	Leverages existing vehicle subscription programs and their APIs to establish a baseline of connectivity	No added charge. Vehicle manufacturer (e.g., Ford, BMW) may charge a subscription fee.
Dongle		Records vehicle data from the CAN bus.	$350
Hub		IoT hub that enables long term local storage and backup of data.	$500
Dash Camera		Device that records camera footage and possibly other telemetry	$500
Fleet Device		Telemetry devices designed for commercial use	$1,000
AI Device		Device that supplements enhanced driving features (e.g., Comma AI)	$2,000

...

Licensing and Bonding

Licenses are NFTs that can only be minted or transferred by DIMO Integrations. These certify the integration provider meets all required qualifications and has been whitelisted for the integration of compatible devices. After receiving a license, the integration provider is required to submit a deposit of 100,000 $DIMO tokens (the “bond”). For more on how this works, see License.

Periodically, or with a significant change in price of $DIMO, the amount required to bond will rebase automatically. Every year on January 1st, the bond amount automatically adjusts to whatever the amount of $DIMO is that is equivalent to $10,000 USD. Rebasing can also happen within the year, whenever the 7 day token weighted average price (TWAP) of $DIMO changes by 50% or more relative to the price last used to calculate the deposit amount. For example, if $DIMO is worth $2.00 on January 1st, the bond requirement is 5,000 $DIMO. If the price of $DIMO increases to $2.80, there is no change in the deposit amount. Once the token weighted average price over 7 days increases to $3.00, then the bond requirement is rebased to 3,333 $DIMO.

If the bond amount is ever decreased, existing license holders have the option to withdraw the excess amount by notifying the DIMO Foundation of their desire to do so. If the bond amount ever increases, the license holder is grandfathered in and not obligated to add additional $DIMO.

This DIP may be updated without passing an amendment to update the bond amount below per the rules described herein.

As of the last rebasing on July 5, 2024, the bond amount is 77,101 $DIMO.

Past bond amounts were:

• December 12, 2022: 100,000 $DIMO

While it is preferred that the integration provider is the party putting up the bond, it is also possible for a financing partner, such as a distributor, to put up the bond on behalf of the manufacturer.

Should applicants not have $DIMO or not want to interact with tokens, they may purchase $DIMO from the Foundation and/or have the Foundation put up the bond on their behalf.

The bonding amount may be altered by any future governance vote.

Slashing & License Revocation

Through a governance vote, DIMO token holders have the ability alter the manufacturer’s bonding requirements. Manufacturers must be given thirty days to adjust their bond to the new level.

Token holders are also able to ban devices from the network (e.g., if they’re not secure and provide false data) and/or suspend or revoke a manufacturer’s license through a valid governance vote if they violate the obligations specified above or there is demonstrable and material negligence or malice perpetrated by the manufacturer that harms users or the DIMO protocol generally.

Any manufacturer may renounce their license and receive back their bonded $DIMO after six months.

Connecting a Device to DIMO

Device Payment Requirements

For physical hardware, licensed manufacturers pay a 4,000 DIMO Credits (DCX)set amount of $DIMO to mint a device and enable it to connect to the $DIMO network.

The $DIMO payment is set aside. Each month that the connection persists, the integration provider receives some of that $DIMO back as rebate for twenty four months until they earn back 70%.

Why add this complexity? It's to align incentives.

This rebate mechanism ensures that both integration providers and DIMO Integrations are long-term holders of $DIMO and that they have an incentive to produce resilient devices and services that users will love and want to keep connected.

The DIMO Treasury keeps any $DIMO that isn't returned to the manufacturer.

Cost of Device Minting

The amount of DIMO required for device minting varies by device type.

Type	Description	Cost (in $DIMO)
Software	Leverages existing vehicle subscription programs and their APIs to establish a baseline of connectivity	0
Hardware	New hardware that users and purchase and install in their vehicle.	25

Similar to the bond required for licensing, device minting costs may be covered by financing partners, such as a distributor.

Temporary Licenses

For six months after the passage of this DIP, the following companies have a temporary license. Following six months, they will need to apply for a permanent license per the process defined above.

• AutoPi Aps is licensed to produce it's DIMO x AutoPi Data Miner

• Smartcar is licensed to offer a software connection

• Digital Infrastructure Inc is licensed to offer a software connection.

// And would make the following changes to DIP-5 Abstract section.

The DIMO app ecosystem has several main parties:

• Data Publishers: Users connect their devices via hardware and software connections;

• Nodes: receive data from users, validate it, issue proofs of data validity, and serve it to licensed apps and data customers; and

• Data Subscribers: Products that make use of user data and connectivity.

Nodes store data on behalf of users and make it available to the developers with authorization from the user.

This proposal defines how these two entity typesNodes, and Data Subscribers will form, remain in good standing, and interact with users, their data, and the protocol itself. Data publishers are addressed in DIP-4: Device Integrations.

// And would make the following changes to DIP-5 Specification section.

Nodes

A Node is an entity that stores data on behalf of users and makes it available to developers only as authorized by their usersreceives data from devices and, after validating it against proof of movement, makes it available to Data Subscribers. These entities are responsible for forming and upholding agreements that protect user privacy and enable DIMO applications.

Nodes may receive data from several protocols, such as UDP, MQTT, or Streamr Network. They provide API's and interfaces that can be used to access data, and the on-chain indexer.

All data they receive must be encrypted in transit and at rest. Both Nodes and the businesses that they serve must always comply with relevant privacy regulations (e.g., GDPR). Node operators may only share data with licensed developersData Subscribers per the explicit terms of a user's active opt-in. In other words, any Data Subscriber must receive an explicit signature from a user's wallet in order to receive their data.

Prospective Nodes may receive a license by passing a DIP that follows the License Approval Template and by depositing the required $DIMO bond.

Periodically, or with a significant change in price of $DIMO, the amount required to bond will rebase automatically. Every year on January 1st, the bond amount automatically adjusts to whatever the amount of $DIMO is that is equivalent to $30,000 USD. Rebasing can also happen within the year, whenever the 7 day token weighted average price (TWAP) of $DIMO changes by 50% or more relative to the price last used to calculate the deposit amount. For example, if $DIMO is worth $2.00 on January 1st, the bond requirement is 15,000 $DIMO. If the price of $DIMO increases to $2.80, there is no change in the deposit amount. Once the token weighted average price over 7 days increases to $3.00, then the bond requirement is rebased to 10,000 $DIMO.

If the bond amount is ever decreased, existing license holders have the option to withdraw the excess amount by notifying the DIMO Foundation of their desire to do so. If the bond amount ever increases, the license holder has six months to deposit additional $DIMO to reach the new minimum.

This DIP may be updated without passing an amendment to update the bond amount below per the rules described herein.

As of the last rebasing on July 5, 2024, the bond amount is 231,303 $DIMO.

Past bond amounts were:

• December 12, 2022: 500,000 $DIMO

Nodes are to DIMO what Infura or Alchemy are to Ethereum.

DevelopersData Subscribers

DevelopersData Subscribers are entities that offer services to users (e.g., a refinancing app) and/or pay users for data (e.g., an electric vehicle R&D company). Developers must pay 100,000 DIMO Credits (DCX), which is equivalent to $100 USD, to acquire a developer license.

Clients

A client is a type of application that allows users to interact directly with the DIMO protocol. Typically, this will mean creating and managing their account, creating and managing their vehicle identity, adding and removing credentials in their identity glovebox (e.g., insurance and registration), adding and removing telemetry devices, and viewing back their own data.

Clients are to DIMO what Metamask and Rainbow Wallet are to Ethereum. DIMO Mobile is an example of a client.

Applications

An application is a like a light client. It allows users to gain additional value from the protocol by leveraging the data from their vehicle. It will read data and issue commands, but does not mint new vehicles and manage vehicle connections (e.g., pairing a hardware device). Typically this will mean logging in with DIMO to the application and allowing it to access your vehicle data, where the application extends the available insights, enables new savings, or new features on top of the protocol.

Some examples of apps include peer-to-peer car rentals, efficient online car marketplaces, defi auto lending, smart insurance, and web3 ride hailing. Uber, Geico, eBay Motors, and Hertz could be rebuilt as leaner, cheaper, and more effective protocols on top of DIMO. DIMO Explorer is an example of an application.

Data Consumers

A data consumer is an entity that subscribes to user data. Various businesses will want to purchase traffic, battery, self-driving, video, and other telemetry data. McKinsey published an overview on the value of data consumption here.

Licensing

Prospective Clients and Nodes may receive a license by passing a DIP using the License Approval Template.

Applications and Data Consumers do not require a governance vote to receive a developer license, but must comply with all terms in the Obligations and Bonding sections in order to interact with DIMO Users and their data. The DIMO Foundation is able to issue developer licenses in its discretion.

Bonding

Clients, Nodes, Applications, and Data Consumers must bond $DIMO (or must have someone do it on their behalf) as defined below. If a licensee violates their obligations as specified below, their license may be suspended or revoked. They may renounce their license and receive back their bonded deposit six months later.

Nodes: Must bond 500,000 $DIMO as a one-time deposit.

Clients: Must bond 20,000 $DIMO as a one-time deposit.

Applications & Data Consumers: Do not need to bond $DIMO for now.

Should applicants not have $DIMO or not want to interact with tokens, they may purchase $DIMO from the Foundation and/or have the Foundation put up the bond on their behalf.

The amounts for bonding, as well as the exchange rate for $DIMO offered by the Foundation, may be altered by any future governance vote.

Obligations

Clients, Nodes, Apps, and Data ConsumersNodes and Developers commit to maintaining strict quality and security standards, provide support for their services, always act in good faith, and agree not to engage in unlawful activities. The following is illustrative but not exhaustive.

...

Temporary Licenses

For six months after the passage of this DIP, the following companies are have a temporary license. Following twelve months, they will need to apply for a permanent license per the process defined above.

• Digital Infrastructure Inc is licensed to operate:

  • Node: DIMO Web Services

  • Client: DIMO Mobile

Implementation

If passed, DIPs 4 & 5 would be udpated and these changes implemented once the software code is audited and ready, or after the four day timelock, whichever is later.

Copyright

Copyright and related rights waived via CC0

Citation

Please cite this document as:

The DIMO Foundation, " DIP 4 & 5 Amendment 2", June 2024. [Online serial]. Available: [https://github.com/DIMO-Network/DIP]

Changelog

Disclaimer

The contract addresses for $DIMO are 0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b on Ethereum and 0xE261D618a959aFfFd53168Cd07D12E37B26761db on Polygon. Please always confirm that you are interacting with these contract addresses and not those of a fraudulent imitator. This proposal may not be enacted if it violates Cayman Islands law. Please triple check that any communications are authentic as it’s common for scammers to try to trick you into sending them crypto or into revealing your private keys.

Certain statements in this document constitute forward-looking statements. The words “may,” “will,” “should,” “project,” “anticipate,” “believe,” “estimate,” “intend,” “expect,” “continue,” and similar expressions or the negatives thereof are generally intended to identify forward-looking statements. Such forward-looking statements, including the intended actions and performance objectives, involve known and unknown risks, uncertainties, and other important factors that could cause the actual results, performance, or achievements to differ materially from any future results, performance, or achievements expressed or implied by such forward-looking statements. There can be no assurance that such statements will prove to be accurate as actual results and future events could differ materially from those anticipated in such statements. Accordingly, readers should not place undue reliance on forward-looking statements and nothing in this document represents a promise of specific work to be completed in the future.