Technical Specifications for IWA Digital Measurement, Reporting and Verification (dMRV) Framework, Version 2.5 (DRAFT)

1. Background

This document presents the second major version of the Digital Measurement, Reporting & Verification (dMRV) Framework, initially published in late 2021. The InterWork Alliance (IWA) and Global Blockchain Business Council (GBBC) members have extensively shared the framework throughout the sustainability ecosystem, identifying missing elements, refining definitions, and striving to establish common standards for unifying ecological and environmental product manufacturing or origination processes, such as voluntary carbon credits. This specification supersedes its predecessor entirely due to the diligent efforts and collaboration of its contributors.

The lifecycle of environmental or ecological credits, such as carbon or renewable energy credits, includes two main phases: origination (or manufacturing) and distribution. The origination phase involves the creation or issuance of a credit from an issuing authority, comparable to commodity origination processes like agriculture or raw materials, where the work is done to grow and harvest the crop in preparation for distribution. The transition from origination to distribution necessitates different infrastructure and requirements, ranging from supporting data collection and verification during manufacturing to facilitating marketplace and exchange activities for trading and settlement. The dMRV Framework focuses specifically on the origination phase of ecological assets.

Within the origination phase, there are two sub-phases: Validation and Verification. The validation phase entails the process for a project to be validated by an issuing program before credits can be issued. This phase encompasses project design, location, plan, involved parties, governance, adjacent impacts on society, and establishing a baseline for measuring impacts. The outcome of this phase typically results in a Project Design Description (PDD) document, which serves as the official recognition and resource for project information. The validation phase is governed by the issuing registry and conducted by a Validation and Verification Body (VVB), usually validated for multiple years.

The verification phase involves subsequent monitoring of the data points outlined in the validation phase and reporting this data to the VVB for verification. The verification findings are then reported to the issuing registry, which issues a credit for the verified impact to the project. Historically, the validation phase has represented the majority of the effort for establishing projects and issuing credits, often taking a year or more to complete. This extended timeframe is primarily due to early projects being land- and nature-based, such as forestry or land use, which could not produce direct evidence of impact over short periods. Consequently, trust anchors were established based on the validation phase, with annual issuances relying on indirect evidence or factoring to calculate carbon reduction or avoidance.

Recently, environmental markets have shifted with the introduction of engineered projects and a focus on carbon removal rather than reductions or avoidances. These new technology-based solutions, such as solar, wind, or direct air capture, utilize digital sensors that produce large volumes of highly accurate and verifiable data. This shift emphasizes verification during the origination phase over project validation.

Engineered projects are typically operated by established corporate entities, have smaller land footprints, and require faster issuance times—monthly instead of annually. Engineered environmental projects, including renewable energy and carbon capture and storage, should prioritize verification over validation, reflecting the shift in trust anchors from a project’s reputation established during validation to proof of impact accurately measured in near real-time. The Digital MRV Framework is optimized for these new types of engineered projects, which generate substantial quantities of precise measurement data for verification, thereby directly proving energy output or carbon sequestration.

Currently, there are multiple open standard initiatives, such as the Carbon Data Open Protocol, aimed at unifying carbon project data from project validation and credit issuance. The Digital MRV Framework can introduce an open standard for verification and implement a new "effort scale" between validation and verification based on project type, moving away from a one-size-fits-all approach.

2. Introduction

The Digital MRV (dMRV) Framework outlines the terminology, roles, process workflows, generic evidence packaging, and attestations that digital MRV solutions should follow to create the next generation of environmental credits as digital assets. The framework establishes a common roles-based process along with an extensible data model to maintain a consistent taxonomy across infrastructure and asset classes, allowing for customization to accommodate various activities that can produce these new assets. It describes an asset origination supply chain (dMRV network), where different roles are responsible for different parts of the process.

For instance, a project developer, who performs the work generating environmental benefits, provides raw measurement data and evidence into the supply chain. The verifier then validates this evidence against a quality standard, such as methodology, ensuring its accuracy and reliability. The verifier generates a report used to issue the digital asset, such as a carbon credit, to the issuing registry.

The framework aims to support investments in and the generation of high-quality, data-backed ecological assets at scale. It specifies the entities and processes enabling the application of various standards, protocols, and technologies that can collaboratively produce high-quality projects and claims, ready for validation and verification.

This document serves as the technical specification for the dMRV Framework. It is intended for software developers, business analysts, data scientists, and others seeking to understand the data model and its entities, such as tokens, agreements, and data extensions, defined by this specification.

2.1. Status of this Document

Although this is the released Version 2.5 of the framework, comments regarding the document are welcome, for IWA members, please file issues directly on GitHub, using the dMRV label. Branching feedback can be made via pull request by branching and editing the GitHub Spec Bikeshed source directly.

Feedback from non-members is welcome via email to iwa

The technical specifications within this document are the result of consent processses by GBBC/IWA members and other external sources.

2.2. Scope

The scope of this document is to reach consensus on a tokenized orgination process that describes the behaviors, common data model, schema or data dictionary and encoding standard of the process for the IWA Voluntary Ecological Markets taskforce to represent the data entities involved in the origination process for the resulting digital assets.

2.3. Regarding the Token Taxonomy Framework

The Token Taxonomy Framework (TTF) is the IWA’s primary tool for defining an open specification for a token. It focuses on defining individual tokens but does not offer a framework for defining sets of related tokens involved in broader processes. This artifact will complement, rather than replace, the tokens defined in the TTF. The tokens and their data models from this artifact will be utilized to define the tokens within the TTF.

Token definitions will be titled as Token & Data Type to make it clear that the token is defined in the context of the data model. All other data types are considered Property Sets in the TTF.

Placing all of the token definitions and especially the data model in a single artifact makes it easier to understand the relationships and dependencies between the tokens.

Additionally, a single agreement that governs the process of origination, the Verification Process Agreement, see § 4.32 Agreement & Data Type: VerificationProcessAgreement, is defined in this artifact. This agreement is used to establish the parties and their roles in the origination process.

2.4. Intended Audience

This technical specification is for

• software developers who want to build software to edit, exchange or store data in the format defined by this specification

• business analysts who want to understand the data model and data dictionary defined by this specification

• data scientists who want to understand the data model and data dictionary defined by this specification

• anyone else who wants to understand the data model and data dictionary defined by this specification

2.5. About the Voluntary Ecological Markets Taskforce

The IWA Voluntary Ecological Markets Taskforce is a working group of the InterWork Alliance (IWA) that is focused on the develoment of standards for the creation of digital assets that represent the environmental benefits of voluntary ecological markets.

The lifecycle of these assets has two main phases: origination and distribution. The origination phase is the process of creating the digital asset and the distribution phase is the process of distributing the digital asset to the market, e.g., marketplaces, exchanges, DeFi, etc.

This document and the specifications are aimed at the origination phase of the lifecycle.

2.6. Disclaimer

While IWA encourages the implementation of the technical specifications by all entities for interoperability, those organiazations and individuals who contributed to the development of this document do not assume responsibility for any consequences or damages resulting directly or indirectly from the use of this document.

2.7. License

The license can be found in Appendix A: License.

3. Terminology

dMRV

Digital Measurement, Reporting and Verification, also a Namespace in the framework.

Accountable Impact Organization

An Accountable Impact Organization undertakes activities to achieve specific environmental outcomes measured by Activity Impact Modules (AIMs). Multiple AIMs can target different objectives, following a particular Quality Standard. For instance, an agricultural project may have separate AIMs for carbon removal and biodiversity conservation. Carbon Capture and Storage projects may have distinct modules for capture, transport, and storage phases. This structure allows the organization to manage various types of credits or organize activities into separate modules for streamlined issuance.

The encoding of an Accountable Impact Organization in the data model is specified in § 4.3 Token & Data Type: AccountableImpactOrganization

Activity Impact Module (AIM)

An Activity Impact Module, AIM, can represent a single project with all § 4.56 Data Type QualityStandard modules represented in a single AIM, or span multiple AIMs where each AIM represents a different module within a project and be grouped into a § 4.8 Data Type: ActivityImpactModuleGroup. Each AIM has a defined scope and a defined set of activities that are intended to achieve a defined set of outcomes. The outcomes of the project are typically environmental benefits and follow a spcific Quality Standard, i.e. methodology.

A AIM is scoped or bound to a quality standard/methodology that it follows along with a physical location or boundary that defines where the project activities occur. For example, a land based project would be scoped to an area/polygon on a map and an engineered sequestion based project would be scoped to a power plant/GPS/INSS.

An Accountable Impact Organization can have multiple AIMs, but there cannot be another AIM using the same benefit type/quality standard/methodology and location.

The encoding of a Activity Impact Module in the data model is specified in § 4.5 Data Type: ActivityImpactModule

Quality Standard

A quality standard is a generic term for the methodology or protocol(s) that are used to validate a project and measure, report and verify the environmental benefits of an Activity Impact Module. The quality standard may include additional project validation requirements and be composed of different combinations of tools to calculate things like Additionally, etc.

The encoding of a Quality Standard in the data model is specified in § 4.56 Data Type QualityStandard

Verification Automation

