🌏
Season 4+ Global Scale
April 2023 & beyond: How DIMO reaches every device in the world
This is a future season of DIMO, so everything listed here is subject to change.
You can join the discussion on Discord to provide feedback or ideas.

Native OEM Integration Toolkit

Future vehicle architectures will potentially allow the removal of plug-in devices from the vehicle and direct integration with the OEMs that provide sufficiently secure and independent onboard computing platforms.
3rd-party plugin devices will be a supported option that provides additional security, redundancy, and functionality - similar to β€œrunning your own node” in traditional blockchain networks. This will allow for verified data streams to continue to be collected by fleet operators, insurance companies, and device owners who do not want to rely on OEMs for connectivity.

Data Privacy & Validity Improvements

User DID

We will closely monitor and contribute to the anti-sybil and proof of personhood infrastructure that is in development by various web3 companies such as Gitcoin, IDX, BrightID, and others. As the Zero Knowledge Proof and DID space evolves, we will utilize these tools to further decentralize user/device information and improve privacy beyond what is possible today.
Key Management
With DIMO, vehicle owners control connections to their devices in cryptographically secure and anonymized ways. Given that anyone can participate in the DIMO network, data payloads of devices are strongly encrypted using asymmetric key cryptography. Only parties holding an authorized private key can read the data. The key to the data will be held in a smart contract which will define the parties that can access the key and the data. This will guarantee that only the authorized recipients can access the data. Multicast encryption techniques may be used in the future to frequently rotate the keys to the data and selectively block data consumers who are misbehaving.
Additionally, DIMO will prioritize user privacy by utilizing zero-knowledge proofs, separating personally identifiable information wherever possible, and providing users with fine grained opt-in data sharing controls, rather than all-or-nothing or complex opt-out controls, as has become the norm in many web2.0 applications.

Universal Secure Communication

Every automotive OEM has their own closely guarded protocols for communicating with vehicles. DIMO will work with OEMs to create an open source communication standard that allows for open communication between person/app/company and vehicle (P2V), as well as vehicle to vehicle (V2V)
Copy link
On this page
Native OEM Integration Toolkit
Data Privacy & Validity Improvements
Universal Secure Communication