The details and rationale for the initial token distribution
$DIMO is an ERC-20 token on the Polygon and Ethereum blockchain with a 1,000,000,000 token supply. For more on how to add it to your wallet and move it between chains, click here.
The total supply of 1,000,000,000 $DIMO has been allocated in a manner that lines up with industry average allocations for protocol rewards, the treasury, the initial team, and initial capital partners. A community-first approach is important, which is why we’re allocating an above average 70% of tokens to users and the treasury.
The DAO Treasury
700,000,000 $DIMO will be initially allocated to the community controlled DAO treasury. Teams and individuals that contribute to the network may receive $DIMO (and/or other cryptocurrency that the treasury accumulates) in the form of bounties or grants. However, the way most users will earn tokens is through driver rewards.
With DIP-2: Baseline Issuance, the community earmarked 450,000,000 out of the the 700,000,000 $DIMO treasury to incentivize drivers with Baseline Issuance. The initial airdrop was effectively a large distribution of Baseline Issuance and leaves 382,491,185 $DIMO. This pool will be distributed over 40 years by issuing 1,105,000 $DIMO to users per week for the first year, with issuance decreasing by 15% each year.
The remaining 300,000,000 $DIMO has been allocated to the initial team (roughly 224,000,000) and investment partners (roughly 76,000,000). These allocations are subject to a minimum two year lock up starting, from the date of the mainnet launch, whereby tokens unlock monthly until fully unlocked after three years. Team members may be subject to additional vesting on top of the lockup. Any tokens held by the company, Digital Infrastructure Inc., may also be used for network participation (e.g., paying 50 $DIMO to mint devices) or as incentives for non-team contributors (e.g., sending a small amount of $DIMO to those who show up to public community calls, posting bounties for tweeting about DIMO, etc.).
*This page is making no binding representations. See Disclaimer.