Solutions, platforms, services, etc., designed to accelerate the verification of claims. Depending on the Quality Standard, it may be able, with appropriate audit requirements, to perform full verification of claims issuance of impact credits. For other Quality Standards, these platforms or services may automate and prepare findings data that are evaluated by a VVB in order to speed up and support a continuous verification process.

Impact Claim

An impact claim is a collection of the evidence data submitted according to the quality standard being followed by the AIM for a claim period. A claim period is typically the same as the issuing cadence, i.e., monthly or annually. An impact claim is composed of one or more checkpoints.

The encoding of an Impact Claim in the data model is specified in § 4.10 Token & Data Type: ImpactClaim

Impact Claim Checkpoint

An impact claim checkpoint is a collection of the evidence data submitted periodically to an impact claim. The checkpoint is a cryptographic fingerprint of the evidence data contained within a Data Package to establish the provenance and integrity of the evidence being submitted.

The encoding of an Impact Claim Checkpoint in the data model is specified in § 4.11 Data Type: ImpactClaimCheckpoint

Data Package

A data package, is the data package file, i.e. .zip file, that contains the raw evidence data being submitted with a checkpoint.

The encoding of a Data Package in the data model is specified in § 4.12 Data Type: DataPackage

Data Package Manifest

A data package has a manifest.json file in the root of the package file that contains the metadata about the contents of the file as well as extensible metadata that is specific for the quality standard being followed.

The encoding of a Manifest in the data model is specified in § 4.13 Data Type: Manifest

Processed Claim

For each Impact Claim, there is a Processed Claim used by the Verifier to record verification outcomes. A processed claim is the Impact Claim’s corresponding collection of checkpoint results that are generated by the verifier.

The encoding of a Processed Claim in the data model is specified in § 4.30 Token & Data Type: ProcessedClaim

Checkpoint Result

A Checkpoint Result is paired with a corresponding Impact Claim Checkpoint for the claim being processed and contains the results of the verification of the checkpoint.

The encoding of a Checkpoint Result in the data model is specified in § 4.31 Data Type: CheckpointResult

Activity Impact Module Group

The ActivityImpactModuleGroup is a group of Activity Impact Modules that are grouped together to combine claims from multiple projects, potentially from different organizations, into a single group claim. A carbon credit may require several different modules and claims to be combined to create a single credit, the AIMs would be grouped together in an ActivityImpactModuleGroup, even in scenarios involving different organizations.

For example, Carbon Capture and Storage (CCS) may require a project developer to capture CO2 from a plant, then hand it off to a different organization to transport the CO2 to a storage facility, then a third organization to store the CO2. Each of these organizations would have their own AIM and claim, but only one credit will be issued for the combined claims. The AIMs would be grouped together in an ActivityImpactModuleGroup, their claims would be combined into an ClaimGroup for a single credit to be issued for the group. Since an Activity Impact Module can be a member of multiple groups, when a claim is created it must identify the Claim Group it will belong to.

The encoding of an Activity Impact Module Group in the data model is specified in § 4.8 Data Type: ActivityImpactModuleGroup

Claim Group

An ClaimGroup is a group of Impact and Processed Claim pairs that are grouped together to combine claims from multiple projects (AIMs), potentially from different organizations, into a single claim for processing.

A ClaimGroup is a member of only one Activity Impact Module Group.

The encoding of a Claim Group in the data model is specified in § 4.15 Data Type: ClaimGroup

Extension

An Extension can be an Entity, Message, Formula or Variable extension to the data model that is specific to the quality standard being followed. These extensions are used to extend the data model and process to support the specific requirements of the quality standard and can be contextually applied to the appropriate data types. For example, an Entity Extension can be applied to an Activity Impact Module to support the data requirements of a specific quality standard. An Extension Message Pair can be defined to add a process step to a claim verification for one party to request something from another and be recorded as a request/response message pair in the proper context of the business process.

Each extension must have an extension template defined in an Extension Set. There are templates for each extension type, Entity Template, Message Pair, Formula Template and Variable Template. Templates are defined in an Extension Set that is shared by all participants in the dMRV Process as a way of creating structured data and messaging to digitize the MRV Process.

To use an extension, a template must be defined first, then an extension instance can be created from the template and applied.

The encoding of an Extension in the data model is specified in § 4.23 Data Type: FormulaTemplate & § 4.24 Data Type: Formula, § 4.25 Data Type: VariableTemplate & § 4.26 Data Type: Variable, § 4.21 Data Type: EntityTemplate & § 4.22 Data Type: Entity, § 4.18 Data Type: MessagePair & § 4.19 Data Type: Message

Extension Set

An extension set is a grouping of Extension Templates that can be organized into ExtensionSetModules that is the shared library of available extensions available for use by the participants in the dMRV process.

ExtensionSets and Templates are how specific Quality Standards are digitally implemented in the framework.

The encoding of an Extension Set in the data model is specified in § 4.16 Data Type: ExtensionSet

Verification Process Agreement

A multiparty agreement between the parties involved in the origination and digital MRV process. It defines the roles, rules, quality standard and the ExtensionSet that can be used by the participants. Every dMRV origination process must have a Verification Process Agreement in place and is the rule book that governs the process.

The encoding of a Verification Process Agreement in the data model is specified in § 4.32 Agreement & Data Type: VerificationProcessAgreement

Carbon Removal or Reduction Credit - CRU

A CRU can represent either a carbon removal or reduction credit. The difference is that a carbon removal credit is a credit that is issued for the removal of carbon from the atmosphere, while a carbon reduction credit is a credit that is issued for the reduction of carbon emissions.

This is just one example of a credit definition. New types of credits can be defined and applied to the framework.

The encoding of a CRU in the data model is specified in § 4.33 Token & Data Type: CRU

4. Tokens and their Data Model

This section specifies the tokens and their data model for the entities involved in the origination process to conform with this specification.

The data model consists of the following major data types:

1. AccountableImpactOrganization: contains information identifying an individual or organization that will host one or more Activity Impact Module(s).

2. ActivityImpactModule: is parented by an Accountable Impact Organization that can have multiple AIMs and contains information identifying a project, or optionally a module for a project, that will host one or more Impact Claim(s).

3. ImpactClaim: contains information identifying a claim that will host one or more Checkpoint(s).

4. DataPackage: contains information identifying a data package that will contain evidence or processed results of verification.

5. ProcessedClaim: contains information identifying a processed claim that will host one or more Checkpoint Result(s).

6. VerificationProcessAgreement: contains information identifying a verification agreement that will host one or more Checkpoint Result(s).

7. CRU: contains information identifying a carbon removal or reduction credit. This is the cononical example of an ecological asset and can be replaced by a different asset type, e.g., biodiversity, water, etc.

8. REC: contains information identifying a renewable energy credit. This is the cononical example of an ecological asset and can be replaced by a different asset type, e.g., biodiversity, water, etc.

Of these data types, the CRU and REC are the only tokens that are traded and retired or redeemed in the system. The other data types are used to support the origination process and provide the system of record for the data that backs the asset types.

Some data types, like the DataPackage, support extensible metadata. This means that the data type can be extended to support additional data types that are specific to the quality standard being followed. For example, the DataPackage data type can be extended to support the data types required by specific methodologies or quality standards.

Not all data types defined in this artifact are tokens, but are a Property-Set which are a collection of properties grouped together that can be used or composed into other property-sets or be present in many token definitions.

4.1. Highlevel Data Model

The following diagram shows the highlevel data model for the tokens defined in this specification, including the relationships between the them. This model only includes the highlights of properties within the data types and does not include the full list of properties for each data type.

4.2. Data Model

The following diagram shows the detailed data model for this specification, including the relationships between the them. This model is quite large can be downloaded from here.

4.3. Token & Data Type: AccountableImpactOrganization

AccountableImpactOrganization is a data type which represents the individual or organization that will host one or more ActivityImpactModule(s).

This data type is used to represent a one to many relationship that can occur when an Accountable Impact Organization wishes to create multiple types of ecological assets and not have to establish an organiazational identity for each type of asset.

4.3.1. Base Token and Behaviors

The AccountableImpactOrganization has a Non-Fungilble base that has the following behaviors:

1. Transferable (t): The AccountableImpactOrganization can be transferred from one party to another.

2. Divisible (d): The AccountableImpactOrganization can be divided into multiple AccountableImpactOrganization tokens, up to 2 decimal places.

3. Burnable (b): The AccountableImpactOrganization can be burned, retired or permanently deactivated.

TTF base formula with behaviors is: [τ_N{d,t,b}]

4.3.2. Properties

An Accountable Impact Organization has the following properties:

4.4. Data Type Address

An address is a collection of address lines, city, state, postal code and country that can represent physical, legal or mailing addresses.

4.4.1. Properties

4.5. Data Type: ActivityImpactModule

A ActivityImpactModule represents the actual project work that will generate benefits. It is bound to to Quality Standard and is where claims are issued from. An AIM can represent a project as a whole, or be modularized to represent a specific part of a project and be correlated using a correlation identifier.

4.5.1. Scope of a ActivityImpactModule

Each ActivityImpactModule is scoped:

1. To a parent Accountable Impact Organization, which can host multiple Activity Impact Modules

