Page cover

Protocol

Protocol Overview

The Chroom protocol is a decentralized Real Time Communication Network operating an algorithmic prosumer marketplace for real-time data, powered by a blockchain and a native protocol token

  • Clients – representing the demand side – spend tokens to acquire Chroom data to power meetings, audio spaces, and other applications requiring real-time data.

  • Media Nodes – representing the supply side – earn tokens by enabling low-latency real-time data to provision the Clients.

The Chroom Network utilizes Proof of Resource to ensure fair compensation for Media Nodes and enforce performance standards by tracking and rewarding nodes based on on-chain Quality of Service data, incentivizing high up-time and optimal service quality from node operators.

The network functions as a multisided algorithmic marketplace:

  • Supply: Media Nodes providing network resources (bandwidth, compute).

  • Demand: Consumer and industrial applications built on the Chroom Network.


Chroom Protocol Sketch

Network
Media Node

  1. At request by registry (Smart Con- tracts): (a) The Rewards Contract queries the Proof of resource Contract for node data

    (b) Rewards for each Media Node are calculated

    (c) The Rewards Contract requests token release from the Reserve Contract

    (d) Tokens are transferred to each Media Node’s pool Contract

    (e) The Pool Contract distributes rewards per its rules

  1. Listen for requests from Orches- trator

  2. Process RTC workloads

  3. Perform QoS Tests on request from Registry Nodes

at each epoch t:

  1. For each Client C, Report RTC Usage

  2. Claim Rewards Earned for giving RTC Usage

Network
Orchestrator

at any time: at any time:

  1. Perform QoS Tests on Media Nodes and collect analytics

  2. Request for Media Nodes from Registry:

  3. Listen for Media Nodes entry re- quests to the network (a) query Media Nodes from reg- istry based on

  4. Gossip New Media node entries to the network input parameters

  5. Verify Media Nodes are Alive 2. Allocate and Balance RTC Work- load on Media Nodes

  6. Serve latest Media Node entries and metadata to clients

  1. Listen for requests from Orches- trator

  2. Process RTC workloads

  3. Perform QoS Tests on request from Registry Nodes

at each epoch t:

  1. For each Client C, Report RTC Usage

  2. Claim Rewards Earned for giving RTC Usage

Protocol Diagram

Last updated