License Approval Template
Last updated
Last updated
Headline: One sentence headline
Author: Name
Submitter(s): Name [0x Address]
Status: Review
Voting URL: Pending
Discussion Forum: #🗳️governance forum
Vote Type:
This is a slightly longer 3-5 sentence summary of the proposal.
This explains the rationale and goals for the DIP.
The highly detailed description of the DIP including precise terms, protocol updates, blockchain transactions and smart contract code that will be executed with comments, and more.
The following components of the specification do not necessarily need to be in this exact order of format, but all should be covered.
Please list all requested licenses: Integrations Provider (Hardware); Integrations Provider (Software); and/or Node.
At minimum, please include legal name, DBA, website, address, entity type (non-profit, C Corp, LLC), major owners, and contact details.
Describe the revenue share between the applicant and DIMO Network if applicable. For example, if applying to be a Node that sells user data, what percentage of revenue will the applicant keep and what percentage will go to the user?
This should be the longest section. Please describe the technological specifications of the product or service. This is particularly important for hardware manufacturers, and should include device specifications and certifications.
How would the applicant ensure the safety of the DIMO User and their data? How is data securely stored and encrypted? What is being tracked and who has access?
Is the applicant making any commitments to the DIMO network? A commitment to a certain service levels, production quantities, pricing, or anything else relevant.
A description of the implementation procedure that would follow if the DIP achieves a successful vote.
Please cite this document as:
Any changes made while the DIP is the Review stage must be summarized in this section including the date and time of the change.
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
Author, "Title", no. DLP #, Month Year. [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.