Ecosphere
  • Introduction
  • Elevator Pitch
  • Pitch Deck
  • Lean Model Canvas
  • OVERVIEW
    • Mission
    • Problem Statement
    • Ecosphere Prime Solution
    • Benefits
    • Value Proposition
    • Use Cases By Industry
    • Achieving Net Zero
    • Technology Platform
    • "Waze For Weather"
    • Strategic Roadmap
  • Technology
    • Climate Intelligence Network
    • Climate Nodes
      • Prototype
      • Device Mockup
      • Device Setup
      • Node Location Planning
      • Node Explorer
    • Smart Nodes On Hedera
      • Web3
      • Smart Nodes Vs Smart Contracts
    • DIDs and Verifiable Credentials
    • Peer-to Peer Data Sharing
      • How We Use Hedera
      • Hedera Topics
      • Data Tokenization
      • Data Sharing
    • Decentralized Identity
    • Micro Royalties
    • Fractional Ownership
    • Integration
      • Climate Data Workbench
      • API
    • AI Forecasting
  • Functional Flows
    • Registering A New User
    • Registering A New Node
    • Data Collection From Nodes
    • Data Tokenization
    • Data Sharing
    • AI and DLT
    • Marketplace
    • Fractional Ownership
  • Community Product
    • Product Community Fit
    • Product Vision
    • Minimum Viable Product App
    • Wireframe
      • Onboarding
      • Walkthrough Tutorials
      • Wallet Creation
      • Location List
      • Weather Information
      • Location Options and Support
      • Timelapses
      • Animations
      • Weather Station Setup
      • Search and Explore
      • Settings
      • Sharing and Notifications
    • Style Guide
    • Visual Design Elements
    • Usernames Feature
  • Commercial Product
    • Sector Focus
    • Product Market Fit
    • Comprehensive Reporting and Dashboards
    • Climate Data Oracle
    • Go-To-Market
    • Competition
  • Tokenomics
    • Revenue Drivers
    • $PRIME Token
    • Value Capture Mechanism
    • Reward Structure
    • Locale Coverage
    • Nodes For Public Good
  • Community
    • Whitepaper
    • Public Good
    • Joining Ecosphere
    • Governance
    • Awareness
    • Disaster Readiness
    • Early Warning System
    • Socials
  • Project Developer
    • About
    • Team
    • Funding
    • Testnet Accounts
Powered by GitBook
On this page
  1. Technology

DIDs and Verifiable Credentials

PreviousSmart Nodes Vs Smart ContractsNextPeer-to Peer Data Sharing

Last updated 4 months ago

Ecosphere tracks data provenance by using a combination of blockchain technology and decentralized identifiers (DIDs). This is similar to the design used in the Hedera Guardian. Here’s how it works:

  1. Decentralized Identifiers (DIDs): Ecosphere uses DIDs to uniquely identify data sources and their owners. These identifiers are crucial for establishing trust and authenticity without relying on centralized authorities.

  2. Verifiable Credentials: Data is often accompanied by verifiable credentials, which are cryptographically secure and can prove the authenticity and integrity of the data. These credentials are issued by Ecosphere during the user and device registration process.

  3. Immutable Ledger: Hedera's distributed ledger technology ensures that once data is recorded, it cannot be altered or tampered with. This immutability is essential for maintaining a reliable history of data provenance.

  4. Smart Nodes: Smart nodes are used to automate the tracking and verification of data provenance. These contracts can enforce rules and conditions for data use and access, ensuring compliance and transparency.

  5. Audit Trails: Every transaction or change in data is logged with a timestamp and other relevant metadata, creating a complete audit trail. This trail can be reviewed to verify the origin and journey of the data.

  6. Interoperability: Ecosphere plans to integrate with other systems and technologies in the future. This will require the establishment of a set of standards to ensure that data provenance information can be shared and usable across different platforms and sectors.

By combining these elements, the Ecosphere provides a robust framework for tracking data provenance, ensuring that data is trustworthy and its origins can be verified.

Design Flow

Step 1: Creation of Data Source DID (Node Device)

  1. Identify Data Source:

    • Determine the data source that needs a unique decentralized identifier (DID).

  2. Generate DID:

    • Use a DID method to generate a unique DID for the data source. This involves creating a DID document that includes public keys and service endpoints.

  3. Register DID:

    • Register the DID on a decentralized network, ensuring it is publicly resolvable. This makes the DID discoverable and verifiable by others.

Step 2: Issuance of Verifiable Credential (VC)

  1. Prepare Credential Data:

    • Collect the necessary data that will be included in the verifiable credential. This data typically includes claims about the data source.

  2. Sign Credential:

    • The issuer (Ecosphere) digitally signs the credential using their private key. This signature ensures the credential's integrity and authenticity.

  3. Embed Proofs:

    • Embed cryptographic proofs in the VC to enable verifiers to check its validity and integrity.

  4. Issue Credential:

    • Issue the signed verifiable credential to the holder, which in this case is the entity responsible for the data transfer.

Step 3: Data Transfer and Verification

  1. Present Credential:

    • When transferring data, the holder presents the verifiable credential to the recipient or verifier.

  2. Verify Credential:

    • The verifier checks the cryptographic signature and proofs to ensure the credential is authentic and has not been tampered with.