Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Concepts
    • Architecture
  • IntegrationNet
  • API Reference
    • DAG4.js
      • Intro to dag4.js
      • Interacting with Wallets
      • Connecting to the Network
      • Sending Transactions
      • Message Signing
      • Metagraph Tokens
      • Dag4.js Example Apps
    • Hypergraph APIs
  • Metagraph APIs
  • Block Explorer APIs
  • Integration Guides
    • Transaction Signing
    • Delegated Staking
Powered by GitBook

Main

  • Website
  • Get DAG
  • Explore Projects
  • Partners

Socials

  • Telegram
  • Discord
  • X (Twitter)

Tools

  • Wallet
  • DAG Explorer
  • Coingecko

© 2025 CONSTELLATION NETWORK

On this page
  • Architecture
  • DAG​
  • DAG L1​
  • Global L0​
  • Metagraph Tokens​
  • Metagraph L1​
  • Metagraph L0​
  • Global L0​

Was this helpful?

Export as PDF
  1. Concepts

Architecture

NextIntegrationNet

Last updated 1 month ago

Was this helpful?

Architecture

Transaction Lifecyle

Interested in more in-depth information about the currency transaction lifecycle and data flow within the Hypergraph? See for more info.

Constellation Network architecture overview

In order to make the most of Constellation Network APIs, a brief understanding of the architecture of the network is useful. The Hypergraph consists of multiple layers of networks of individual responsibility through which transactions flow. Each of the major network layers has REST API endpoints available with distinct functionality. Transactions are sent to the outermost layer, labeled as L1 networks in the graphic, before being processed into a state snapshot in an L0 layer.

DAG transactions are sent to the DAG L1 network which bundles the transactions into blocks and sends them to the Global L0 for inclusion into global snapshots. Snapshots are then indexed by the Block Explorer via a snapshot streaming service that processes them.

Metagraph token transactions flow in a similar way from the metagraph currency L1 where they're received, bundled into blocks, and then passed to the currency L0 layer to be included in metagraph snapshots. The metagraph snapshots are then submitted to the Global L0 to be included in global snapshots and eventually indexed into the Block Explorer via the snapshot streaming service.

The APIs for each of the L1 and L0 layers is nearly identical with a few minor differences, namely endpoint naming of /dag for DAG endpoints and /currency for currency endpoints. You can explore the API specs for each in the Network APIs sections below.

In summary, the functionalities of the different APIs for DAG and metagraph tokens are as follows:

  • DAG transactions are sent to this API via the /transactions POST endpoint.

  • Pending transactions can be queried through this API via the /transactions/:hash endpoint.

  • The address lastRef for an address can be queried here as well.

  • Query global snaphots

  • Query DAG supply and address balances

  • Submit metagraph (state channel) snapshots

  • DAG transactions are sent to this API via the /transactions POST endpoint.

  • Pending transactions can be queried through this API via the /transactions/:hash endpoint.

  • The address lastRef for an address can be queried here as well.

  • Query metagraph snapshots

  • Query metagraph token supply and address balances

  • Submit metagraph (state channel) snapshots

DAG

DAG L1

Global L0

Metagraph Tokens

Metagraph L1

Metagraph L0

Global L0

​
​
​
​
​
​
​
Network Fundamentals Architecture