How it works

Hyve H3 provides developers with a decentralized storage layer with high bandwidth capacity to store large files. Being decentralized, it does not rely on Hyve-managed server parks around the globe to store this data, but rather it utilizes a distributed set of servers that communicate over a peer-to-peer network.

This section will dive into the decentralized Hyve H3 protocol inner workings and a moderate level of consensus theory and decentralization knowledge is required. For a complete deep dive, we have a Hyve Specs Github.

Architecture

H2's architecture is composed of multiple components

Storage Layer

These storage providers are nodes that run Hyve H3's software and are continuously agreeing on data objects that must be included.

Data Objects

Starting with the data structure. Hyve H3 is an object storage layer and therefore data that you submit is unstructured and will be send as a binary large object (blob). Along with the blob comes a header, the header contains information about the blob itself, including the checksum, time-to-live (TTL), publisher, and metadata tags.

Data publishing

This section is gonna dive into how it works

It should cover:

• Decentralization
• DAG
• Clusters
• proving
• TTL and objects