2. Is bound or mapped to a QualityStandard that matches the AIM activities

3. Must be unique for its geographic footprint and Quality Standard

4.5.2. Properties

A ActivityImpactModule has the following properties:

4.6. Data Type: Validation

Represents the validation steps and artifacts created in the validation phase of a project. These would include Project Design Documents (PDD), etc.

4.6.1. Properties

4.7. Data Type: ValidationStep

A validation step is a single step in the validation process, a validation process can be composed of multiple steps each step can generate its own artifact like a Project Design Document.

4.7.1. Properties

4.8. Data Type: ActivityImpactModuleGroup

The ActivityImpactModuleGroup is a group of Activity Impact Modules that are grouped together in order to combine claims from multiple project, potentially from different organizations, into a single claim. A carbon credit may require several different modules and claims to be combined to create a single credit, the AIMs would be grouped together in an ActivityImpactGroup, even accross different organizations.

4.8.1. Properties

4.9. Data Type: ClaimSource

A ClaimSource is a registered source of evidence data to support a claim. A claim source can be a device like a sensor or meter, an application that collects user data or reference data like satellite imagery.

4.9.1. Properties

4.10. Token & Data Type: ImpactClaim

An ImpactClaim represents the actual project work that will generate benefits through out the claim period that is agreed to by the developer, VVB and Registry. ImpactClaims are created by a ActivityImpactModule and contains metadata about the claim period as well as a collection of checkpoints that are used to submitted project evidence that is verified by the VVB or Verification Automation.

4.10.1. Base Token and Behaviors

The ImpactClaim has a Non-Fungilble base that has the following behaviors:

1. Indivisible (~d): The ImpactClaim is indivisible, meaning it cannot be divided into multiple ImpactClaim tokens.

2. Non-transferable (~t): The ImpactClaim is non-transferable, meaning it cannot be transferred to another parent Accountable Impact Organization/AIM.

3. Delegable (g): The ImpactClaim can have certain behaviors delegated to another party.

4. encumberable (e): The ImpactClaim can be encumbered by a third party, typically the verification automation or VVB.

5. ProcessedClaimControl (PCC): The ImpactClaim also has this Behavior-Group with a set of behaviors a bundled and configured to control the processing of the ImpactClaim.

   • Mintable (m): The ImpactClaim can be minted, i.e., created, by the parent ActivityImpactModule.

   • Roles (r): The ImpactClaim can have roles assigned to it, i.e., the VVB, Verifier, etc. that has the ability to burn or retire the claim after processing has completed.

   • Burnable (b): The ImpactClaim can be burned, i.e., retired, by the VVB or Verifier.

TTF base formula with behaviors is: [τ_N{~d,~t,g,e,PCC}]

4.10.2. Properties

4.11. Data Type: ImpactClaimCheckpoint

The impact claim checkpoint is a collection of evidence that is submitted by the developer to support the claim. The VVB or verification automation will review the evidence and provide a status of the evidence in a corresponding CheckpointResult in the processed claim.

Checkpoints are used to periodically submit evidence on an agreed upon basis from the ActivityImpactModule to the VVB or verification automation. This enables the development of continous verification of the project and the ability to provide feedback to the developer on the status of the project and the evidence submitted before the end of the claim period.

4.11.1. Properties

4.12. Data Type: DataPackage

A data package is an index and metadata file that is stored in the root of the DataPackage file that is submitted with a checkpoint. It contains meta data about the evidence files contained in the package as well as extensible MRV data that is specific to the Quality Standard/Methodology the AIM is bound to.

4.12.1. Properties

4.13. Data Type: Manifest

The Data Package has a manifest.json file that is an extensible JSON object that contains the metadata about the contents in the Data Package. The manifest contains a list of files that are contained in the Data Package and the metadata about the files. The manifest also contains extensible MRV data that is specific to the Quality Standard/Methodology the AIM is bound to.

4.13.1. Properties

4.14. Data Type: DataFile

A DataFile is a set of metadata about an evidence file contained within the Data Package.

4.14.1. Properties

4.15. Data Type: ClaimGroup

An ClaimGroup is a group of Impact and Processed Claim pairs that are grouped together in order to combine claims from multiple projects (AIM), potentially from different organizations, into a single claim for processing.

4.15.1. Properties

4.16. Data Type: ExtensionSet

A collection of Extensions (Entity, Message, Formula or Variable) and Modules that are specific to the Quality Standard/Methodology the AIM is bound to, typically comprosised of multiple MRV Extensions for modules or activities. A ExtensionSet can be defined by the supplier, verifier and issuer based on a set of methodology modules to form reusable libraries for the MRV process for all parties.

4.16.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.16.2. Properties

4.17. Data Type: ExtensionSetModule

A MRV Extension St Module is a collection of MRV Extensions that are specific to the Quality Standard/Methodology the AIM is bound to, typically comprosised of multiple MRV Extensions for modules or activities. A ExtensionSetModule, categorizes MrvExtensions into modules like, "Carbon Capture", "Carbon Sequestration", "Carbon Removal", etc.

Templates for Entity Extensions, Messages, Formulas and Variables defined at the module level can only apply to the module and its child modules.

4.17.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.17.2. Properties

4.18. Data Type: MessagePair

A Extension Message Pair is a defined set of Request and Response messages that used to communicate and drive MRV Process between the parties involved in the MRV process, i.e., the supplier, verifier, issuer.

4.18.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.18.2. Properties

4.19. Data Type: Message

A Extension Message is a defined message that is used to communicate and drive MRV Process between the parties involved, i.e., the supplier, verifier, issuer. It is recommended that these messages use Apache Avro and Json Schema to define the message structure, content and serialization.

4.19.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.19.2. Properties

4.20. Data Type: AnyData

Any data is used to represent a custom message type defined for Extensions. If the message is defined in a protocol buffer, the message will be serialized to protoData and the remaining fields will be null. If other serialization, a dataType can use a custom class or json schema to define the message type and the value will be serialized to value.

4.20.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.20.2. Properties

4.21. Data Type: EntityTemplate

An Entity Extension Template is an extensible object (JSON, proto, etc.) that contains custom data that is specific to a Quality Standard/Methodology Entity. Entity Extension Templates can be defined by the methdology developers or the verifier, or verification automation to include attributes or data that is helpful to have on the ledger. entityTemplates are used to create Entity instances and add to most entity types, i.e., ActivityImpactModule, ImpactClaim, and ProcessedClaim types.

The Entity Extension Template is defined and added to a ExtensionSet with an accompanying schema. The ExtensionSet is a part of the VerificationProcessAgreement and is used by participants to define the MRV process and data that is required for the verification process.

4.21.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.21.2. Properties

4.22. Data Type: Entity

An Entity Extension is an extensible object (JSON, proto, etc.) that contains custom data that is specific to a Quality Standard/Methodology Entity. Entity Extensions are an instance of an EntityTemplate and can be added to most entity types, i.e., ActivityImpactModule, ImpactClaim, and ProcessedClaim types. An Entity Extension is used to add custom data to the entity that is not part of the core schema.

Entity Extensions are defined and reference their EntityTemplate and added to a ExtensionSet with an accompanying schema. The ExtensionSet is a part of the VerificationProcessAgreement and is used by participants as the repository of extensions used for the Quality Standard/Methodology.

4.22.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.22.2. Properties

4.23. Data Type: FormulaTemplate

A Formula Template is a formula that is used to calculate the MRV data for a Quality Standard/Methodology. Formula Templates are composed into ExtensionSet and are used to calculate the MRV data for the Quality Standard/Methodology. A Formula is an instance from a Formula Template that is used to calculate the MRV data for a Quality Standard/Methodology and is applied to an ActivityImpactModule.

4.23.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.23.2. Properties

4.24. Data Type: Formula

A Formula is an instance of a FormulaTemplate that is used to calculate the MRV data for a Quality Standard/Methodology. Formulas are applied to an ActivityImpactModule and are used to calculate the MRV data for the Quality Standard/Methodology. Formulas are composed of Variables that are used to calculate the MRV data for the Quality Standard/Methodology and are applied to entities like a ActivityImpactModule.

4.24.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.24.2. Properties

4.25. Data Type: VariableTemplate

A Variable Template is a variable that is used in a Formula Template to calculate the MRV data for a Quality Standard/Methodology. Variable Templates are composed into FormulaTemplate and are used to calculate the MRV data for the Quality Standard/Methodology.

A Variable is an instance from a Variable Template that is used to calculate the MRV data for a Quality Standard/Methodology and is applied to entities like a ClaimSource.

4.25.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.25.2. Properties

4.25.3. Data Type: VariableTemplates

A collection of VariableTemplate objects that are used in a Extension Sets and Claims.

4.26. Data Type: Variable

A Variable is an instance of a VariableTemplate that is used to calculate the MRV data for a Quality Standard/Methodology. Variables are used in Formula Templates to calculate the MRV data for the Quality Standard/Methodology. Variables are applied to entities like a ClaimSource or ImpactClaimCheckpoint.

4.26.1. Namespace

The ExtensionSet is a part of the dmrv namespace.

4.26.2. Properties

4.27. Data Type: Variables

A collection of Variable objects that are used in a Extension Sets and Claims.

