# Dovu Methodologies (Agre Calc & Cool Farm)
On this page you'll find:
* [Dovu IWA Policies](#dovu-iwa-policies)
* [Understanding Dovu's Process](#understanding-dovus-process)
* [Workflow Diagram](#workflow-diagram)
* [Policy Guide](#policy-guide)
## Dovu IWA Policies
DOVU has leveraged the IWA VEM specification for the carbon token lifecycle by delivering an auditable process, focused on MRV and capturing proofs in the audit trail tied to individual actors that have been validated and verified. These actors have unique keys, which they use to sign every transaction following W3C Decentralized Identifier (DID), Verifiable Credential (VC), and Verifiable Presentation (VP) standards and linking them to a native Token using the Hedera Hashgraph public DLT and Hedera’s Guardian, an open source reference implementation of the IWA’s Voluntary Ecological Markets Standards.
## Understanding Dovu's Process
The first step towards compliance was building a system to support manual attestations for an MRV. To mitigate the risk of manually attested data, DOVU supports attestation from multiple sources, as well as verification of the manual data by a 3rd party verifier. In addition, in order to reduce the risk of actors carrying the risk of manual data, DOVU is building a collateral mechanism that would be tied to these actors to serve for insurance purposes.
## Workflow Diagram
## Policy Guide
Step 1: We need to import the Dovu's Policies : [AgrecalC](https://github.com/hashgraph/guardian/tree/main/Demo%20Artifacts/Dovu/policies/Agrecalc%20MRV/v2) or [Cool Farm tool ](https://github.com/hashgraph/guardian/tree/main/Demo%20Artifacts/Dovu/policies/Cool%20Farm%20Tool%20MRV/v2)through three ways:
For testing purpose, we will just perform **Import from file** option and clicked on Import button.
Step 2: As we can see, this policy needs three roles: Standard Registry, Registrant, Verifier. We need to create more two roles other than Standard Registry by sending invite through Tenant.
Step 3: Once the roles are created, we will publish the policy.
Step 4: Now, we will logout and login as a Registrant role and click on Go on the respective policy:
Step 4 : Once clicked on Go, we need to select Registrant role in the drop down as shown below:
Step 5 : We need to fill the Registrant Application form and click on OK as shown below:
for AgrecalC, we get the below form:
for Cool Farm, we see below form:
Once submitted, it is waiting for Standard Registry to approve it.
Step 6 : Now we log out and login as Standard Registry, once viewing the registrant documents, we approve the application by clicking on Approve button.
Step 7 : Once approved, we again login back as Registrant and submit Farm Registrant form by clicking on Create Farm button:
Once filled and clicked on OK, Registrant waits for approval from Standard Registry:
Step 8: Now we login as Standard Registry and click on Farm Projects tab, we can see the Request being submitted by Registrant for Approve/Reject
For testing purpose, we will approve the farm project.
Step 9: Once SD approves,we login back as Registrant and submit AgreCalc Document by filling out the form:
For Cool Farm Tool methodology, you will see the below request form:
Step 10: Once the Request is submitted, Registrant is waiting for it to be approved by Verifier.
Step 11 : Now we logout and login as Verifier, we verify the documents by clicking on approve.
Step 12: Once approved, we login as SD and check the Token History by clicking on Token History Tab:
Step 13: We can also check the TrustChain by clicking on View TrustChain button:
