👩🌾VM0042 Methodology for Improved Agricultural Land Management
Policy developed by Envision Blockchain
PreviousVM0017 Adoption of Sustainable Agricultural Land Management, v1.0NextVM0047 Afforestation, Reforestation, and Revegetation
Last updated
Policy developed by Envision Blockchain
Last updated
For more Verra VM0042 REDD+ Methodology policy information, please visit the Envision Blockchain-contributed open-source Guardian policy page here
The Verra VM0042 methodology is used to calculate the emissions reductions and carbon storage increases that result from using improved land management practices in agriculture. It takes into account emissions from fossil fuel combustion, manure deposition, biomass burning, and nitrogen fertilizers. Improved land management practices can include reducing the use of fertilizers and tillage, improving water management, managing crop residue, planting, and harvesting cover crops, and improving grazing practices. Currently, there are 35 VM0042 projects listed on Verra’s registry and a total of 21,722,438 (tCO2e) estimated annual emission reductions.
The workflow begins with the Project Proponent submitting the project description (PD) to Verra. The project description will include ex-ante estimates of the monitoring parameters, as well as other project details to demonstrate alignment with the VCS program requirements. Verra then adds the PD and project docs to the Project Pipeline and Project Registry. Next the Validation and Verification Body (VVB) will assess and validate the PD and provide a Validation Report. Then the Project Proponent will conduct monitoring and develop a Monitoring Report, replacing the ex-ante estimates with ex-post MRV data and submit it to the VVB. The VVB then verifies the Monitoring Report and delivers a Verification Report, Verification Representation, and Verification Statement. Finally, Verra reviews the issuance request and VCUs and are issued to the Project Proponent.
In future iterations, the workflow will begin with the Project Proponent completing a questionnaire to determine the appropriate methodology, modules, and MRV requirements. Then branch functionality can enable the automatic creation of context-specific schemas.
Roles in the below Workflow Diagram are represented as follows : Project Proponent (Blue), Verra (Orange), VVB (Green)
Typically, the way we start the demonstration is by logging in as a Standard Registry.
Create a Standard Registry user if you haven't done so already.
You'll now be prompted to configure your Standard Registry account. Go through the user profile setup screen. At the last step of the user profile screen, Standard Registry users will need to fill out the Standard Registry attribute form (see screenshot below). Press Connect when finished. This will now initialize the Guardian instance on the correct Hedera Consensus Service Topics, create a DID document, create a Verifiable Credential, etc.
Now we will be creating the Policy. Click on the "Policies" tab and select "Policies." We have three ways to create policies.
The first way is to actually create the policy from scratch. The second way is to import a policy. The third way is to import a policy through our pre-loaded policies from the Guardian's open source methodology library. Importing a policy will import all schemas, tokens, and policy workflow blocks to automatically populate.
For this demo guide, we will use the "Import from Open Source" way. Click on that button and find the policy for this guide and click on the import button.
Once the policy is imported successfully, you get two options: Publish and Dry Run mode. We select the Dry Run option and select Go.
Create additional users by clicking the “Create User” button.
Once the users have been created go to each one and assign the appropriate role (i.e. Project Proponent and VVB).
Go to the Standard Registry profile and approve the VVB in the “Approve VVB” tab.
Click on the Project Proponent profile and select “New Project”.
Now, we can input all the project details and data associated with the project in the “New Project” form. In the schema Excel file, if the final CRU calculations do not result in a positive integer, selecting "Ok" after completing the form will trigger errors.
To proceed with the flow, the next step is to access the Standard Registry profile and include the project in the project pipeline. This can be achieved by navigating to the "Project Pipeline" tab and selecting the "Add" option.
Next, proceed to the Project Proponent profile and locate the "Projects" section. Then, click on the downward arrow and assign the VVB to the project.
After successfully assigning the VVB to the project, the next step is to access the VVB profile and click on the "validate" option located in the Projects tab.
Navigate back to the Project Proponent profile to complete the monitoring report. In the Projects tab select “Add Report”.
Upon selecting "Add Report", a file will open containing the project details and schemas previously filled out. Here, you can update the information based on the relevant monitoring plan provided by the methodology. After updating the information and including a project area map, you may click on "Ok" to proceed.
Once you have completed the monitoring report, please access the VVB profile and go to the monitoring reports tab. Here, you will find a "Verify" button - select that to proceed.
This is the final step in the workflow. Access the Standard Registry profile and navigate to the "Monitoring Reports" tab. Here, you will find a "Mint" button - select that to mint the tokens for this monitoring period.
By accessing the "Token History" tab, you can view the number of tokens that have been minted. Additionally, clicking on the "View TrustChain" button will allow you to view the TrustChain.
The Trust Chain view presents critical elements that are publicly available for discovery, such as token information, policy information, and all the necessary details concerning the Verifiable Credentials comprising the Verifiable Presentation. On the bottom of the screen, you will find "Cards" showcasing the Verifiable Credentials in chronological order.
