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
  • Hedera Consensus Service (HCS)
  • HCS Topics
  1. Technology

Peer-to Peer Data Sharing

Hedera Consensus Service (HCS)

HCS provides a decentralized consensus mechanism for events and incoming data submissions from the nodes. As sensors send data, HCS can reliably record the sequence of events and provide proofs of their order.

Advantages:

  1. Decentralized Ordering: HCS ensures that data from all nodes is ordered and can be verified independently, adding to the integrity of the system.

  2. Scalability: HCS can handle many transactions per second, crucial for a distributed network of sensor nodes.

  3. Provenance and Trust: By using HCS to include logs or events, you can create an immutable ledger of sensor data, increasing trust among users of your app.

  4. Flexibility: HCS allows you to build applications without the need for complex blockchain logic, focusing more on event-driven architecture.

HCS Topics

Topics are a unique feature within HCS which enables decentralized, trustless, and verifiable messaging.

What are Topics in Hedera?

In Hedera, a topic is a channel or subject in which messages are published on the Hedera network through the Consensus Service. Each topic has a unique ID and serves as a log where messages (like transactions or events) can be written sequentially. Once messages are published to a topic, they’re timestamped, ordered, and made immutable by the Hedera network.

Key Aspects of Topics in Hedera:

  1. Unique Topic ID: Each topic has a specific ID (e.g., 0.0.xxxxx), making it easy to refer to and access.

  2. Immutable Log: Messages published to a topic are stored in a tamper-proof, chronological sequence, making it ideal for audit trails or event tracking.

  3. Consensus Timestamp: Each message is timestamped by the network, giving it an official, trusted record.

  4. Public or Private Access: Topics can be open for public or restricted access, allowing only authorized parties to publish or view messages, depending on permissions.

Ecosphere leverages topics to enable trustless, transparent communication, especially in applications needing secure, verified, or timestamped messages.

  1. Heartbeats

  2. Service receipt

  3. Service acknowledgement

  4. Service request

  5. Service completion

  6. Service error

  7. Service extension

Each device is writing to its own Topics on Hedera using the Hedera Consensus Service.

PreviousDIDs and Verifiable CredentialsNextHow We Use Hedera

Last updated 4 months ago