Introduction to the HyveDA Protocol Docs

This section of the documentation will guide you through the architecture behind HyveDA. We'll dive into the lifecycle of blobs and the security considerations we've made.

The HyveDA protocol consists of a few different components and layers that are managed and maintained by Hyve. In production, these layers can handle a throughput of over 1GB/s. All components are completely open source software that anyone can run and operate, even in a local environment.

What is HyveDA

HyveDA is a middleware data availability layer built on Ethereum that empowers decentralized networks, such as Layer2s and Validiums, to achieve unparalleled potential data publishing throughput. Our solution is specifically designed to meet to needs of applications where data demands are exceptionally high, such as DePIN, AI apps and rollups, parallel execution environments, and L2s.

Our vision

HyveDA's core principle is permissionless participation. Unlike traditional data availability committees, which often rely on permissioned networks and centralized batch proposers, HyveDA employs a permissionless data availability committee (DAC). This ensures that anyone can help maintain data availability and eliminates the need for a single point of authority, reducing security assumptions and increasing the scalability.

Each node in the DAC is supported by a delegated stake via Symbiotic, which provides economic incentives for honest participation. This stake is not for show—misbehavior results in slashing, ensuring that only reliable nodes contribute to the network's data availability.

Why HyveDA?

HyveDA adopts unique design principles in the protocol that ensures permissionless participation, horizontal scalability, security, and unmatched throughput. This leads to some key features in our network:

• Elimination of a Centralized Proposer: In HyveDA, there is not a single batch proposer. This choice eliminates the bottleneck in throughput and removes a security assumption on a single authority in the network. Instead, anyone is free to write blobs to the DAC as long as there is a valid fee paid for the blob. The DA network adopts a unique epoch and P2P attestation strategy that ensures smooth processing of incoming valid blobs.
• No Consensus: Unlike modular blockchains, middleware DAs do not require consensus to provide data availability attestations. By eliminating consensus, DA nodes barely communicate with each other and therefore the network of DA Nodes can horizontally scale without much effort. This ultimately leads to higher throughputs.
• Permissionless Participation: Any entity can become a part of the DAC by staking through Symbiotic. This open model ensures widespread participation and enhances network security through decentralization.
• Shared Security: The delegated stakes that back each DAC member are subject to slashing if any node acts maliciously, thereby reinforcing the trustworthiness of the network.

Want to learn more?

Ready to dive into HyveDA?

• If you're interested in learning more about the choice for middleware DA, start with The DA(C) Problem
• If you're interested in understand the HyveDA network blob lifecycle, start with the Blob Lifecycle and Components.
• If you're interested in the permissionless architure, start with DA Node and Security.