4.28. Extension Schema File: ExtensionDefinition

MRV extensions MAY define a valid JSON Schema document according to the JSON Schema specification. The extension schema file defines the data encoding and syntactical data validation details.

Authors of extension schema definitions SHOULD attempt to add as many validation rules as possible such that data validation can be automated as much as possible.

Extension schemas SHOULD be defined in a way to make illegal extension representations unrepresentable.

Additional details which are not representable in JSON Schema such as data semantics or validation rules, MUST be defined in the extension documentation (§ 4.29 Extension Documentation: ExtensionDocumentation).

4.29. Extension Documentation: ExtensionDocumentation

The extension documentation is a human-readable document that describes the extension in detail. Extension document MUST be written in English. The documentation CAN be offered as a translation in other languages as well.

The documentation MUST include:

1. Version of the extension and the document. The value MUST be a string in the format major.minor.patch as defined in Semantic Versioning 2.0.0.

2. If the extension was updated, the document MUST include a changelog. The changelog MUST contain a summary of the changes between subsequent versions.

3. A description of the extension, including the business case addressed by the extension and the business value gained by extending the Pathfinder Data Model. 2.1 This includes methodological alignment of the extension, especially covering the alignment with the Pathfinder Framework if applicable.

4. A public URL to the § 4.28 Extension Schema File: ExtensionDefinition.

5. A license declaration covering the documentation, the extension schema file, and their use.

6. Electronic contact information on how to get in touch with the authors and maintainers of the extension.

4.30. Token & Data Type: ProcessedClaim

The verification automation or VVB creates a ProcessedClaim at the beginning of verification to track the verification process and support continous verification. A ProcessedClaim is paired with an ImpactClaim and also contains a collection of CheckpointResults where results for each checkpoint verified are recorded.

4.30.1. Base Token and Behaviors

The ProcessedClaim has a Non-Fungible base with the following behaviors:

1. Indivisible (~d): The ProcessedClaim is indivisible, meaning it cannot be divided into multiple ImpactClaim tokens.

2. Non-transferable (~t): The ProcessedClaim is non-transferable, meaning it cannot be transferred to another parent Accountable Impact Organization/AIM.

3. Delegable (g): The ProcessedClaim can have certain behaviors delegated to another party.

4. CredibleClaimControl (CCC): The ProcessedClaim also has this Behavior-Group with a set of behaviors a bundled and configured to control the processing of the ImpactClaim.

   • Mintable (m): The ProcessedClaim can be minted, i.e., created, by the parent ActivityImpactModule.

   • Roles (r): The ProcessedClaim can have roles assigned to it, i.e., the Issuing Registry. that has the ability to burn or retire the claim after a credit has been issued.

   • Burnable (b): The ProcessedClaim can be burned, i.e., retired, by the VVB or Verifier.

TTF base formula with behaviors is: [τ_N{~d,~t,g,CCC}]

4.30.2. Properties

4.31. Data Type: CheckpointResult

A CheckpointResult is summary and verified links to verification results for the corresponding ImpactClaimCheckpoint. The CheckpointResult enables continous verification of the project and the ability to provide feedback to the developer during the verification process.

4.31.1. Properties

4.32. Agreement & Data Type: VerificationProcessAgreement

A VerificationProcessAgreement is an agreement between a developer, verifier and registry that defines the terms of the verification process. Shared properties of all the data entities in the validation and verification process are listed here, like the Quality Standard being used, the MRV Requirements, Claim Period, audit schedule, etc. The VerificationProcessAgreement is the indirect parent object for all the other data entities in the origination process.

4.32.1. Properties

4.33. Token & Data Type: CRU

The Carbon Removal or Reduction Unit, is a digital asset or token that services as a credit represents 1 metric tonne of CO2e. This is a non-financial, un-regulated, intangible digital asset that behavies like a commodity and is ready for distribution.

This is one example of a specific type of token or credit that can represent the ecological or environmental benefits that can be traded and retired to net down effective emissions for the beneficiary.

Other types of credits can be created, and reuse all of the other data entities for the generic validation and verification process.

4.33.1. Base Token and Behaviors

The CRU has a Non-Fungible base with the following behaviors:

1. Divisible (d): The CRU can be divided into multiple CRU tokens, up to 4 decimal places.

2. Transferable (t): The CRU can be transferred from one party to another.

3. Encumberable (e): The CRU can be encumbered by a third party, typically by a listing agent for distribution.

4. Revokable (v): The CRU can be revoked by the issuer, typically if the credit is found to be invalid, i.e., a carbon reversal event.

5. Delegable (g): The CRU can be delegated to a third party, typically by a listing agent in distribution scenarios.

6. Offsetable Supply Control (OSC): The CRU has a Behavior-Group for offseting and supply control with the following behaviors:

   • Mintable (m): The CRU can be minted by the issuer.

   • Roles (r): The CRU has a role for the issuer to be able to mint/issue and approve retirements.

   • Burnable (b): The CRU can be burned or retired by the owner, or by delegation, but requires approval by the issuer and optionaly can include other metadata like reporting period and jurisdiction.

TTF base formula with behaviors is: [τ_N{d,t,e,v,g,}]

4.33.2. Properties

4.34. Data Type: CoreCarbonPrinciples

The CoreCarbonPrinciples are a set of properties that are used to describe the carbon removal or reduction that follows the ICVCM Core Carbon Principles.

4.34.1. Properties

4.35. Data Type: Durability

The Durability properties are used to describe the durability of the carbon removal or reduction, its expected permanence, and the expected duration of the carbon removal or reduction. It includes the risk of reversal and how that risk is mitigated.

4.35.1. Properties

4.36. Data Type: Degradable

The Degradable properties are used to describe the degradation of the carbon removal or reduction.

4.36.1. Properties

4.37. Data Type: Replacement

Replacement is used when a credit is replacing a revoked credit.

4.37.1. Properties

4.38. Data Type: Co-Benefit

Co-benefits currently map to the UN SDGs and include a description for how the benefit applies.

4.38.1. Properties

4.39. Data Type: ReversalMitigation

The ReversalMitigation properties are used to describe the risk of reversal and how the risk is mitigated.

4.39.1. Properties

4.40. Data Type: PACompliance

Details about a credit’s Paris Agreement Compliance.

4.40.1. Properties

4.41. Token & Data Type: REC

The Renewable Energy Credit is an example token is a Fungible Token that represents the environmental benefits of a renewable energy project and is exchangeable for evidencing the production of electricity. The primary unit of measure for I-REC(E)s is the megawatt hour (MWh), with below megawatt hour resolution to the watt hour (Wh) as optional. Each unit of electricity is uniquely attributable to the source generation using the same project and claims process that other assets like the CRU originate from.

This is one example of a specific type of token or credit that can represent the ecological or environmental benefits that can be traded and retired to net down effective emissions for the beneficiary.

4.41.1. Base Token and Behaviors

The REC has a Non-Fungible base with the following behaviors:

1. Divisible (d): The REC can be divided into multiple REC tokens, up to 6 decimal places.

   • 1.000000 = 1MW

   • 0.001000 = 1kW

   • 0.000001 = 1W

2. Transferable (t): The REC can be transferred from one party to another.

3. Encumberable (e): The REC can be encumbered by a third party, typically by a listing agent for distribution.

4. Revokable (v): The REC can be revoked by the issuer, typically if the credit is found to be invalid, i.e., a carbon reversal event.

5. Delegable (g): The REC can be delegated to a third party, typically by a listing agent in distribution scenarios.

6. Offsetable Supply Control (OSC): The REC has a Behavior-Group for offseting and supply control with the following behaviors:

   • Mintable (m): The REC can be minted by the issuer.

   • Roles (r): The REC has a role for the issuer to be able to mint/issue and approve retirements.

   • Burnable (b): The REC can be burned or retired by the owner, or by delegation, but requires approval by the issuer and optionaly can include other metadata like reporting period and jurisdiction.

TTF base formula with behaviors is: [τ_F{d,t,e,v,g,}]

4.41.2. Properties

4.42. Data Type: ClimateLabel

A ClimateLabel is a reference to an external data element that contains a climate label, typically set by the registry or methodology.

4.42.1. Properties

4.43. Data Type: VerifiedLink

A VerifiedLink is a reference, URI or URL to an external data element along with a cryptographic fingerprint of the external data so that its integrity can be checked by any party.

4.43.1. Properties

4.44. Data Type: ReferencedCredit

A ReferencedCredit is used to hold values for credits that reference a credit on another registry, there are likely to be more fields needed here so using a property-set instead of a single field.

4.44.1. Properties

4.45. Data Type: Audits

Audits contain the audit schedule, date of last audit and the verified links to the audit reports for the verification agreement.

4.45.1. Properties

4.46. Data Type: Signatory

A Signatory is a party that has signed a document or agreement. The Signatory is a digital entity or identity in a specific role in the dMRV process.

4.46.1. Properties

Data Type: DigitalSignature

4.47. Data Type: DigitalSignature

A Signature is a digital signature of a document or agreement. The Signature is a digital entity or identity in a specific role in the dMRV process. Support for JWT and Verifiable Credentials is planned.

4.47.1. Properties

