dIP-1: dGenesis Improvement Proposals

dIP-1: dGenesis Improvement Proposals


dGenesis Improvement Proposals, or dIP, are governance proposals for making changes to the dGenesis platform. They are accepted or rejected through DGV holder governance.

Format of a dIP

Each dIP should have the following sections:

  • Title
    • Should be in the format dRC-#: [insert title here] when it is in the request for comment stage, and in the format dIP-#: [insert title here] when it has been accepted.
    • Should be something short and sweet, so that people can understand what you aim to do in a glance.
  • Specification
    • What is the aspect of dGenesis you want to improve? How are things done currently?
    • What specific improvements are you proposing? It should be clear enough that anyone with the specs can implement the changes.
  • Argument for
    • Why should the proposed changes be adopted?
    • Who does it benefit? What kind of benefits?
    • How is the status quo hurting the growth of dGenesis?
  • Argument against
    • What potential downsides does your proposal have? What could go wrong?
    • Who might be hurt by this proposal? How much damage might be caused?
    • What objections might a reasonable person raise?
  • Required actions
    • What specific actions need to be taken if this proposal was accepted? Again, it should be clear enough that a developer with the specs can implement the changes.

Lifecycle of a dIP

  1. Draft
  • Draft the dIP following the guidelines.
  • It’s probably a good idea to ask a few community members to coauthor with you. Writing governance proposals is not an easy task, and having coauthors is a good way to ensure your proposal doesn’t have glaring issues before you make things public.
  • Discussing the dIP in the relevant special interest groups on Discord is also a good idea.
  1. Request for comments
  • After an dIP has been drafted, it should be published on the forum for the community to comment on it.
  • This period should last at least 7 days. This is to ensure that the general community has enough time to be aware of the proposal, learn about it and the arguments for and against it, and make an informed decision as to whether they support the dIP or not.
  1. Vote
  • After enough debating has been done, the authors of the dIP may put it up to a governance vote.
  • The vote will initially be done using Snapshot, but may be migrated to other platforms if better options arise.
  • If the vote passes, the dIP will be implemented. A passing vote must have a quorum of 50 votes and receive >50% of the total votes cast. The vote must be active for at least three days.

Argument for


Argument against


Required actions

Any new dIPs should follow the guidelines written in this dIP.


Passed with a quorum: