You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Demia is working on a secure decentralized storage system with peer-to-peer access controls that give people and companies full control over their data. We're developing initial integrations to connect our climate-focused data infrastructure to the Hedera network and Guardian platform and enable integration and interoperability with other platforms across the Hedera ecosystem. We will work within our long-standing relationship with Dell to ensure alignment on data confidence integrations (Project Alvarium) between various opportunities. We will also leverage work with Gold Standard over the past 2 years on defining the digital infrastructure and data standards necessary for the voluntary carbon market to scale through trust, quality, and integrity.
Motivation
To give companies and countries full control and protection over their digital information while making it easy to use and access by those needing access. The existing Hedera ecosystem needs support for immutable storage and access to dynamic data, as identified through issues 1040 and 2907.
Rationale
This design implementation will provide a frictionless plugin feature bridging the gap between Demia's DMRV and Confidence measurement solutions with the downstream Policy Engine workflows for streamlined end-to-end data attestation and verification. Using similarly specified W3C adherent Identification protocols provides an agnostic framework for cross-network operability and verification. Data provided by Demia data producers can be ingested by Hedera tooling to provide a higher level of confidence in calculations and methodological outcomes that result in carbon offset accreditation, as well as a secure, streamlined process for auditing from the certification level down to the granular data sourcing. Confidence scoring metrics follow the principles of the Hedera Governing Council member Dell Technologies project Alvarium framework.
Other potentially relevant Hedera issues and improvement proposals identified include:
Issue 2959
Issue 1690
Issue 1515
Issue 826
HIP 27
HIP 28
User stories
Demia's services cater to a spectrum of primary users with distinct roles within carbon markets. Project Developers who generate valuable data by implementing carbon reduction, mitigation, or adaptation projects benefit from Demia's streamlined data logistics and security. Auditors tasked with verifying project impacts can rely on Demia's transparent and immutable data to enhance the accuracy and efficiency of their reports while decreasing uncertainty through comprehensive data. Certifiers responsible for upholding environmental standards find Demia's data integrity and accessibility valuable for swift and trustworthy project certifications. These primary users form an ecosystem where Demia's solutions empower data-driven decision-making and bolster trust within carbon markets.
By serving these primary users, Demia enhances data transparency, quality, and accessibility within carbon markets, contributing to more efficient and trustworthy environmental impact assessments. How these users can interact with Demia's data logistics capabilities and infrastructure is further defined below.
Project Developers / Data Producers:
Data producers can set up gateways at their facilities/data sources that will be identified by a DID document stored within the Demia network. These identities are referenced in VCs within the Hedera network to provide a trust framework for issuing messages into the Hedera ecosystem. The gateways identify the granular data sources and aggregate the data they produce into an organized structure called a Stream. The streams act as a data tree structure with branches that help organize and create access control structures for the source data. Additionally, annotations are generated to provide metadata proofing for the provided data (including checks for things like TLS communication, usage of a TPM module, appropriate PKI attestation, and any number of other custom metadata points of relevance).
Data messages and annotations are sent via Streams into the Demia Distributed Oracle Network (DON for short), where they can then be put through analytics and reporting processes. The Hedera integrations would additionally be published in aggregated reports as a VC into the Hedera network at regular intervals to be ingested by a policy engine. Each gateway will also host a listener service to watch for event updates in the Trust Chain for the topic they are submitting to. Whenever an event is seen, it will be logged within the Stream on the Demia network, providing a copy of the trust chain history within the DON, including any minting operations (VCs and VPs).
A visualized user journey for Project Developers and Data Producers will reside here.
Auditors (Verification and Validation Bodies):
An auditor can retrieve the Trust Chain history from the VPs produced by an identified Policy Instance. Once the VP has been retrieved, the VCs contained within can then be audited, and these VCs will include references to the report generated by the Demia gateway instances. Within those reports are the Demia message links related to the source data and annotations used to generate that report. Provided the auditors have the appropriate permissions, they can retrieve those messages from the Stream details and Message Identifiers from the DON (or an associated Demia API gateway) to review the messages down to the granular source level.
A visualized user journey for Auditors or Verification and Validation Bodies (VVBs) will reside here.
A certifier (once a credential has been issued by a Root Authority) will generate a new VC for the data source provider whose identity is stored within the Demia data infrastructure network. This VC will act as the root of trust for the data issued from the Demia network into the Hedera network for policy ingestion. They will also wish to generate custom policies to act upon the parameters and metadata provided by the data producers to automate calculations and verification workflow for reporting and minting processes.
A visualized Carbon Market Standards and Registries user journey will reside here.
Whether the user is a data producer, an auditor, a certifier, or a registry, these tools would allow for a streamlined process for end to end generation of credits. They will enable a new level of depth for granular attestation and distributed identification and verification methods across network boundaries, with security, interoperability, and transparency at its core.
Specification
The document discusses and presents Demia's key concepts, definitions, and process flows in this section.
Introduction
With the Hedera Policy Workflow approach, carbon market stakeholders can streamline tracking and validation processes for carbon offset projects. For those policies to produce trusted results, there needs to be a secure pipeline for managing the data ingested by the policy flow. That's where the Demia tooling comes in. The tools provided through Demia's data logistics and infrastructure will enable a trusted framework for measuring data quality provided by data-producing entities. High-quality, verifiable data is necessary for providing high-quality calculations and, as a byproduct, high-quality credits.
We must first approach the source identification and verification processes to produce high-quality data for policy ingestion. Demia provides a DID-based solution for identifying data sources within its distributed ledger. These DID documents are stored within the network, pinned using tokens as pointers into the ledger state, allowing for a distributed verification of ownership within the Demia ecosystem. This provides the flexibility to DID document owners to generate verification methods for granular data stream access control and the generation of VCs similar to the processes seen throughout the Hedera network. These documents are the foundation of identity for data producers and consumers within the network to create arbitrarily complex access control streams for organizing data sources into data trees within the distributed database and resulting Decentralized Oracle Network (DON).
Definitions
Term
Description
Data Source
The producing entity of data that will be published through a Stream using an associated cryptographic identifier. This includes manual and automated data.
Stream
High-level definition of data streaming across the DON within the Demia ecosystem
Tree
An organized data structure comprised of branches and leaves
Branch
A topic-defined stream of data messages with access control
Leaf
A data message within a branch.
Signature
A cryptographic digital stamp that can be used to verify the identity of a data source.
Data Producer
A facility or device that acts as a collection point for data sources, organizing and annotating data messages as leaves within a Stream.
Manual Data
Data collected from spreadsheets or manually entered via forms by an operator at the data-producing end.
External Data
Data collected from sources outside of the Data Producer's scope relevant for analysis and reporting purposes.
Project Data
Data collected from sources within the scope of the Data Producer. Used in organizational display, calculations, and reporting for certification.
Reporting Engine
An automated service aggregating Project Data and Annotations into reports for review by auditors/certifiers and ingestion into policy workflows.
Gateway Application
The Demia production software runs at the edge level, acting as a collector and access point to Data Producer-based API.
Demia Gateway
A physical hardware device provided by Demia that houses a Gateway Application instance.
HCS Listener
A listener service present on a Demia gateway that monitors events associated with a specified topic(s) that registers event logs as Leafs into a data stream
Distributed Oracle Network (DON)
A Distributed Ledger Technology comprised of nodes gossiping and verifying a shared state and database
Publishing Node
A lightweight node in the Demia ecosystem dedicated to publishing data into the DON.
Service Node
A node in the Demia ecosystem that handles service operations such as message and identity retrieval and publishing.
Alvarium
A flexible framework for tracking and measuring the quality of data provided from a Data Source through the use of metadata Annotations and a scoring algorithm for successfully produced annotations.
Annotation
A metadata structure defining the status of a particular attribute (such as TLS and TPM usage, geolocation PKI attestation, etc).
Key Integrations
Hedera and Demia Integrations: Swim Lane Diagram
1. Data Ingestion
Data ingestion is a bridge function between a data producer and their ability to publish data onto Demia's data infrastructure and utilize Demia's data management tools.
Concerning Demia's initial integrations with Hedera's Guardian and Services, ingestion begins with enabling interoperability of existing Hedera W3C DID implementation currently in practice on the Hedera network (as outlined in HIP 28) and Demia's implementation of W3C DIDs for data storage, compartmentalizations, encryption, signing and retrieval.
Data is compartmentalized at the edge level via a Gateway Application configured to identify and collect from manual, automated, and external sources at specific intervals. This data is organized, wrapped, encrypted, and signed before being published into the DON. Alongside these data messages, configured annotations provide additional metadata attesting to various attributes of the data handling and state present.
For Guardian integration, these data messages are also aggregated alongside their annotations to be published within a report via the Reporting Engine present within the Gateway Application. These reports are issued regularly into the Hedera Consensus Service as a VC that the Guardian Policy Engine can process. These reports are posted using the Demia-based DID that has been attested for by a VC issued within the Hedera ecosystem.
2. Identification and Verification
To provide the appropriate connection between DID instances across networks, a set of API tools is necessary to attest to the linkage between networks, allowing for Verifying bodies within the ownership chain in the Guardian to create a claim of verification (in the form of a VC) for an existing DID within the Demia ecosystem.
This can be represented through a handshake agreement between the networks:
A detailed API pseudocode example will reside here
Having the tools on both ends to retrieve and resolve DID documents, VCs, and VPs will allow for a streamlined attestation and verification process across network boundaries. Since the W3C standard for DIDs is being adhered to by both Demia and Hedera, the documents for each network do not require replication and can be decoupled from a network/registry perspective while still providing universal resolvability.
3. Data Management
Data management activities utilized through Demia's infrastructure consist of multiple automated functions that leverage the suite of tools Demia has developed. These functions include:
Storage - storage of data on Demia's Decentralized Oracle Network (DON).
Compartmentalization / Sharding - the act of embedding the data into a sovereign data tree sharded across the DON to ensure only the data producer can grant and revoke access to the data as well as maintain the instructions to reassemble it.
Encryption - the act of obfuscating data within a sovereign data tree to only be accessed by the approved parties. Failure to decrypt the initial message will result in a failure to decrypt all subsequent messages in the chain. Demia encrypts all leaves within a data tree utilizing standard X25519 encryption mechanisms.
Batching - the act of aggregating data messages and annotations into a summary report for digestion in external systems such as Hedera's Policy Engine.
Signing - digitally stamping a data message with a cryptographic proof of identification. Demia uses an ED25519 signature scheme for signing leaves within a data tree. Signing is utilized to aid in identifying data providers, originating organizations and facilities, identifying storage boundaries in alignment with regulatory requirements, and as a foundation for peer-to-peer access control mechanisms for sharing data.
Publishing - the act of attaching new blocks into a distributed ledger protocol (such as the DON and the Hedera Consensus Service)
Subscribing - the act of requesting and being granted access to a particular data tree branch (and thus a particular data source from a data provider). Once accepted by a provider, subscription requests will grant forward access to leaves within a data tree branch.
Verification - the act of confirming the identity of a data-producing source. Leaf signatures are consistently verified against the identity of the data source before any ingestion into Demia services. These same verification methods can be used to check the proofs on data reports published from Gateway Application into the HCS
Reporting - Data from a data provider will be aggregated into reports for easier digestion by auditor workflows and analytics tooling. These reports are produced internally for Demia service purposes and externally for a custom utility-like use in Hedera Policy Flows via the Reporting Engine.
4. Data Annotations (Project Alvarium)
The Demia team has a long-standing history of co-development and contribution with Hedera Governing Council member Dell Technologies. Through the work with Dell, Demia has refined and iterated on establishing data confidence fabrics for quantifying the confidence we can have in the data that comes from a project facility. These functions are embedded into the Demia protocol as metadata annotators using the Alvarium SDK. All data leafs produced from a data source through a Gateway Application will be accompanied by a collection of metadata leaves (Annotations) that attest to attributes of the data production process. These metadata Annotations are then used to produce a confidence score to rate on a custom gradient how trusted each piece of data produced from a data source can be, as well as the aggregate score of the data producers as a result.
A trust schema must be defined as part of the Demia integration process to establish trust in a Hedera Trust Chain. This should include a necessary understanding of data handling and security procedures established on-site and using various tools that Demia provides through its data management capabilities.
Insert Trust Schema Example for Discussion and Refinement
5. Data Retrieval
Data can be granularly retrieved from the Demia Service Nodes and Service API. If the user has the appropriate permissions to decrypt the data, the payloads and annotations can be used in calculations, reporting, and analytics. For auditing purposes, aggregation reports are issued regularly, referencing the source data that can be retrieved at the individual message level for granular analysis. VPs produced via the Policy Engine will contain references to the VCs that were processed to generate them, and subsequently, the VCs will contain the aggregate reports that reference the granular data links within the Demia DON. This allows auditing flow from the highest to the lowest level, with all the cryptographic proofing and encryption to secure data endlessly within the workflow.
Link here to the Auditor user journey diagram highlighting this process
Outline how data will flow between projects, Demia infrastructure, hedera, and the services we'll enable on top of the data flow.
6. Summary
Utilizing the key integrations outlined above, Demia will enable a deeper understanding of the uncertainty associated with a project through extensive Digital MRV capabilities. These key integrations can be understood through the data flow diagram below. The diagram outlines how data is captured for a source, managed on an edge device, published to the Demia DON, and reported to Hedera. Other various functions and activities it goes through with Demia's data logistics and managed service capabilities are also identified.
Hedera and Demia Integrations: Data Flow Diagram
Backwards Compatibility
This integration would not compromise compatibility with existing policy engine functionality or identification processes, it would instead provide tooling for externalized data to be ingested by the policy engine as well as an additional event logging functionality within the Demia data infrastructure. Identities within both networks conform to the DID specification and are intended to be cross-compatible (DID documents and VCs from the Hedera network will be resolvable within the Demia infrastructure, and the VCs issued from the Demia end should provide an appropriate resolvability within the Hedera VC's). VPs issued by the Hedera Guardian that are stored in IPFS will have reference links to the ingested policy data forwarded from the Demia-issued VCs, allowing an audit flow to trace the policy inputs and outputs from source to minting.
Security Implications
Demia's data storage, encryption, transfer, and access capabilities are built in alignment with Zero-Trust Architectures through Demia's innovative Zero-Trust Layered Data Model, which includes decentralized data fabrics, confidential computing integrations, and secure data wallet products. These are all scoped to ensure sovereign data management over decentralized data infrastructure, creating leading-edge cyber security solutions and tools for organizations and individuals leveraging Demia's capabilities. These tools are built on standardized ED25519 encryption libraries aligned with existing Hedera capabilities.
Through our integrations with Hedera's Guardian, we will enable the creation of decentralized digital vault capabilities for climate data for granular data points, files, and services to leverage dynamically. We will also develop and release 3-4 open-source tools that enhance data storage, security, analytics, or oracle utility in sustainable finance use cases throughout the Guardian ecosystem.
How to Teach This
As part of our development process, Demia's team will develop standard operating procedures for utilizing Demia's data infrastructure and tools, which will be hosted on the Demia Wiki (to be released). We will also ensure that existing Hedera documentation and guidance are updated to reflect the ability to utilize Demia's data infrastructure and tools in alignment with current practices. This will include:
Code documentation
Wiki documentation
Updates to Hedera documentation
Standard Operating Procedures (SOPs) /Guides
Video walkthroughs
Code examples
NOTE: All educational material developed as part of this HIP will be linked in this HIP as it is published.
Reference Implementation
The reference implementation will be developed and stored under the Demia Protocol GitHub as a project and will include a public roadmap.
Once the reference implementation and core integrations are complete, the services presented in this Integrated System Overview for identified carbon market stakeholders will be able to interoperate in a trusted and sustainable manner. Streamlining the monitoring, reporting, and verification of necessary activities across voluntary carbon markets for more rapid iteration.
Hedera and Demia Integrations: Reference Implementation Diagram
NOTE: Once the Project folder has been published publicly, the HIP will be updated with a link to the folder.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Abstract
Demia is working on a secure decentralized storage system with peer-to-peer access controls that give people and companies full control over their data. We're developing initial integrations to connect our climate-focused data infrastructure to the Hedera network and Guardian platform and enable integration and interoperability with other platforms across the Hedera ecosystem. We will work within our long-standing relationship with Dell to ensure alignment on data confidence integrations (Project Alvarium) between various opportunities. We will also leverage work with Gold Standard over the past 2 years on defining the digital infrastructure and data standards necessary for the voluntary carbon market to scale through trust, quality, and integrity.
Motivation
To give companies and countries full control and protection over their digital information while making it easy to use and access by those needing access. The existing Hedera ecosystem needs support for immutable storage and access to dynamic data, as identified through issues 1040 and 2907.
Rationale
This design implementation will provide a frictionless plugin feature bridging the gap between Demia's DMRV and Confidence measurement solutions with the downstream Policy Engine workflows for streamlined end-to-end data attestation and verification. Using similarly specified W3C adherent Identification protocols provides an agnostic framework for cross-network operability and verification. Data provided by Demia data producers can be ingested by Hedera tooling to provide a higher level of confidence in calculations and methodological outcomes that result in carbon offset accreditation, as well as a secure, streamlined process for auditing from the certification level down to the granular data sourcing. Confidence scoring metrics follow the principles of the Hedera Governing Council member Dell Technologies project Alvarium framework.
Other potentially relevant Hedera issues and improvement proposals identified include:
User stories
Demia's services cater to a spectrum of primary users with distinct roles within carbon markets. Project Developers who generate valuable data by implementing carbon reduction, mitigation, or adaptation projects benefit from Demia's streamlined data logistics and security. Auditors tasked with verifying project impacts can rely on Demia's transparent and immutable data to enhance the accuracy and efficiency of their reports while decreasing uncertainty through comprehensive data. Certifiers responsible for upholding environmental standards find Demia's data integrity and accessibility valuable for swift and trustworthy project certifications. These primary users form an ecosystem where Demia's solutions empower data-driven decision-making and bolster trust within carbon markets.
By serving these primary users, Demia enhances data transparency, quality, and accessibility within carbon markets, contributing to more efficient and trustworthy environmental impact assessments. How these users can interact with Demia's data logistics capabilities and infrastructure is further defined below.
Project Developers / Data Producers:
Data producers can set up gateways at their facilities/data sources that will be identified by a DID document stored within the Demia network. These identities are referenced in VCs within the Hedera network to provide a trust framework for issuing messages into the Hedera ecosystem. The gateways identify the granular data sources and aggregate the data they produce into an organized structure called a Stream. The streams act as a data tree structure with branches that help organize and create access control structures for the source data. Additionally, annotations are generated to provide metadata proofing for the provided data (including checks for things like TLS communication, usage of a TPM module, appropriate PKI attestation, and any number of other custom metadata points of relevance).
Data messages and annotations are sent via Streams into the Demia Distributed Oracle Network (DON for short), where they can then be put through analytics and reporting processes. The Hedera integrations would additionally be published in aggregated reports as a VC into the Hedera network at regular intervals to be ingested by a policy engine. Each gateway will also host a listener service to watch for event updates in the Trust Chain for the topic they are submitting to. Whenever an event is seen, it will be logged within the Stream on the Demia network, providing a copy of the trust chain history within the DON, including any minting operations (VCs and VPs).
Auditors (Verification and Validation Bodies):
An auditor can retrieve the Trust Chain history from the VPs produced by an identified Policy Instance. Once the VP has been retrieved, the VCs contained within can then be audited, and these VCs will include references to the report generated by the Demia gateway instances. Within those reports are the Demia message links related to the source data and annotations used to generate that report. Provided the auditors have the appropriate permissions, they can retrieve those messages from the Stream details and Message Identifiers from the DON (or an associated Demia API gateway) to review the messages down to the granular source level.
Carbon Market Standards & Registries (Certifiers):
A certifier (once a credential has been issued by a Root Authority) will generate a new VC for the data source provider whose identity is stored within the Demia data infrastructure network. This VC will act as the root of trust for the data issued from the Demia network into the Hedera network for policy ingestion. They will also wish to generate custom policies to act upon the parameters and metadata provided by the data producers to automate calculations and verification workflow for reporting and minting processes.
Whether the user is a data producer, an auditor, a certifier, or a registry, these tools would allow for a streamlined process for end to end generation of credits. They will enable a new level of depth for granular attestation and distributed identification and verification methods across network boundaries, with security, interoperability, and transparency at its core.
Specification
The document discusses and presents Demia's key concepts, definitions, and process flows in this section.
Introduction
With the Hedera Policy Workflow approach, carbon market stakeholders can streamline tracking and validation processes for carbon offset projects. For those policies to produce trusted results, there needs to be a secure pipeline for managing the data ingested by the policy flow. That's where the Demia tooling comes in. The tools provided through Demia's data logistics and infrastructure will enable a trusted framework for measuring data quality provided by data-producing entities. High-quality, verifiable data is necessary for providing high-quality calculations and, as a byproduct, high-quality credits.
We must first approach the source identification and verification processes to produce high-quality data for policy ingestion. Demia provides a DID-based solution for identifying data sources within its distributed ledger. These DID documents are stored within the network, pinned using tokens as pointers into the ledger state, allowing for a distributed verification of ownership within the Demia ecosystem. This provides the flexibility to DID document owners to generate verification methods for granular data stream access control and the generation of VCs similar to the processes seen throughout the Hedera network. These documents are the foundation of identity for data producers and consumers within the network to create arbitrarily complex access control streams for organizing data sources into data trees within the distributed database and resulting Decentralized Oracle Network (DON).
Definitions
Key Integrations
Hedera and Demia Integrations: Swim Lane Diagram
1. Data Ingestion
Data ingestion is a bridge function between a data producer and their ability to publish data onto Demia's data infrastructure and utilize Demia's data management tools.
Concerning Demia's initial integrations with Hedera's Guardian and Services, ingestion begins with enabling interoperability of existing Hedera W3C DID implementation currently in practice on the Hedera network (as outlined in HIP 28) and Demia's implementation of W3C DIDs for data storage, compartmentalizations, encryption, signing and retrieval.
Data is compartmentalized at the edge level via a Gateway Application configured to identify and collect from manual, automated, and external sources at specific intervals. This data is organized, wrapped, encrypted, and signed before being published into the DON. Alongside these data messages, configured annotations provide additional metadata attesting to various attributes of the data handling and state present.
For Guardian integration, these data messages are also aggregated alongside their annotations to be published within a report via the Reporting Engine present within the Gateway Application. These reports are issued regularly into the Hedera Consensus Service as a VC that the Guardian Policy Engine can process. These reports are posted using the Demia-based DID that has been attested for by a VC issued within the Hedera ecosystem.
2. Identification and Verification
To provide the appropriate connection between DID instances across networks, a set of API tools is necessary to attest to the linkage between networks, allowing for Verifying bodies within the ownership chain in the Guardian to create a claim of verification (in the form of a VC) for an existing DID within the Demia ecosystem.
This can be represented through a handshake agreement between the networks:
Having the tools on both ends to retrieve and resolve DID documents, VCs, and VPs will allow for a streamlined attestation and verification process across network boundaries. Since the W3C standard for DIDs is being adhered to by both Demia and Hedera, the documents for each network do not require replication and can be decoupled from a network/registry perspective while still providing universal resolvability.
3. Data Management
Data management activities utilized through Demia's infrastructure consist of multiple automated functions that leverage the suite of tools Demia has developed. These functions include:
4. Data Annotations (Project Alvarium)
The Demia team has a long-standing history of co-development and contribution with Hedera Governing Council member Dell Technologies. Through the work with Dell, Demia has refined and iterated on establishing data confidence fabrics for quantifying the confidence we can have in the data that comes from a project facility. These functions are embedded into the Demia protocol as metadata annotators using the Alvarium SDK. All data leafs produced from a data source through a Gateway Application will be accompanied by a collection of metadata leaves (Annotations) that attest to attributes of the data production process. These metadata Annotations are then used to produce a confidence score to rate on a custom gradient how trusted each piece of data produced from a data source can be, as well as the aggregate score of the data producers as a result.
A trust schema must be defined as part of the Demia integration process to establish trust in a Hedera Trust Chain. This should include a necessary understanding of data handling and security procedures established on-site and using various tools that Demia provides through its data management capabilities.
5. Data Retrieval
Data can be granularly retrieved from the Demia Service Nodes and Service API. If the user has the appropriate permissions to decrypt the data, the payloads and annotations can be used in calculations, reporting, and analytics. For auditing purposes, aggregation reports are issued regularly, referencing the source data that can be retrieved at the individual message level for granular analysis. VPs produced via the Policy Engine will contain references to the VCs that were processed to generate them, and subsequently, the VCs will contain the aggregate reports that reference the granular data links within the Demia DON. This allows auditing flow from the highest to the lowest level, with all the cryptographic proofing and encryption to secure data endlessly within the workflow.
Outline how data will flow between projects, Demia infrastructure, hedera, and the services we'll enable on top of the data flow.
6. Summary
Utilizing the key integrations outlined above, Demia will enable a deeper understanding of the uncertainty associated with a project through extensive Digital MRV capabilities. These key integrations can be understood through the data flow diagram below. The diagram outlines how data is captured for a source, managed on an edge device, published to the Demia DON, and reported to Hedera. Other various functions and activities it goes through with Demia's data logistics and managed service capabilities are also identified.
Hedera and Demia Integrations: Data Flow Diagram
Backwards Compatibility
This integration would not compromise compatibility with existing policy engine functionality or identification processes, it would instead provide tooling for externalized data to be ingested by the policy engine as well as an additional event logging functionality within the Demia data infrastructure. Identities within both networks conform to the DID specification and are intended to be cross-compatible (DID documents and VCs from the Hedera network will be resolvable within the Demia infrastructure, and the VCs issued from the Demia end should provide an appropriate resolvability within the Hedera VC's). VPs issued by the Hedera Guardian that are stored in IPFS will have reference links to the ingested policy data forwarded from the Demia-issued VCs, allowing an audit flow to trace the policy inputs and outputs from source to minting.
Security Implications
Demia's data storage, encryption, transfer, and access capabilities are built in alignment with Zero-Trust Architectures through Demia's innovative Zero-Trust Layered Data Model, which includes decentralized data fabrics, confidential computing integrations, and secure data wallet products. These are all scoped to ensure sovereign data management over decentralized data infrastructure, creating leading-edge cyber security solutions and tools for organizations and individuals leveraging Demia's capabilities. These tools are built on standardized ED25519 encryption libraries aligned with existing Hedera capabilities.
Through our integrations with Hedera's Guardian, we will enable the creation of decentralized digital vault capabilities for climate data for granular data points, files, and services to leverage dynamically. We will also develop and release 3-4 open-source tools that enhance data storage, security, analytics, or oracle utility in sustainable finance use cases throughout the Guardian ecosystem.
How to Teach This
As part of our development process, Demia's team will develop standard operating procedures for utilizing Demia's data infrastructure and tools, which will be hosted on the Demia Wiki (to be released). We will also ensure that existing Hedera documentation and guidance are updated to reflect the ability to utilize Demia's data infrastructure and tools in alignment with current practices. This will include:
NOTE: All educational material developed as part of this HIP will be linked in this HIP as it is published.
Reference Implementation
The reference implementation will be developed and stored under the Demia Protocol GitHub as a project and will include a public roadmap.
Once the reference implementation and core integrations are complete, the services presented in this Integrated System Overview for identified carbon market stakeholders will be able to interoperate in a trusted and sustainable manner. Streamlining the monitoring, reporting, and verification of necessary activities across voluntary carbon markets for more rapid iteration.
Hedera and Demia Integrations: Reference Implementation Diagram
NOTE: Once the Project folder has been published publicly, the HIP will be updated with a link to the folder.
Rejected Ideas
N/A
Open Issues
Directly related open issues include:
References
A collection of URLs used as references through the HIP.
Copyright/license
This document is licensed under the Apache License, Version 2.0 -- see LICENSE or (https://www.apache.org/licenses/LICENSE-2.0)
Beta Was this translation helpful? Give feedback.
All reactions