A Signature contains the following properties:

Data Type: Credential (data format, type (JWS, Verifiable Credential))

4.48. Data Type: Credential

A Credential is a digital credential that is an emerging W3C standard for Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). As implementations of the standard emerge, the dMRV specification will be updated to reflect the standard. Implementations can use the current format and type of the credential as a placeholder until the standard is finalized.

It is expected that the Credential will be a JSON Web Signature (JWS) or a Verifiable Credential (VC) as defined by the W3C Verifiable Credentials Data Model 1.0 specification and can be used to assign a DID to a party, device, source, etc. in the dMRV process. These will be used for attestations, verifications, and signatures in the dMRV process.

See W3C Verifiable Credentials Implementation Guidelines 1.0 for more information.

4.48.1. Properties

A Credential contains the following properties:

4.49. Data Type: CredentialSubject

A CredentialSubject is the subject of a Credential.

4.49.1. Properties

A CredentialSubject contains the following properties:

4.50. Data Type: Proof

A Proof is a digital proof of a Credential.

4.50.1. Properties

A Proof contains the following properties:

4.51. Data Type: VerifiablePresentation

A VerifiablePresentation is a digital presentation of a Verifiable Credential or Digital Signature that is linked to a DID or Signatory.

4.51.1. Properties

A VerifiablePresentation contains the following properties:

4.52. Data Type: Attestation

Attestations provide opportunities for context in MRV data. Conceptually, attestations can be the data within the project or the commentary around the project. For project data, “Direct Data Attestations” can come from individuals, project developers, verifiers, and/or directly from devices asserting an event that is represented digitally on the public ledger.

Attestations, metadata, or “Tags” describing digital entities, such as actors, calculations, or their quantifiable outcomes, allow for more context to exist about Accountable Impact Organizations or Impact Modules (AIM) within the market, which inherently have a relationship with credit pricing and can describe overall project effectiveness.

4.52.1. Properties

An Attestation contains the following properties:

4.53. Data Type: Tag

Are attested metadata describing digital entities, such as actors, calculations, or their quantifiable outcomes, allow for more context to exist about a data type within the market, which inherently have a relationship with credit pricing and can describe overall project effectiveness.

4.53.1. Properties

A Tag’s properties will vary based on the implementation, for example using DIDs or Verified Credentials. An example tag might have the following properties:

4.54. Data Type: MitigationActivity

The combination structure of the CCP MitigationActivity attribute.

4.54.1. Properties

4.55. Data Type: GeographicLocation

The GeographicLocation is a data type that can represent a GNSS/GPS point location for projects like a facility or building and or a geographic area, like a land project using a polygon represented as a string or file. *Either the longitude and latitude or the string or file for the area must have a value.

4.55.1. Properties

4.56. Data Type QualityStandard

The QualityStandard is a set of properties that identify the accredited standard, a methodology and any versioning information for the validation and verification process.

4.56.1. Properties

4.57. Data Type MRVRequirements

The MRVRequirements is a set of properties that identify the measurement specification, the precision of the measurement and the link to the specification. Here is where a Quality Standard can prescribe a set of Extensions to be used in the verification process.

4.57.1. Properties

4.58. Data Type: PrecisionMix

The mix of precision, by percentage, of the measurement specification used for the project. The sum of all the mixes must be 100 for 100%.

4.58.1. Properties

4.59. Data Type: DateRange

A date range contains a start and end date, with optional timestamps for precision.

4.59.1. Properties

4.60. Data Type: DatePoint

A DatePoint combines a date with an optional UTC Timestamp for precision if needed.

4.60.1. Properties

4.61. Data Type: DateString

A simple date string, i.e. "2023-01-01".

4.61.1. Json Representation

Each DateString MUST be encoded as a JSON String.

4.62. Data Type: Date

Represents a date with discrete values for month, day and year.

4.62.1. Properties

4.63. Data Type: DateTime

A DateTime is a date and time with an optional UTC Timestamp for precision if needed.

Example values:

4.63.1. JSON Representation

Each DateTime MUST be encoded as a JSON String.

4.64. Data Type: Timestamp

A Timestamp is a number of milliseconds since the Unix epoch (1970-01-01T00:00:00Z).

Example values:

4.64.1. JSON Representation

Each Timestamp MUST be encoded as a JSON String.

4.65. Data Type: ITMOId

An ITMOId is a unique identifier for an Internationally Transferred Mitigation Outcome. It is a unique composite identifier made up of 6 parts, separated by a -.

Example:

"f4b1225a-bd44-4c8e-861d-079e4e1dfd69"

