Biochar Utilization in Soil & Non-Soil Applications
Durable carbon storage by producing biochar and applying it to soils and materials.
- Registry
- VCS
- Sector
- Biochar
- Credit
- VCU-BCR · tCO₂e
- Issued as
- org.hypercerts.claim.activity
The issued hypercert is a batch of VCU-BCR credits recorded at once, comparable to a registry issuance batch. It carries weighted contributors, a work scope and a rights record, so any app in the ATProto Collective Funding Ecosystem can read it natively.
Overview
VM0044 quantifies carbon dioxide removals from converting waste biomass into biochar at new biochar production facilities. Eligible uses of the biochar include soil applications such as croplands and grasslands, and non-soil applications such as biochar-amended concrete and other building materials. The methodology is applicable globally and credits the durable carbon stored in biochar. Each credit, issued as a Verified Carbon Unit, represents one tonne of carbon dioxide equivalent removed.
Sources: methodology document · Verra Verified Carbon Standard
01 · Roles
Standard Registry
role · registry
Owns the policy, approves participants, anchors each issuance to its evidence.
Project Proponent
role · proponent
Registers the project and submits monitoring reports.
Validation & Verification Body
role · vvb
Independently validates the design and verifies monitored data.
02 · Policy graph
10 nodesThe workflow as an explicit directed graph. In Graph each column is one role, so you can see who acts at each step; every node names the org.broadlistening.policy.block.* def it resolves to plus its input and output record. Data flow switches to a lineage view that makes explicit what data each node needs and makes, with dependency arcs tracing every record back to the node that produced it. Hover to trace, click to inspect; revise edges (dashed) send work back.
Hover to trace · click to inspect
Issue credits
Standard RegistryA hypercert batching the credits issued for the period, anchored to the bundle.
- Lexicon
- org.broadlistening.policy.block.issue
- Input
- org.hypercerts.collection + the computed total
- Output
- org.hypercerts.claim.activity
Node kinds in this graph
- Role selectorg.broadlistening.policy.block.roleSelect
- Request documentorg.broadlistening.policy.block.requestDocument
- Revieworg.broadlistening.policy.block.review
- Persistorg.broadlistening.policy.block.persist
- Computeorg.broadlistening.policy.block.compute
- Aggregateorg.broadlistening.policy.block.aggregate
- Issue hypercertorg.broadlistening.policy.block.issue
- Provenanceorg.broadlistening.policy.block.provenance
control-flow event
revise (sends back)
03 · Generated lexicon records
The records this methodology compiles to, ready to write to a PDS. The first tabs are the new policy engine records; the ★ claim.activity tab and those after it are reused ATProto Collective Funding Ecosystem records (org.hypercerts.*): the issued hypercert batch, its rights, an example verification attachment and a retirement receipt.
org.broadlistening.policy.methodology/vm0044
{
"$type": "org.broadlistening.policy.methodology",
"code": "VM0044",
"name": "Biochar Utilization in Soil & Non-Soil Applications",
"registry": "Verra Verified Carbon Standard (VCS)",
"sector": "Biochar",
"creditType": "removal",
"status": "active",
"version": "1.0",
"scopes": [
"Carbon removal"
],
"roles": [
{
"id": "registry",
"name": "Standard Registry",
"permission": "Owns the policy, approves participants, anchors each issuance to its evidence."
},
{
"id": "proponent",
"name": "Project Proponent",
"permission": "Registers the project and submits monitoring reports."
},
{
"id": "vvb",
"name": "Validation & Verification Body",
"permission": "Independently validates the design and verifies monitored data."
}
],
"schemas": [
"at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.schema/vm0044-project-design",
"at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.schema/vm0044-monitoring-report"
],
"graph": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.broadlistening.policy.graph/vm0044",
"issuesAs": "org.hypercerts.claim.activity",
"workScope": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.workscope.cel/vm0044-scope",
"rights": "at://did:plc:bl0adl1sten1ngp0l1cyreg/org.hypercerts.claim.rights/vm0044-rights",
"createdAt": "2025-01-01T00:00:00.000Z"
}04 · Schemas
Project Design Document
schema · project-designDescribes the Biochar project, baseline scenario and monitoring plan.
| Field | Type | Req | Description |
|---|---|---|---|
| projectTitle | string | ✓ | Human-readable project name. |
| proponentDid | ref | ✓ | DID of the project proponent. |
| country | string | ✓ | ISO-3166 host country. |
| baselineScenario | string | ✓ | The most plausible scenario absent the project. |
| estimatedAnnual | number | ✓ | Estimated annual abatement (tCO₂e). |
| crediting | string | ✓ | Crediting period (ISO-8601 interval). |
Monitoring Report
schema · monitoring-reportPeriodic measured data used to quantify the abatement claimed.
| Field | Type | Req | Description |
|---|---|---|---|
| project | ref | ✓ | strongRef to the registered project document. |
| period | string | ✓ | Monitoring period (ISO-8601 interval). |
| measured | array | ✓ | Parameter readings with units and sources. |
| netAbatement | number | ✓ | Net verified abatement for the period (tCO₂e). |
More from VCS