Constellation Network
IntroductionFundamentalsFor DevelopersNode Validators
  • Index
  • Validator Node Guides
    • 💰Delegated Staking
      • What is delegated staking?​
      • For Node Operators
      • Understanding Delegated Staking
      • Prerequisites
      • Create Delegated Staking Configuration
      • First Time Configuration
      • Modify Existing Configuration
      • Add/Update Delegating Staking Parameters
      • Update Delegated Staking
      • Duplicate Update
      • Status Command
    • 🚧Build Your Node
      • Create Discord Account
      • 🗒️Node Operator Notes
      • ⚙️Node Specifications
      • 🚧Generic Build a VPS Guide
      • ☁️Cloud Provider Specific
        • 🚧Build AWS EC2 Instance
        • 🚧Build DigitalOcean Droplet
        • 🚧Build Hetzner Server
      • 🚉First Time Connection Guide
      • 💽The nodectl utility
      • Download nodectl
      • 🏗️Turn your VPS into a Node
        • 🚩Node Prerequisites
        • 🐇Quick Install Guide
        • 🎨Normal Install Guide
        • 🛠️Manual Installation
      • 🏆Authorize to Join Hypergraph or metagaph
    • 💰Collateralize Your Node
    • 1️⃣First Time Cluster Connection
    • 💫Enable Auto Restart
    • 📂Operational Guides
      • ♻️Restart Validator Node Guide
      • 🐎Upgrade Tessellation Quick Start
      • 🏭Upgrade Tessellation Guide
      • 🏗️Reinstallation Guide
      • ♻️Backup/Restore a P12 KeyStore
      • 🚋Migrate V1 to V2 - P12 Keystore
  • 👑MainNet
    • MainNet & IntegrationNet Quick Start Guide
    • 🚧Upgrade Tessellation to v3
  • 🥅IntegrationNet
    • 🧪IntegrationNet Quick Start Guide
  • Metagraphs
    • 🚪Dor metagraph
      • 🚪Dor Validator Onboard Guide
      • 🚪Understanding Rewards
      • 🚪Technical Procedures
        • 🚪Build Dor Validator Node
  • 📚References
    • 📚nodectl Command Reference
    • Firewall Settings Table
    • 🔐SSH Remote Access
      • 🔑Create SSH Keys
      • 📁Upload SSH Public Key
      • 🔐Securing SSH Access
      • ♻️How to SSH into VPS
    • 🍴Node Fork Types
    • 🗝️P12 Keystore
    • 🏐Tarball
    • 💻Virtual Private Server
  • GitHub nodectl utility
  • Run a Node Validator
  • Lattice Dashboard
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
  • Forks in the Constellation Network
  • What is a Majority Fork?
  • What is a Minority Fork?
  • Considerations
  • Implications in Constellation’s Network
  • Final Thoughts

Was this helpful?

Export as PDF
  1. References

Node Fork Types

Forks in the Constellation Network

In the context of the Constellation Network's Hypergraph or metagraph clusters, the concepts of majority fork and minority fork relate to how the network reaches consensus during discrepancies, synchronization issues, or splits in transaction history.


What is a Majority Fork?

A majority fork occurs when the majority of validator nodes in the network agree on a particular version of the transaction history. This version becomes the canonical chain and is recognized as the valid state of the network.

Unlike traditional linear blockchains, Constellation uses a Directed Acyclic Graph (DAG) architecture. In this system, the majority fork represents the most widely accepted state of the DAG, ensuring consistency, correctness, and security.

Majority forks typically occur during routine operations—such as when one of the three source nodes in a cluster is restarted during an upgrade or maintenance cycle.

Examples:

  • Tessellation is upgraded from version vX.0.0 to vX.0.1.

  • Two conflicting transaction histories emerge, and the one accepted by most validators becomes part of the official ledger.


What is a Minority Fork?

A minority fork occurs when a smaller subset of nodes deviates from the consensus and follows an alternate transaction history. This version of the DAG is generally considered invalid or non-authoritative because it lacks sufficient validator support.

Minority forks may arise due to:

  • Network partitioning

  • Incomplete upgrades

  • Misconfigurations

  • Malicious behavior

In the Constellation Network, these forks are automatically disregarded by consensus protocols, as they fail to meet the quorum thresholds for validation.

Example:

  • Tessellation is upgraded to vX.0.1, but one or more nodes remain on vX.0.0, resulting in those nodes temporarily diverging into a minority fork.


Considerations

  • Transactions included in a minority fork may temporarily appear valid to affected nodes.

  • Once consensus re-aligns with the majority, those transactions are rejected and excluded from the network’s official state.


Implications in Constellation’s Network

Security and Stability

Prioritizing the majority fork ensures that only the most secure and validated version of the ledger is retained, which protects against double spending and preserves network reliability.

Fork Resolution

The network includes automated mechanisms to reconcile forks. Nodes on a minority path are guided back to the consensus-approved chain, restoring full alignment across the network.


Final Thoughts

The majority fork represents the unified, authoritative state of the Constellation Network. The minority fork is a temporary divergence, typically caused by upgrades or desynchronization, and is automatically corrected through the network’s consensus process.

PreviousHow to SSH into VPSNextP12 Keystore

Last updated 1 month ago

Was this helpful?

📚
🍴