Community Owned
How we're transition the DIMO project to user-ownership.

Why DIMO must be a decentralized community owned protocol

DIMO aims to be a reliable, secure, and user-aligned base layer for connected devices. We believe the only way to credibly achieve these goals is to build DIMO as an open source platform where control is vested in a diverse collection of users and stakeholders who all have skin in the game.
Facebook, Twitter, Instagram, Google, and connected vehicle platforms like Wejo are "walled garden" platforms. Users have seen how their incentives are not aligned when interacting with these digital monoliths. Developers have seen how they will extort you if you become successful on their platform. There are no clear rules on access and censorship, and ultimately ownership of your data.
We blame the incentives that Web 2.0 business models systematically create. DIMO’s vision is to create a reality where user-owned digital ecosystems are the norm. We're building a better model.
We also want DIMO to scale and grow its offering quickly and effectively. By reducing friction and bureaucracy, opening up DIMO to global contributors, creating an operating structure that can scale, and aligning all stakeholders around the $DIMO token, the DIMO platform and the apps on top of it will be built far better and way faster.

DIMO Will Be Run as a Foundation (DAO)

Digital Infrastructure Inc, and other early partners responsible for building the IP behind DIMO will shift control of the project to a foundation (which we'll refer to as DIMO). Our intent is to operate this entity as a Decentralized Autonomous Organization ("DAO") where holders of the $DIMO token can generate and vote on proposals that control DIMO. There are no self-imposed restrictions on what the DIMO community is able to vote on and do. We expect that some of the key activities of the DIMO foundation will include:
  1. 1.
    Designing, deploying, and adjusting rewards pools for drivers and referral bonus programs;
  2. 2.
    Allocating authority and resources to subDAOs (called dTeams) and individuals via streams, grants, and bounties. This may fund work such as: building the decentralized data storage infrastructure; determining the optimal method by which vehicle data will be priced and sold; building applications on top of DIMO; and DBC decoding to expand the number of supported vehicles;
  3. 3.
    Whitelisting third-party hardware suppliers who build the devices that sign and stream data; and
  4. 4.
    Investing the treasury.

Foundation Design

The designs of different DAOs in the industry vary widely. DIMO’s initial structure aims to maximize practicality and efficiency without compromising decentralization, alignment, and security. On the spectrum of DAOs that, on one side are completely flat and vote on everything at the DAO level to DAOs that, on the other side rely on stewards, subDAOs, and delegation to simplify operations, we'll skew towards the latter.
We’ll seed the initial structure of DIMO so that it will:
  1. 1.
    Make it natural and easy for token holders to delegate their voting power to stewards if the don’t have the time or context to vote themselves (similar to Gitcoin and ENS);
  2. 2.
    Establish special responsibilities for the stewards who reach a certain threshold of delegated voting power (similar to Element and their GSC);
  3. 3.
    Delegate authority and resources so that work can get done faster in dTeams (similar to Yearn and their yTeams);
  4. 4.
    Utilize a proposal documentation and review structure (similar to the one robsolomon.eth designed at ConsenSys) for defining the plans, needs, and risks of dTeams;
  5. 5.
    Introduce time delays before voting execution to allow users and the DAO to exit or intervene (similar to Compound);
  6. 6.
    Utilize best in class tools such as Open Zeppelin Governor, Collab.Land, Snapshot, Tally, and more to organize transparent and programmatic collaboration; and
  7. 7.
    Operate as an offshore non-profit foundation to limit liability for DAO participants, simplify tax compliance, and execute contracts in the physical world. Such foundations tend to have administrative costs between $30,000 and $50,000 per year, which would need to be paid out of the DAO's treasury.
After it’s launched, DIMO foundation will be responsible for upgrading itself and tweaking this structure. We’re paying attention to the ideas expressed by Vitalik, Element, and others on improving votingβ€” when feasible, we expect to implement voting vaults, hybrid NFT/$DIMO voting, and quadratic voting.
Our team also considers the unique and existing governance processes around mobility that we’ll need to interact with. Everything from a 100-year-old automaker to a state DMV will need to interact with our platform, and we’re respectful of the fact that transportation is already quite decentralized.
Our vision is to build a community of people who can reshape mobility - the physical act of moving people and goods around. This is a different challenge than building purely digital projects, and if successful, we will help bring many millions more people into the web3 world.