🏭VM0044 Methodology for Biochar Utilization in Soil and Non-Soil Applications
Table of Contents
Need and Use for the VM0044 Policy
Introduction
In the realm of sustainable practices, VM0044 emerges as a methodology designed to reduce biomass waste through biochar production. As the world grapples with pressing environmental concerns, particularly the need to address carbon dioxide removal and reduce greenhouse gas (GHG) emissions, VM0044 represents an innovative approach under the Verra Verified Carbon Standard (VCS). It focuses on the transformation of waste biomass into biochar, a strategy that has potential in mitigating climate change.
The urgency to combat the rising levels of atmospheric carbon dioxide and GHG emissions necessitates methodologies like VM0044. This methodology is centered around waste biomass management, introducing a methodology for quantifying emissions and assessing the GHG benefits of converting biomass into biochar. The responsible management of waste biomass is crucial as its improper handling can lead to substantial emissions, contributing to the greenhouse effect. VM0044 promotes the utilization of biochar in various applications, preventing emissions and simultaneously harnessing the potential of biochar as a valuable resource.
VM0044's framework is strengthened by a suite of methodological tools aimed at ensuring precise emission calculations. These tools, including "Tool to calculate project or leakage CO2 emissions from fossil fuel combustion," "Tool to calculate baseline, project and/or leakage emissions from electricity consumption,” and “Tool to calculate project and leakage emissions from transportation of freight” provide the necessary schemas and parameters for accurate assessments. These tools play a role in calculating baseline emissions, project emissions, leakage, and emission reductions, making VM0044 a comprehensive approach to sustainable waste biomass management.
Moreover, VM0044 recognizes the environmental risks associated with traditional waste biomass handling practices. In scenarios where waste biomass is left to decay or combusted without energy recovery, substantial GHG emissions can occur, with far-reaching implications for the environment. By adopting the VM0044 methodology, with their specific conditions and monitoring parameters, the release of GHGs into the atmosphere can be mitigated. This methodology not only ensures GHG reduction but also demonstrates a commitment to sustainable development by merging environmental stewardship with innovative waste biomass management practices.
Need and Use for the VM0044 Policy
Excess waste biomass has become a significant global concern due to inefficient waste management practices and the rising demand for energy and resources. When waste biomass is not properly managed, it decomposes and releases substantial greenhouse gases (GHGs), primarily carbon dioxide, into the atmosphere. This exacerbates the greenhouse effect, contributing to global climate change and environmental degradation. The improper disposal of waste biomass can also lead to contamination and harm local ecosystems. Addressing waste biomass management has become a pressing need, and Verra's VM0044 methodology provides a practical solution that underscores the importance of sustainable waste biomass management and carbon sequestration.
VM0044's approach goes beyond waste biomass management to offer a comprehensive strategy for mitigating GHG emissions. By converting waste biomass into biochar, this methodology prevents unnecessary carbon emissions and repurposes waste as a valuable resource for various applications. This dual benefit not only tackles the issue of excess waste but also contributes to reducing GHG emissions, marking a significant step towards sustainability and addressing climate change on a global scale.
Furthermore, this methodology is now available in a digital format on the Guardian, enhancing the convenience and efficiency of data input, emissions calculations, and emission reduction processes. The Guardian's platform ensures the transparency and auditability of each step in the process.
Within this digital methodology, users will use a collection of Clean Development Mechanism (CDM) methodological tools that aid in the calculation and management of emissions, including tools for calculating emissions from fossil fuel combustion, electricity consumption, and emissions from transportation of freight. The presence of these digital tools within The Guardian not only streamlines the management of waste biomass and reduces greenhouse gas emissions but also guarantees that the data is readily comprehensible and reusable, eliminating the need for extensive alterations for each project.
Demo Video
Policy Workflow
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252F13SJEiyS0VDC4EjHiKy1%252Fimage.png%3Falt%3Dmedia%26token%3D2fe0d801-4e9e-4c62-aa6f-470d68a925a3&width=768&dpr=4&quality=100&sign=6892101d&sv=1)
Policy Guide
This policy is published to Hedera network and can either be imported via Github (.policy file) or IPFS timestamp.
Available Roles
Project Proponent - The project proponent is responsible for executing the emission reduction project. The project proponent must adhere to the requirements outlined by Verra’s VCS program and provide evidence of the emission reductions achieved. Upon successful verification, the project proponent receives Verified Carbon Units (VCU) as an incentive for their emission reductions.
Verification and Validation Body (VVB) - The VVB plays a critical role in independently verifying and validating the project data submitted by the project proponent. They thoroughly assess the project's emission reduction potential, methodologies, and adherence to the policy guidelines. Based on their evaluation, the VVB either approves or rejects the project for registration.
Registry (Verra) – With Verra as the registry they take on responsibilities that encompass project intake, pipeline management, and final review of project descriptions and monitoring reports. This process ensures that emission reduction projects meet the highest standards before tokens are issued.
Important Documents & Schemas
Project Description - Project Proponent information, standard project information, methodology information like baseline emissions, project emissions, etc.
Emissions Reduction – Schema included within the project information form; this is filled out by the project proponent to calculate annual emission reductions. Monitoring Report – The monitoring report is to be filled out based on the monitoring plan mentioned within the methodology.
Tools Referenced
Methodological Tool 03 - Tool to calculate project or leakage CO2 emissions from fossil fuel combustion.
Methodological Tool 05 - Baseline, project and/or leakage emissions from electricity consumption and monitoring of electricity generation.
Methodological Tool 12 - Project and leakage emissions from transportation of freight.
Token (Verified Carbon Unit)
Verified Carbon Unit (VCU) credits, each equivalent to one tonne of CO2.
Step by Step
Login as a standard registry and you will be able to see tabs as shown below:
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FaAXd30jAC16WyqaEnq7i%252Fimage.png%3Falt%3Dmedia%26token%3Dd4d49698-e08a-43ca-9379-8243036a45c7&width=768&dpr=4&quality=100&sign=de557f8b&sv=1)
Create a new user and assign role as Project Proponent.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FNN4pY5Jo39tqHFi2RD3N%252Fimage.png%3Falt%3Dmedia%26token%3D30647ca8-389a-4d3d-ad41-3c267bfbefb7&width=768&dpr=4&quality=100&sign=cbb0620d&sv=1)
Create a New project by clicking on "New Project" button and enter all the required details.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252Fd9jfjyK9iAK2BSp6cPcf%252Fimage.png%3Falt%3Dmedia%26token%3D22da66ae-7796-4cf7-854f-5357e53d4883&width=768&dpr=4&quality=100&sign=d371b9c7&sv=1)
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FokyObTj2lUs8T3W4YMHn%252Fimage.png%3Falt%3Dmedia%26token%3D46a1772a-b440-48e4-b49d-3106a570b2b4&width=768&dpr=4&quality=100&sign=c4a05146&sv=1)
Once project details are submitted, Verra waits for its approval
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FauIvNmZHG1HqFAAd00zd%252Fimage.png%3Falt%3Dmedia%26token%3D1430beca-e2f0-4a33-87c9-69343070ec65&width=768&dpr=4&quality=100&sign=ee06f74c&sv=1)
Now, we create a new user and assign its role as VVB
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FA4DqzLijzIHUGaXSYCkG%252Fimage.png%3Falt%3Dmedia%26token%3D07c9a08b-cdd3-4983-b83a-94ccac4e9716&width=768&dpr=4&quality=100&sign=ce98a36b&sv=1)
We need to set VVB name
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FmePIwvodQTWk3nBS0nWB%252Fimage.png%3Falt%3Dmedia%26token%3D291a9fb1-7bea-4eb4-b1ba-46d804c88f2c&width=768&dpr=4&quality=100&sign=4ca1b126&sv=1)
Once VVB name is set, it waits for SR to approve it.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FQedVMMR3uZYND1o746c0%252Fimage.png%3Falt%3Dmedia%26token%3D30624fac-948f-4d8d-930c-00c40ec78687&width=768&dpr=4&quality=100&sign=d8cac97&sv=1)
Now we login as SR and approve VVB.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FOzlaNtbQ8ztZwSvszNwj%252Fimage.png%3Falt%3Dmedia%26token%3Dc7f31438-50f8-454c-890f-466eea640485&width=768&dpr=4&quality=100&sign=70866f0&sv=1)
Once VVB is approved, SR goes to Project Pipeline tab and click on Add button
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FocismHJf6MZG5rlW9qAj%252Fimage.png%3Falt%3Dmedia%26token%3Def9866f1-faab-453c-bc7b-518c57cce957&width=768&dpr=4&quality=100&sign=7e975ec9&sv=1)
Once Project is added, it waits for validation from Verra
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252F7cpfKHLcuz6GZeEQIzLH%252Fimage.png%3Falt%3Dmedia%26token%3D4feae8d1-5682-4c21-aa9f-24f3c18ebfed&width=768&dpr=4&quality=100&sign=4867e101&sv=1)
Now we login as Verra and assign project to VVB
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252Ft8ShehTtA6c0NEtcwSm6%252Fimage.png%3Falt%3Dmedia%26token%3D140199ed-3188-40d3-ac79-e540b6256405&width=768&dpr=4&quality=100&sign=28b9a465&sv=1)
Now we login as VVB and validate the project by viewing project document details. Once validated, VVB clicks on Validate button.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FsO82KQX1HjBsOQxrNLdf%252Fimage.png%3Falt%3Dmedia%26token%3Df9770e6a-1ed0-4b35-85c9-81325ae42e86&width=768&dpr=4&quality=100&sign=d151ac6e&sv=1)
Once validated, we login as Project Proponent and Add Monitoring Report.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252Ft00fHxUESis0qV11jSGB%252Fimage.png%3Falt%3Dmedia%26token%3D1bda28e5-8215-41da-9e4c-d91cb95dd027&width=768&dpr=4&quality=100&sign=97bead73&sv=1)
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FrahmksBRTaPSzfeKwQ1A%252Fimage.png%3Falt%3Dmedia%26token%3Db2700241-bdb3-40c4-8826-9925941a8f86&width=768&dpr=4&quality=100&sign=9e6f3cf2&sv=1)
Once report is submitted, we now login as VVB and validate the monitoring report by clicking on Verify button.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FdaRfvKoTlbzzeGXKdg5r%252Fimage.png%3Falt%3Dmedia%26token%3Dc7cd5a72-68df-4b8e-87eb-82ee2a13b167&width=768&dpr=4&quality=100&sign=5543a0c4&sv=1)
Once monitoring report is validated, we login as SR and click on Mint to mint the tokens.
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FiDzMSo6ZqsiAIuvVqEs6%252Fimage.png%3Falt%3Dmedia%26token%3D1deef421-2779-4db0-9bc9-44771bb2bc0a&width=768&dpr=4&quality=100&sign=2ded178c&sv=1)
Once minting is completed, we can view tokens in Token History tab
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FJSzw6Glcmwm6FA7tfncr%252Fimage.png%3Falt%3Dmedia%26token%3D781580a7-61f9-4b96-8bcd-69e1303b3556&width=768&dpr=4&quality=100&sign=e4d5f549&sv=1)
Trustchain can also be viewed by clicking on View TrustChain button:
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252F7rgqQmdSi2zM6PmvZ7gy%252Fimage.png%3Falt%3Dmedia%26token%3Decd03cba-5406-4e37-aad9-55348644f86b&width=768&dpr=4&quality=100&sign=882d7a7d&sv=1)
![](https://docs.guardianservice.io/~gitbook/image?url=https%3A%2F%2F3006114282-files.gitbook.io%2F%7E%2Ffiles%2Fv0%2Fb%2Fgitbook-x-prod.appspot.com%2Fo%2Fspaces%252FXVOaWpJKxLZf1Tee9eCO%252Fuploads%252FxlRDb8U3yi4zOY5gKRF7%252Fimage.png%3Falt%3Dmedia%26token%3Dc02ecc9c-acc6-48b6-a1c6-0e1e60e019f5&width=768&dpr=4&quality=100&sign=afcc244b&sv=1)
Last updated