Emerging Platform dMRV

Reference the reusable dMRV capability model in Emerging Platform and link into solution-specific implementation guides.

This page documents the Emerging Platform scope. It is the canonical reference for reusable digital measurement, reporting, and verification (dMRV) capabilities that can be used by multiple solutions.

What dMRV means at platform level

At platform level, dMRV provides shared capabilities for:

• entity-linked measurement records
• claims and verification workflows
• credential issuance and status checks
• tamper-evident registry references

These capabilities are not specific to one vertical implementation.

Capability layers

Identity layer

DID-based entity identity and controller relationships.

Measurement layer

Structured ingestion of time-linked monitoring evidence.

Verification layer

Rule-based and oracle-assisted checks on submitted claims.

Certification layer

Verifiable credentials for accepted outcomes and attestations.

Core dependencies in IXO

• Identity and domain model: /platforms/Emerging/digital-identifiers
• Domain lifecycle and control: /platforms/Emerging/domain-registration
• Registry-backed state: /platforms/Emerging/registry
• Credential lifecycle: /platforms/Emerging/credential-issuance

Solution implementations

Use this reference together with implementation pages:

• Emerging Household Energy implementation: /platforms/Emerging/emerging-dmrv
• Household data collection: /platforms/Emerging/household-monitoring
• Device telemetry flow: /platforms/Emerging/stove-use-monitoring

When to use this page

Use this page when you are designing or integrating reusable dMRV infrastructure.
Use solution pages when you need workflow details for a specific domain.

title: ‘Emerging Platform dMRV’ icon: ‘chart-line’ description: ‘Reference overview of dMRV capabilities in the Emerging Platform, with links to the Emerging Household Energy implementation.’

The Emerging Platform provides reusable digital measurement, reporting, and verification (dMRV) capabilities for identity-linked data collection, claim verification, and credential issuance. This page describes platform-level building blocks. For the household-energy implementation, use the Emerging Household Energy dMRV guide.

What this page covers

The platform model is solution-agnostic and can be adapted to multiple domains. Core capabilities include:

• Household-Level Reporting - Consolidated data across multiple devices and fuel sources
• Usage Monitoring - Tracking of multiple devices and fuels to prevent double-counting
• Connected Data Graph - Linked entities and claims for system-wide insights
• Immutable Records - Blockchain-backed registry for full traceability

Core features

Real-Time Measurement

IoT and smart device integration for continuous data capture

Cryptographic Trust

Immutable audit trail with blockchain verification

Protocol-Based

Standardized templates for rapid deployment

Automated Verification

AI-powered oracles for data validation

System architecture

Data Layer

Secure storage and cryptographic proofs

Protocol Layer

Configurable rules and verification logic

Integration Layer

IoT device and system connectors

Oracle Layer

Automated verification services

Core concepts

Digital Entities

Digital entities are online representations of real-world objects or concepts in IXO services, including:

• Physical entities (stoves, energy devices)
• Cognitive entities (Organisations, projects, assets)

Each entity has a W3C DID (Decentralized Identifier) that provides:

• Unique identification
• Cryptographic verification
• Self-sovereign control

Entity Relationships

Entities form nodes in a data graph connected by relationships that show:

• Project implementation by Organisations
• Project funding sources
• Asset generation
• Claim verification by Oracles
• Credential issuance
• Impact credit tokenization

Domain Registration

Entities register on the blockchain as domains with:

• DID for verifiable ownership
• Domain controllers (authorized updaters)
• Connected services
• Linked resources and claims
• Object capabilities (zCAPs, Cacao)
• Economic accounts
• NFT representation

Protocols

Protocols provide templates for domain configuration including:

• Default data fields
• Standard relationships
• Required services
• Governance settings

Implementation patterns

Device Integration

Supported Devices

• Smart cooking appliances
• Energy meters
• Environmental sensors
• IoT-enabled infrastructure

Data Requirements

• Time-stamped usage metrics
• Device identifiers (DIDs)
• Consumption data
• Environmental parameters

Connection Methods

• Direct API integration
• IoT hub connectivity
• Batch data uploads
• Real-time streaming

Quantification considerations

The accurate quantification of emission reductions in clean cooking initiatives depends on three critical factors:

1. Household Fuel Consumption: Precise measurement of fuel usage patterns and quantities
2. Usage Rate: Actual utilization rates of clean cooking devices
3. Installation Base: Accurate tracking of number and type of stoves installed

Real-Time Field Data

Emission reductions must be verifiable and quantifiable to be recognized under international standards. The dMRV system ensures this through:

• Continuous Data Collection: Real-time field data provides the foundation for credible quantification
• Immediate Verification: Automated validation of incoming data streams
• Temporal Accuracy: No retroactive data collection or post-hoc estimations
• Field-to-Registry Pipeline: Direct flow from measurement to verification to registration

Monitoring Requirements

To ensure reliable quantification, the dMRV system implements:

• Comprehensive Monitoring Plans: Structured data collection across all key metrics
• Statistical Rigor: Sample design and size calculations that meet methodology requirements
• Data Quality Controls: Validation of fuel consumption and usage measurements
• Installation Tracking: Verified device registration and deployment records

These elements are essential for:

• Accurate emission reduction calculations
• Reliable baseline establishment
• Verifiable impact claims
• Methodology compliance

Workflow components

Data Collection

Household Registration

Assign unique DIDs to households and issue credentials

Device Registration

Assign unique DIDs to monitoring devices

Data Ingestion

Secure data pipelines with integrity checks

Claim Verification

Automated measurement and verification based on protocol methods and rules

Verification Process

Automated Checks

• Data completeness verification
• Threshold compliance monitoring
• Anomaly detection
• Pattern analysis

Oracle Services

• AI-powered data validation
• Cross-reference checking
• Methodology compliance
• Real-time alerts

Manual Reviews

• Expert verification
• Audit support
• Compliance documentation
• Stakeholder reporting

Related solution guide

Use this platform reference together with:

• Emerging Household Energy dMRV
• Household monitoring
• Registry

Benefits

• Real-time tracking of system dynamics
• Immutable, verifiable records
• Simplified entity management through protocols
• Automated workflows and verification
• Evidence-based oversight for Article 6.2 compliance

Developer Resources

API Documentation

Complete API reference and examples

Registry Integration

Connect with the Emerging Registry

Protocol Templates

Ready-to-use protocol configurations

Related Guides

Household Monitoring

Implement household-level tracking

Stove Use Monitoring

Track device usage patterns

Kitchen Performance Tests

Measure fuel consumption

Qualitative Surveys

Conduct household surveys