{
  "id": "bef817d3-e178-402c-93bd-b20aab360e71",
  "quantity": "1.41",
  "unit": "TonneCo2E",
  "ownerId": "396a2870-851e-4c93-bd97-e330c0d2d3c1",
  "listingAgentId": "ac497050-23eb-4fac-b9e5-1ec9039b2d34",
  "coreCarbonPrinciples": {
    "assetId": "snei219123-998sdfl-sad21-1-1.41",
    "issuanceDate": {
      "dateTime": "",
      "dateString": "3/20/2025"
    },
    "vintage": "2018",
    "generationType": "Generated",
    "verificationStandard": "Puro",
    "mitigationActivity": {
      "category": "Removal",
      "method": "Technological"
    },
    "durability": {
      "storageType": "Biological",
      "years": 100,
      "degradable": {
        "percentage": 10,
        "factor": 5,
        "degradationType": "Linear"
      },
      "reversalMitigation": {
        "reversalRisk": "Material",
        "insuranceType": "BufferPool",
        "insurancePolicyOwner": "AccountableImpactOrg",
        "insurancePolicyLink": {
          "id": "a08f99d1-99cc-4ff7-804d-d7fab7be0c90",
          "uri": "https://puro.earth/mitigations/a08f99d1-99cc-4ff7-804d-d7fab7be0c90.pdf",
          "description": "Link to the Reversal Mitigation Insurance Policy",
          "hashProof": "98uuisdE12A0213az2133ASdfsdf",
          "hashAlgorithm": "Sha256"
        }
      }
    },
    "replacement": null,
    "parisAgreementCompliance": {
      "ca": "ParisAgreementCompliant",
      "letterOfApproval": {
        "id": "492be7eb-0d9a-499b-9a95-e8ed8d7e4c9f",
        "uri": "https://span.com/492be7eb-0d9a-499b-9a95-e8ed8d7e4c9f.pdf",
        "description": "Letter of Approval for Paris Agreement Compliance",
        "hashProof": "uuisdE12A0213az2133ASdfsdf",
        "hashAlgorithm": "Sha256"
      },
      "itmoId": "CA12-EU01-SP-1234500-2023-NIO"
    },
    "quantifiedSdgImpacts": [
      {
        "unSdg": "AffordableAndCleanEnergy",
        "description": "This project provides affordable clean energy to the surrounding community."
      }
    ],
    "adaptationCoBenefits": [
      {
        "unSdg": "IndustryInnovationAndInfrastructure",
        "description": "The project is contributing to the expansion of renewable infrastructure."
      }
    ]
  },
  "climateLabels": [
    {
      "id": "92252fdf-5c2d-4dc9-9a39-af6362a6b122",
      "name": "Climate Neutral",
      "description": "Climate Neutral - environmentally friendly, climate positive"
    }
  ],
  "status": "Active",
  "referencedCredits": [
    {
      "referencedCreditId": "16e029bb-8258-4721-b3ab-3d4493425151",
      "registryLink": {
        "id": "",
        "uri": "",
        "description": "",
        "hashProof": "",
        "hashAlgorithm": "Sha256"
      },
      "metadata": "serialized json data"
    }
  ],
  "appliedToReportingPeriodId": "",
  "processedClaimId": "2d17d155-ca8b-4208-8cc0-6dc3a85e2c34",
  "issuerId": "2ab239a3-63e6-42dc-a0aa-8ca26dd81cde",
  "processedClaim": {
    "id": "2d17d155-ca8b-4208-8cc0-6dc3a85e2c34",
    "vpaId": "e0d357b0-a75a-40fa-838b-5a5d444d2216",
    "impactClaimId": "a5cd2fbe-0b18-4cb7-99e8-624dc96acafa",
    "claimGroupId": "",
    "creditId": "bef817d3-e178-402c-93bd-b20aab360e71",
    "unit": "TonneCo2E",
    "quantity": "1.41",
    "coBenefits": [
      {
        "unSdg": "CleanWaterAndSanitation",
        "description": "The project was found to significantly contribute towards the communities clean water program."
      },
      {
        "unSdg": "ReducedInequalities",
        "description": "By training and employing locals, this project is reducing inequalities in the country."
      }
    ],
    "extensions": [
      {
        "id": "",
        "templateId": "",
        "data": null,
        "appliedToId": "",
        "extensionContext": "UnknownContext"
      }
    ],
    "checkpointResults": [
      {
        "id": "5eda007d-e136-4b21-8c27-9374447c0212",
        "checkpointId": "189bc8ee-b19c-4116-be65-e8ec1d0b7764",
        "processedData": [
          {
            "manifest": {
              "id": "bd199e99-14e0-4440-af99-03b78096a24b",
              "version": "1",
              "aioId": "8ce532c6-c344-4eee-90bb-13a8a19c5910",
              "aimId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
              "claimId": "2d17d155-ca8b-4208-8cc0-6dc3a85e2c34",
              "processedClaimId": "",
              "projectDeveloperId": "9c6e926f-9603-45de-9933-8af01ac45f31",
              "created": {
                "date": {
                  "dateTime": "03/20/2025 17:22:43",
                  "dateString": "3/20/2025"
                },
                "timeStamp": {
                  "seconds": 1742491363,
                  "nanos": 861642000
                }
              },
              "extensions": [
                {
                  "id": "7662b2b6-e889-49c5-956f-575bcbd9960a",
                  "templateId": "2fb3c5ea-6243-4560-83f3-30365f8c3ac9",
                  "data": {
                    "protoData": null,
                    "dataType": "",
                    "value": ""
                  },
                  "appliedToId": "bd199e99-14e0-4440-af99-03b78096a24b",
                  "extensionContext": "DataPackageManifest"
                }
              ],
              "formulas": [],
              "dataFiles": [
                {
                  "name": "Data from sensor",
                  "type": "DataBinary",
                  "description": "Primary source data from sensor.",
                  "claimSourceId": "147e7105-2333-4f5f-847c-6c984e5220dd",
                  "claimSourceAttestation": "digital_signature",
                  "extensions": [
                    {
                      "id": "41614623-8843-4bc0-8e92-6d681920543c",
                      "templateId": "a1707f69-6bdf-45d7-9f89-4475c4828633",
                      "data": {
                        "protoData": null,
                        "dataType": "",
                        "value": ""
                      },
                      "appliedToId": "bd199e99-14e0-4440-af99-03b78096a24b",
                      "extensionContext": "DataFile"
                    }
                  ]
                }
              ]
            },
            "verifiedLinkToDataPackage": {
              "id": "8403c1d7-af52-4f9b-aa5d-ea07e6e80d05",
              "uri": "https://span.com/8403c1d7-af52-4f9b-aa5d-ea07e6e80d05",
              "description": "Link to the Span Data Package",
              "hashProof": "asdflkdfs889fj3l437098asdfi",
              "hashAlgorithm": "Sha256"
            }
          }
        ],
        "dateRange": {
          "startDate": null,
          "endDate": null
        },
        "efBefore": "",
        "efAfter": "",
        "extensions": [
          {
            "id": "",
            "templateId": "",
            "data": null,
            "appliedToId": "",
            "extensionContext": "UnknownContext"
          }
        ]
      }
    ],
    "issuanceRequest": null,
    "verificationProcessAgreement": {
      "id": "e0d357b0-a75a-40fa-838b-5a5d444d2216",
      "name": "Verification Process Agreement for Concrete Plant 3341",
      "description": "Verification Process Agreement for Concrete Plant 3341, with issuer Puro and verifier SustainCERT",
      "isAimGroup": false,
      "aimOrAimGroupId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
      "signatories": [
        {
          "id": "60425f71-6d55-4875-b661-6bc1b1a4be8a",
          "name": "Puro.earth",
          "description": "Puro.earth is the world's leading platform for engineered carbon removal. Our mission is to mobilize the economy to reward carbon net negative emissions.",
          "signatoryRole": "IssuingRegistry",
          "vvbIdForAim": "",
          "signature": {
            "type": "JWS",
            "jws": "epx324jkasdf883429f2lMMm8asxdz9ZW0",
            "hasJws": true,
            "vc": null,
            "signatureCase": "Jws"
          }
        },
        {
          "id": "58827053-14ab-441d-8699-7108de68e687",
          "name": "SustainCERT",
          "description": "SustainCERT is an organization...",
          "signatoryRole": "ValidationAndVerificationBody",
          "vvbIdForAim": "",
          "signature": {
            "type": "JWS",
            "jws": "789908sa32980231ll132fsd89asdfa123",
            "hasJws": true,
            "vc": null,
            "signatureCase": "Jws"
          }
        },
        {
          "id": "9431e6b8-9601-460b-b0e3-c3da409da3de",
          "name": "Eco-Earth Forest Growth",
          "description": "Eco-Earth Forest Growth is a forest management firm that...",
          "signatoryRole": "ProjectOwner",
          "vvbIdForAim": "",
          "signature": {
            "type": "JWS",
            "jws": "1234567890asdfasdfas",
            "hasJws": true,
            "vc": null,
            "signatureCase": "Jws"
          }
        }
      ],
      "qualityStandard": {
        "name": "Puro - Carbonated Building Materials",
        "description": "Manufactured concrete-like building elements from steel slag (waste material from steel industry) instead of traditional cement. Basically, it’s CO2 negative concrete that removes more CO2 than its production emits.",
        "standard": "Puro",
        "methodologyAndTools": [
          "VcsVm0026",
          "VcsVm0009"
        ],
        "version": "1.0",
        "coBenefits": [
          {
            "unSdg": "ClimateAction",
            "description": "Climate Action, by removing carbon from the atmosphere."
          },
          {
            "unSdg": "LifeOnLand",
            "description": "Improving Life on Land, the use of the projects land to provide..."
          }
        ],
        "standardLink": {
          "id": "be062a19-133c-4626-aa2d-bcca2c510ab2",
          "uri": "https://puro.earth/carbon-removal-methods/carbonated-building-materials",
          "description": "Link to the Carbonated Building Materials",
          "hashProof": "1234567890abc12fasdfw43asdfasdf342",
          "hashAlgorithm": "Sha256"
        }
      },
      "mrvRequirements": {
        "measurementSpecification": "Iso14064",
        "specificationLink": {
          "id": "efc93244-030d-48b8-95a5-9204c45dd679",
          "uri": "https://www.iso.org/standard/70964.pdf",
          "description": "Link to the ISO 14064-3:2018 standard",
          "hashProof": "GX1234567890abc12fasdfw43asdfasdf342",
          "hashAlgorithm": "Sha256"
        },
        "precision": {
          "low": 0,
          "medium": 0,
          "high": 0
        },
        "claimPeriod": "Annual",
        "extensionSetId": "",
        "extensionSet": {
          "id": "d2935622-fd03-4b31-a8d4-7bd876d607f9",
          "name": "",
          "version": "",
          "description": "Extension Set for VerificationProcessAgreement",
          "documentation": "",
          "modules": [
            {
              "id": "",
              "name": "VM0007 REDD+ Methodology Framework Extension",
              "version": "1.6",
              "description": "Methodology specific data attributes being tracked.",
              "documentation": "",
              "entityTemplates": [
                {
                  "id": "",
                  "name": "Δ𝐶𝑊𝑃𝑏𝑖𝑜𝑚𝑎𝑠𝑠,𝑡",
                  "version": "",
                  "description": "Change in carbon stock in biomass carbon pools in the project scenario in year 𝑡 (t C y-1)",
                  "documentation": "",
                  "extensionContext": "DataPackageManifest",
                  "dataSchemaOrType": "",
                  "dataExample": ""
                }
              ],
              "messagePairs": [],
              "formulaTemplates": [],
              "variableTemplates": [],
              "parentSet": null
            }
          ],
          "entityTemplates": [
            {
              "id": "27259534-8f7c-455a-9e6d-c97ebda6077a",
              "name": "Claim Source Make and Model",
              "version": "",
              "description": "An example entity extension for a Claim Source",
              "documentation": "",
              "extensionContext": "ClaimSource",
              "dataSchemaOrType": "MeterDeviceMetadata",
              "dataExample": "'{'make': 'Samsung', 'model': 'FuSIGon G20' }'"
            }
          ],
          "messagePairs": [
            {
              "id": "8484df1c-30d2-43e4-b597-fdba979ca45e",
              "name": "Calibrate Sensor",
              "version": "",
              "description": "Sample request response message pair",
              "documentation": "",
              "extensionContext": "Checkpoint",
              "requestDefinition": {
                "protoData": null,
                "dataType": "CalibrationRequest",
                "value": "'{'deviceId': 'a21-3223a', 'sn': '324123d-23424a1FFs1' }'"
              },
              "responseDefinition": {
                "protoData": null,
                "dataType": "CalibrationResponse",
                "value": "'{'deviceId': 'a21-3223a', 'sn': '324123d-23424a1FFs1', 'status': 'OK' }'"
              }
            }
          ],
          "formulaTemplates": [
            {
              "id": "90a825b5-d2b1-41b5-ad06-a3ca099bd02e",
              "name": "Carbon Removal Formula",
              "version": "1.0.0",
              "formula": "",
              "description": "An example formula template for a Activity Impact Module",
              "documentation": "",
              "dataSchemaOrType": "CDRFormula",
              "dataExample": "CDR = Cap - Emissions * 0.1",
              "variableTemplates": []
            }
          ],
          "variableTemplates": [
            {
              "id": "49bc2d54-b46d-433c-9c9f-458d435f8d88",
              "name": "Carbon Removal Variable",
              "version": "1.0.0",
              "description": "An example variable template for a Activity Impact Module",
              "documentation": "",
              "dataSchemaOrType": "CDRVariable",
              "dataExample": "CAP = Co2Capi,m"
            }
          ]
        }
      },
      "agreementDate": {
        "dateTime": "",
        "dateString": "3/20/2025"
      },
      "estimatedAnnualCredits": "15,000",
      "auditSchedule": "Quinquennial",
      "audits": {
        "lastAuditDate": {
          "dateTime": "",
          "dateString": "3/20/2025"
        },
        "auditReports": [
          {
            "id": "424613f8-bec9-4ca0-b5ec-b6f5d4b02d8f",
            "uri": "https://sustaincert.com/audit/e0d357b0-a75a-40fa-838b-5a5d444d2216",
            "description": "Audit report for verification process agreement e0d357b0-a75a-40fa-838b-5a5d444d2216",
            "hashProof": "0xzxWW-1234567890abcdefasdf",
            "hashAlgorithm": "Sha256"
          }
        ]
      },
      "extensions": [],
      "activityImpactModule": null,
      "processedClaims": []
    },
    "impactClaim": {
      "id": "a5cd2fbe-0b18-4cb7-99e8-624dc96acafa",
      "aimId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
      "processedClaimId": "",
      "claimGroupId": "",
      "startDate": "2021-01-01",
      "endDate": "2021-12-31",
      "unit": "TonneCo2E",
      "quantity": "1.41",
      "coBenefits": [
        {
          "unSdg": "ClimateAction",
          "description": "Climate Action for this project includes: carbon removal, reduction and carbon avoidance."
        },
        {
          "unSdg": "CleanWaterAndSanitation",
          "description": "Clean Water and Sanitation for this project includes: water quality improvement, water availability and water access."
        }
      ],
      "checkpoints": [
        {
          "id": "189bc8ee-b19c-4116-be65-e8ec1d0b7764",
          "claimId": "a5cd2fbe-0b18-4cb7-99e8-624dc96acafa",
          "claimSourceIds": [
            "147e7105-2333-4f5f-847c-6c984e5220dd"
          ],
          "projectDeveloperId": "9c6e926f-9603-45de-9933-8af01ac45f31",
          "efBefore": "0",
          "efAfter": "1.41",
          "checkpointDateRange": {
            "startDate": {
              "date": {
                "dateTime": "",
                "dateString": "3/20/2025"
              },
              "timeStamp": {
                "seconds": 1742491363,
                "nanos": 865435000
              }
            },
            "endDate": {
              "date": {
                "dateTime": "",
                "dateString": "3/20/2025"
              },
              "timeStamp": {
                "seconds": 1742491363,
                "nanos": 865511000
              }
            }
          },
          "extensions": [],
          "dataPackages": [
            {
              "manifest": {
                "id": "bd199e99-14e0-4440-af99-03b78096a24b",
                "version": "1",
                "aioId": "8ce532c6-c344-4eee-90bb-13a8a19c5910",
                "aimId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
                "claimId": "2d17d155-ca8b-4208-8cc0-6dc3a85e2c34",
                "processedClaimId": "",
                "projectDeveloperId": "9c6e926f-9603-45de-9933-8af01ac45f31",
                "created": {
                  "date": {
                    "dateTime": "03/20/2025 17:22:43",
                    "dateString": "3/20/2025"
                  },
                  "timeStamp": {
                    "seconds": 1742491363,
                    "nanos": 865796000
                  }
                },
                "extensions": [
                  {
                    "id": "8500c9b9-b26d-4b05-b6fb-502171944b79",
                    "templateId": "2595f01a-9f01-44a9-9552-d611264d06f6",
                    "data": {
                      "protoData": null,
                      "dataType": "",
                      "value": ""
                    },
                    "appliedToId": "bd199e99-14e0-4440-af99-03b78096a24b",
                    "extensionContext": "DataPackageManifest"
                  }
                ],
                "formulas": [],
                "dataFiles": [
                  {
                    "name": "Data from sensor",
                    "type": "DataBinary",
                    "description": "Primary source data from sensor.",
                    "claimSourceId": "147e7105-2333-4f5f-847c-6c984e5220dd",
                    "claimSourceAttestation": "digital_signature",
                    "extensions": [
                      {
                        "id": "16b1a26d-293c-40d1-9ec6-6742aea6ecaf",
                        "templateId": "8171202d-9972-4550-aaef-98d72dbe26ac",
                        "data": {
                          "protoData": null,
                          "dataType": "",
                          "value": ""
                        },
                        "appliedToId": "bd199e99-14e0-4440-af99-03b78096a24b",
                        "extensionContext": "DataFile"
                      }
                    ]
                  }
                ]
              },
              "verifiedLinkToDataPackage": {
                "id": "8403c1d7-af52-4f9b-aa5d-ea07e6e80d05",
                "uri": "https://span.com/8403c1d7-af52-4f9b-aa5d-ea07e6e80d05",
                "description": "Link to the Span Data Package",
                "hashProof": "asdflkdfs889fj3l437098asdfi",
                "hashAlgorithm": "Sha256"
              }
            }
          ]
        }
      ],
      "extensions": [
        {
          "id": "",
          "templateId": "",
          "data": null,
          "appliedToId": "",
          "extensionContext": "UnknownContext"
        }
      ],
      "activityImpactModule": {
        "id": "d5a9cf0c-4102-4c9d-941a-408001b12147",
        "aioId": "8ce532c6-c344-4eee-90bb-13a8a19c5910",
        "isGrouped": false,
        "name": "Forest Plot 3341",
        "classificationCategory": "CarbonRemoval",
        "classificationMethod": "Natural",
        "benefitCategory": "ClimateAction",
        "projectScope": "CarbonCaptureAndStorage",
        "projectType": "CarbonCaptureAndEnhancedOilRecovery",
        "projectScale": "Medium",
        "country": "BR",
        "region": "SouthAmerica",
        "arbId": "",
        "geographicLocation": {
          "longitude": "41.40338",
          "latitude": "2.17403",
          "geoJsonOrKml": "{'type':'FeatureCollection','name':'1071','crs__type':'name','crs__properties__name':'urn:ogc:def:crs:OGC:1.3:CRS84','features__0__type':'Feature','features__0__properties__Name':'1071','features__0__properties__description':{},'features__0__properties__timestamp':{},'features__0__properties__begin':{},'features__0__properties__end':{},'features__0__properties__altitudeMode':{},'features__0__properties__tessellate':1,'features__0__properties__extrude':0,'features__0__properties__visibility':-1,'features__0__properties__drawOrder':{},'features__0__properties__icon':{},'features__0__geometry__type':'Polygon','features__0__geometry__coordinates__0__0__0':-17.44979726383285,'features__0__geometry__coordinates__0__0__1':14.6208620053651,'features__0__geometry__coordinates__0__0__2':0,'features__0__geometry__coordinates__0__1__0':-17.41480356186299,'features__0__geometry__coordinates__0__1__1':14.63868215949493,'features__0__geometry__coordinates__0__1__2':0,'features__0__geometry__coordinates__0__2__0':-17.39295299318011,'features__0__geometry__coordinates__0__2__1':14.67781171481277,'features__0__geometry__coordinates__0__2__2':0,'features__0__geometry__coordinates__0__3__0':-17.29563788678882,'features__0__geometry__coordinates__0__3__1':14.67680110195058,'features__0__geometry__coordinates__0__3__2':0,'features__0__geometry__coordinates__0__4__0':-17.17383924249105,'features__0__geometry__coordinates__0__4__1':14.59081467498821,'features__0__geometry__coordinates__0__4__2':0,'features__0__geometry__coordinates__0__5__0':-17.09360187476775,'features__0__geometry__coordinates__0__5__1':14.51585846117694,'features__0__geometry__coordinates__0__5__2':0,'features__0__geometry__coordinates__0__6__0':-17.08630514448674,'features__0__geometry__coordinates__0__6__1':14.47029974369886,'features__0__geometry__coordinates__0__6__2':0,'features__0__geometry__coordinates__0__7__0':-16.9635166358808,'features__0__geometry__coordinates__0__7__1':14.3497385970107,'features__0__geometry__coordinates__0__7__2':0,'features__0__geometry__coordinates__0__8__0':-16.94043127233231,'features__0__geometry__coordinates__0__8__1':14.28282669386156,'features__0__geometry__coordinates__0__8__2':0,'features__0__geometry__coordinates__0__9__0':-16.8524904710476,'features__0__geometry__coordinates__0__9__1':14.13282117800751,'features__0__geometry__coordinates__0__9__2':0,'features__0__geometry__coordinates__0__10__0':-16.76401571438566,'features__0__geometry__coordinates__0__10__1':13.94911098722119,'features__0__geometry__coordinates__0__10__2':0,'features__0__geometry__coordinates__0__11__0':-16.60258876944933,'features__0__geometry__coordinates__0__11__1':13.9482543830415,'features__0__geometry__coordinates__0__11__2':0,'features__0__geometry__coordinates__0__12__0':-16.35717663748357,'features__0__geometry__coordinates__0__12__1':13.94597928824933,'features__0__geometry__coordinates__0__12__2':0,'features__0__geometry__coordinates__0__13__0':-16.15567817482042,'features__0__geometry__coordinates__0__13__1':13.9444453347921,'features__0__geometry__coordinates__0__13__2':0,'features__0__geometry__coordinates__0__14__0':-15.84076599032189,'features__0__geometry__coordinates__0__14__1':13.96344759515951,'features__0__geometry__coordinates__0__14__2':0,'features__0__geometry__coordinates__0__15__0':-15.61023581159491,'features__0__geometry__coordinates__0__15__1':13.98459708145865,'features__0__geometry__coordinates__0__15__2':0,'features__0__geometry__coordinates__0__16__0':-15.51441146374702,'features__0__geometry__coordinates__0__16__1':14.03040839455136,'features__0__geometry__coordinates__0__16__2':0,'features__0__geometry__coordinates__0__17__0':-15.27072272145035,'features__0__geometry__coordinates__0__17__1':14.02255567674107,'features__0__geometry__coordinates__0__17__2':0,'features__0__geometry__coordinates__0__18__0':-15.26395397063758,'features__0__geometry__coordinates__0__18__1':14.13443659420945,'features__0__geometry__coordinates__0__18__2':0,'features__0__geometry__coordinates__0__19__0':-15.24023775131042,'features__0__geometry__coordinates__0__19__1':14.32904559912449,'features__0__geometry__coordinates__0__19__2':0,'features__0__geometry__coordinates__0__20__0':-15.21541086886319,'features__0__geometry__coordinates__0__20__1':14.58967912435987,'features__0__geometry__coordinates__0__20__2':0,'features__0__geometry__coordinates__0__21__0':-15.15515131233524,'features__0__geometry__coordinates__0__21__1':15.42311620512102,'features__0__geometry__coordinates__0__21__2':0,'features__0__geometry__coordinates__0__22__0':-15.45264670678973,'features__0__geometry__coordinates__0__22__1':15.42390739827185,'features__0__geometry__coordinates__0__22__2':0,'features__0__geometry__coordinates__0__23__0':-15.94444309310633,'features__0__geometry__coordinates__0__23__1':15.44371941768868,'features__0__geometry__coordinates__0__23__2':0,'features__0__geometry__coordinates__0__24__0':-16.3807688129775,'features__0__geometry__coordinates__0__24__1':15.45532235769231,'features__0__geometry__coordinates__0__24__2':0,'features__0__geometry__coordinates__0__25__0':-16.6574348263018,'features__0__geometry__coordinates__0__25__1':15.45077945422687,'features__0__geometry__coordinates__0__25__2':0,'features__0__geometry__coordinates__0__26__0':-16.75007765137733,'features__0__geometry__coordinates__0__26__1':15.41963731349297,'features__0__geometry__coordinates__0__26__2':0,'features__0__geometry__coordinates__0__27__0':-16.84991521854622,'features__0__geometry__coordinates__0__27__1':15.25813719688476,'features__0__geometry__coordinates__0__27__2':0,'features__0__geometry__coordinates__0__28__0':-16.94933674042656,'features__0__geometry__coordinates__0__28__1':15.12921501453258,'features__0__geometry__coordinates__0__28__2':0,'features__0__geometry__coordinates__0__29__0':-17.03626620967582,'features__0__geometry__coordinates__0__29__1':15.02938820681259,'features__0__geometry__coordinates__0__29__2':0,'features__0__geometry__coordinates__0__30__0':-17.10950928370794,'features__0__geometry__coordinates__0__30__1':14.94591580526796,'features__0__geometry__coordinates__0__30__2':0,'features__0__geometry__coordinates__0__31__0':-17.13088115585902,'features__0__geometry__coordinates__0__31__1':14.91578363643908,'features__0__geometry__coordinates__0__31__2':0,'features__0__geometry__coordinates__0__32__0':-17.27833470905615,'features__0__geometry__coordinates__0__32__1':14.84727548094827,'features__0__geometry__coordinates__0__32__2':0,'features__0__geometry__coordinates__0__33__0':-17.29778756226728,'features__0__geometry__coordinates__0__33__1':14.83767502076119,'features__0__geometry__coordinates__0__33__2':0,'features__0__geometry__coordinates__0__34__0':-17.30879441185855,'features__0__geometry__coordinates__0__34__1':14.8340737594179,'features__0__geometry__coordinates__0__34__2':0,'features__0__geometry__coordinates__0__35__0':-17.44096028793862,'features__0__geometry__coordinates__0__35__1':14.7932587077975,'features__0__geometry__coordinates__0__35__2':0,'features__0__geometry__coordinates__0__36__0':-17.53662598222956,'features__0__geometry__coordinates__0__36__1':14.76802543590545,'features__0__geometry__coordinates__0__36__2':0,'features__0__geometry__coordinates__0__37__0':-17.44979726383285,'features__0__geometry__coordinates__0__37__1':14.6208620053651,'features__0__geometry__coordinates__0__37__2':0}",
          "geographicLocationFile": null
        },
        "firstYearIssuance": "2017",
        "registryProjectId": "vef-1321-99da-1",
        "developers": [
          "9c6e926f-9603-45de-9933-8af01ac45f31"
        ],
        "sponsors": [
          "sponsor"
        ],
        "claimSources": [
          {
            "id": "147e7105-2333-4f5f-847c-6c984e5220dd",
            "aimId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
            "name": "Soil Sensor Device",
            "description": "Located in forest area e2",
            "location": {
              "longitude": "41.40338",
              "latitude": "2.17403",
              "geoJsonOrKml": "",
              "geographicLocationFile": null
            },
            "sourceType": "SensorDevice",
            "unitOfMeasure": "TonneCo2E",
            "reportingFrequency": "SubHourly",
            "sourceIdentifier": "key:efc0b0b0-0b0b-0b0b-0b0b-0b0b0b0b0b0b",
            "extensions": [
              {
                "id": "bdd7c465-6034-4bd4-8869-fc169ec1991a",
                "templateId": "d2af892f-a2ac-42ba-bb5d-b017a677e33e",
                "data": {
                  "protoData": null,
                  "dataType": "",
                  "value": ""
                },
                "appliedToId": "147e7105-2333-4f5f-847c-6c984e5220dd",
                "extensionContext": "ClaimSource"
              }
            ],
            "variableTemplates": []
          }
        ],
        "impactClaims": [
          {
            "id": "",
            "aimId": "",
            "processedClaimId": "",
            "claimGroupId": "",
            "startDate": "",
            "endDate": "",
            "unit": "TonneCo2E",
            "quantity": "",
            "coBenefits": [],
            "checkpoints": [],
            "extensions": [],
            "activityImpactModule": null
          }
        ],
        "extensions": [
          {
            "id": "0e23197e-3b0a-4f2b-a237-1a35ad865759",
            "templateId": "610dce02-b3b1-4cf5-88cc-ea7d66279c5e",
            "data": {
              "protoData": null,
              "dataType": "",
              "value": ""
            },
            "appliedToId": "d5a9cf0c-4102-4c9d-941a-408001b12147",
            "extensionContext": "ActivityImpactModule"
          }
        ],
        "validations": [
          {
            "requestDate": "2021-04-01",
            "validationDate": "3/20/2025",
            "validatingPartyId": "8226ece8-27b8-46f7-b21f-f531705c11cb",
            "validationMethod": "ISO 14064-3:2018",
            "validationExpirationDate": "3/20/2025",
            "validationSteps": [
              {
                "validationStepName": "Project Plan",
                "validationStepDescription": "Detailed project plan for the management of forest carbon sequestration",
                "validationStepStatus": "Completed",
                "validationStepDocumentLink": {
                  "id": "456bf8d1-f090-47b1-b7c0-b539441e557e",
                  "uri": "https://sustaincert.com/forestcarbonsequestration/projectplan.pdf",
                  "description": "Project Plan",
                  "hashProof": "0x32wasfd1234567890abcdef",
                  "hashAlgorithm": "Sha256"
                }
              }
            ]
          }
        ],
        "attestations": [],
        "formulaTemplates": [],
        "fixedVariables": [],
        "accountableImpactOrganization": {
          "id": "8ce532c6-c344-4eee-90bb-13a8a19c5910",
          "name": "Eco-Earth Forest Growth",
          "description": "The Eco-Earth Forest Growth organization is a reforestation project that aims to restore degraded land in the Amazon rainforest.",
          "addresses": [
            {
              "addressType": "Legal",
              "addressLines": [
                "123 ABC St."
              ],
              "city": "Santarém",
              "state": "PA",
              "zip": "234123",
              "country": "Brazil"
            }
          ],
          "owners": [
            "owner"
          ],
          "informationLink": {
            "id": "7edef2c7-ff0e-41fc-b5e7-dda5aa65e850",
            "uri": "https://www.ecoearth.com/forest-growth.html",
            "description": "Project Website",
            "hashProof": "n/a",
            "hashAlgorithm": "Sha256"
          },
          "mediaLinks": [
            {
              "id": "987c9c95-09bf-4ad5-8331-50be9805a9af",
              "uri": "https://www.ecoearth.com/forest-growth-video.mp4",
              "description": "Project Video",
              "hashProof": "n/a",
              "hashAlgorithm": "Sha256"
            }
          ],
          "attestations": [],
          "activityImpactModules": [],
          "extensions": []
        }
      }
    },
    "asset": null
  }
}