DIP-2: Amendment 5
Last updated
Last updated
Headline: Simplifying the connection level system and increasing Tesla rewards
Author: The DIMO Foundation
Submitter(s): The DIMO Foundation [0xCED3c922200559128930180d3f0bfFd4d9f4F123]
Status: Review
Voting URL: TBD
Discussion Forum: #🗳️governance forum
Vote Type:
This amendment replaces the current "Limited" and "Comprehensive" connection categories with a 3-6 level system that raises the bar for qualified connections. Levels range from Level 3 (moderate data updated every minute) to Level 6 (comprehensive real-time data), with progressively higher weekly point rewards incentivizing higher-quality connections.
All reward boosts are consolidated into the level system, simplifying how boosts stack. A connection registry clarifies which integrations qualify for each level and their designated hosts.
Tesla's native connection from Digital Infrastructure Inc. is upgraded to Level 6 due to improved polling, achieving parity with R1 and AutoPi. The classic Smartcar integration becomes ineligible due to limited data liveness, though a future enhanced Smartcar product could qualify for Level 6 when available.
The current binary system inadequately reflects data quality spectrum and fails to establish minimum network participation standards. By raising the qualification floor to Level 3, this amendment addresses a key product-market fit challenge: app developers and users struggle to derive meaningful value from limited connections, so these have been eliminated from earning eligibility.
The 3-6 level system ensures only valuable data contributors receive rewards while properly compensating based on actual network contribution. Consolidating all boosts into the level system eliminates reward calculation complexity.
The connection registry brings transparency to qualification criteria. Tesla's technical improvements warrant Level 6 recognition alongside premium hardware solutions, while legacy integrations failing to meet modern standards are excluded to maintain network quality.
This framework strengthens incentive alignment between data value and rewards while establishing quality thresholds that improve overall network utility for developers and end users.
// If passed, this proposal would incorporate the following changes to the Specifications section of DIP-2:
...
Connection types: Currently licensed connections are categorized as follows:
Level 6: R1 by Ruptela, AutoPi x DIMO by AutoPi, Tesla by Tesla with Digital Infrastructure Inc., Enhanced Smartcar by Smartcar with Digital Infrastructure Inc.
Level 3: Macaron by Hashdog
to be considered "comprehensive", an integration must send extensive telemetry data in near real-time. As of the last update of this proposal, the AutoPi, LTE R1 and native Tesla connections qualify as "comprehensive" integrations.
Every box depicting points can stack on one another. This means that a car can have a streak level, a boost level, on top of their data connection for a maximum level of 12 a software connection, and hardware connection for a maximum 16,000 weekly points. A car must send valid data to qualify for rewards in a given week. If a car isn't driven, it will receive zero $DIMO regardless of any streak or boost.
In the example shown in the table above, Alice earns 1 levels2,000 points for having been connected between 21 to 35 weeks, 2 levels1,000 points for locking 1500 $DIMO for 126 months, 1,000 points for her Limited software connection, and 6 levels,000 points for having a premium connection for comprehensive device installed in her vehicle.
Here there are 40,000 cars connected to DIMO and each car generates an average of 6 levels,000 points that week, for a total of 240,000 levels,000 points. Alice's 9 levels10,000 points represent 0.003754% of the points for that week (910,000 ÷ 240,000,000). Therefore, she earns 41.437546.04 out of the 1,105,000 tokens from this pool (1,105,000 * 0.003754%).
Curious how this would play out for people besides Alice? The table below shows earnings for a small sample of hypothetical drivers in the same hypothetical week. This is meant to be illustrative using a small handful of made up users, not an exhaustive list of every combination of attributes.
If passed, DIP-2 would be updated and these changes implemented after the four day timelock.
Please cite this document as:
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.
Copyright and related rights waived via
The DIMO Foundation, "DIP-2: Amendment 5", June 2025. [Online serial]. Available: []
The contract addresses for $DIMO are 0x5fab9761d60419c9eeebe3915a8fa1ed7e8d2e1b on , 0x5eAA326fB2fc97fAcCe6A79A304876daD0F2e96c on / , and 0xE261D618a959aFfFd53168Cd07D12E37B26761db on . 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.
