Architecture

Overview

Constellation Network uses a modular, horizontally scalable architecture designed to support high-throughput applications, verifiable data, and decentralized value transfer. At the heart of the network is the Global Layer 0 (gL0)—known as the Hypergraph—which acts as the final consensus layer and source of truth for all activity across the network.

The Hypergraph aggregates data from multiple sources, including the DAG L1, where native DAG token transactions are validated and structured into blocks using a directed acyclic graph (DAG) model. Once validated, these blocks are submitted to the global L0 for final inclusion in the network’s canonical ledger.

Constellation also supports modular application layers called metagraphs—independent subnets that define their own logic, tokens, and data structures. Each metagraph includes:

• Currency L1: Validates transactions involving its native L0 token.

• Data L1: Validates domain-specific custom data updates.

• Metagraph L0: Packages validated L1 transactions into metagraph snapshots, which represent the metagraph’s finalized state.

Metagraph snapshots are submitted to the Global L0 (Hypergraph) alongside DAG L1 blocks. After undergoing a final round of validation, all accepted data is recorded into a global snapshot, which serves as the immutable, globally recognized record of network state.

This layered architecture allows Constellation to maintain global consistency while supporting decentralized, scalable execution across a diverse set of applications. By anchoring all activity to the Hypergraph, the network ensures both flexibility at the edge and strong consensus at the core.

Metagraph Architecture​

Metagraphs are modular, application-specific components of the Constellation Network. Each metagraph is composed of a Layer 0 (L0) and one or more Layer 1 (L1) layers. Together, these layers manage the ingestion, validation, consensus, and finalization of application data and token transactions within the metagraph.

Core Concepts

• L1 Layers are responsible for ingesting data or transactions, performing initial validation, and reaching consensus using a DAG-based consensus algorithm.

• L0 Layer performs final validation, runs majority-based consensus, and packages validated blocks from L1 layers into metagraph snapshots—the core unit of state on a metagraph.

• Snapshots are submitted from the metagraph L0 to the Global L0 (Hypergraph) for inclusion in the global snapshot chain.

Each layer consists of a cluster of 3 or more nodes. Nodes within a layer communicate over secure HTTP APIs with source-signed messages. Cross-layer communication (e.g., L1 to L0) also uses HTTP with additional security measures to ensure integrity and authentication.

Euclid SDK

Layer Definitions

Metagraph L0

Also referred to as the Currency L0 layer, this is the final consensus and validation layer of the metagraph. It:

• Aggregates blocks from L1 layers

• Forms the metagraph snapshot chain

• Submits finalized snapshots to the Global L0 (Hypergraph)

The metagraph’s L0 snapshot chain is independent of the global snapshot chain but is periodically synchronized with it through snapshot submission.

---

Currency L1

A DAG-based L1 layer dedicated to L0 token transactions. It:

• Validates transactions (signatures, balances, sender addresses)

• Applies any custom logic defined by the metagraph

• Forms blocks from valid transactions

• Runs graph-based consensus over blocks

• Submits finalized blocks to the metagraph L0 layer

---

Data L1

A DAG-based L1 layer for domain-specific custom data updates. It:

• Validates and decodes application-specific data

• Verifies signatures and runs custom validation logic

• Forms blocks of valid data

• Runs DAG-based consensus

• Submits finalized blocks to the metagraph L0 layer

---

Global L0 (Hypergraph)

The Hypergraph is the network-wide Layer 0 consensus layer. It:

• Validates and finalizes metagraph snapshots

• Validates and finalizes DAG L1 blocks

• Aggregates them into global snapshots

• Maintains the canonical record of all activity across DAG L1 and metagraphs

Once a metagraph snapshot is accepted into a global snapshot, it is considered finalized and recorded on-chain.

---

Scaling Considerations

Constellation’s metagraph architecture is optimized for both horizontal and vertical scaling:

Layer	Scaling Method	Description
L1 Layers	Horizontal	Adding more nodes increases throughput and parallel consensus capabilities
L0 Layer	Vertical	Throughput is limited by node resources; scaling requires more powerful nodes. Adding more L0 nodes improves fault tolerance, decentralization, and security, but not throughput

L1 layers benefit from distributed consensus and can scale out as needed to support high data volumes. L0 layers must reach majority consensus and require synchronized participation, so their performance scales vertically rather than horizontally.

Summary

Constellation’s architecture combines localized processing with global consensus to support secure, scalable, and application-specific blockchain infrastructure. Metagraphs operate independently with their own validation and consensus layers, while the Hypergraph serves as the unifying Layer 0 that finalizes state across the entire network. By coordinating all finalized activity into global snapshots, Constellation ensures a consistent, tamper-proof ledger—while enabling parallel execution and innovation at the edge of the network.