# DMP-3: DCP Purpose and Guidelines

**URL:** <https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186>\
**Category:** dHEDGE Meta Proposals (DMPs)\
**Created:** [August 4, 2021, 8:56pm UTC](https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186 "2021-08-04T20:56:36Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![edson](https://forum.dhedge.org/letter_avatar_proxy/v4/letter/e/aca169/32.png) [@edson](https://forum.dhedge.org/u/edson)\
**Post date:** [August 4, 2021, 8:56pm UTC](https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186/1 "2021-08-04T20:56:36Z")

</div>

| Header | Content |
| --- | --- |
| Author | Edson Ayllon ([@relativeread](https://twitter.com/relativeread)) |
| Created | 2021-8-4 |
| Status | Completed |

## Motivation

dHEDGE Capital Proposals (DCPs) are how token holders decide how large capital allocations are made. Examples include rebalancing and distribution of fees collected by the protocol and capital allocations to the Eco DAO.

## Description

DCPs go through the following stages

- Draft: Proposal made, but not voted on
- Under Review: A vote is ongoing
- Planned: Passed vote
- Rejected: Failed vote
- Completed: Capital has been deployed

To be put to vote, a post must be made in [forum.dhedge.org](http://forum.dhedge.org/). The title of the DFP must start with DCP-X, where X is the DCP number (ie. DCP-1). The DFP number must increase in order (eg. a DCP posted after DCP-1 must be named DCP-2).

Under the title should be the header. Header fields include:

- Author: Author of the proposal
- Created: Creation date in YYYY-MM-DD format
- Status: Statuses include - Draft, Under Review, Planned, Completed, Rejected

The DCP must contain the following sections:

- Motivation - The reason for allocating capital
- Description - What the capital allocation is
- Implementation - How this capital will be moved

Once the post is created in this format, it can be put up to vote. The vote must link back to the DCP, and the DCP back to the vote. The voting period must be 2 days minimum.

Discussion to DCPs happens under the same forum post of the DCP.

After a DCP passes the vote, it may be implemented. The transactions involving the DCP may be posted as a comment in the DCP.

## Vote

[Vote passed](https://gov.dhedge.org/#/gov.dhedge.eth/proposal/QmQ9tZpkakaPJrZ4LuvNaG9MbcUjMZFQRBAnNzie3KB8R6).

---

<div class="post-metadata">

**Author:** ![exponent](https://forum.dhedge.org/letter_avatar_proxy/v4/letter/e/e47774/32.png) [@exponent](https://forum.dhedge.org/u/exponent)\
**Post date:** [August 5, 2021, 3:05am UTC](https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186/2 "2021-08-05T03:05:22Z")

</div>

Strongly support this

---

<div class="post-metadata">

**Author:** ![runex](https://forum.dhedge.org/letter_avatar_proxy/v4/letter/r/e9bcb4/32.png) [@runex](https://forum.dhedge.org/u/runex)\
**Post date:** [August 12, 2021, 12:32pm UTC](https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186/3 "2021-08-12T12:32:24Z")

</div>

> [@edson](#):
>
> - l allocation is
> - Implementation - How this capital will be moved
> 
> Once the post is created in this format, it can be put u

indeed. Needs to be formalized now. I’ll rewrite my proposal in this style already.

---

<div class="post-metadata">

**Author:** ![runex](https://forum.dhedge.org/letter_avatar_proxy/v4/letter/r/e9bcb4/32.png) [@runex](https://forum.dhedge.org/u/runex)\
**Post date:** [August 12, 2021, 12:34pm UTC](https://forum.dhedge.org/t/dmp-3-dcp-purpose-and-guidelines/186/4 "2021-08-12T12:34:02Z")

</div>

It would also be nice to have a clear overview of the current state each time. Earlier on there was some discussion about this and the info is out there. It’s just no so easy to find and that complicates some stuff. This proposal will allow dhedhe dao to track allocations.