Corex Network
  • Concept
  • INTRODUCTION
    • Capabilities
    • General Architectural Outline
  • Joint Computing Environments
    • Outline and Operation
    • Standards and Cryptography
    • Auxiliary Channel Protection
  • NODES
    • Setup & Configuration
    • Management & Incentives
    • Efficiency and Stability Monitoring
    • Secure Execution Zones
    • Node Staking
      • Delegation Dynamics & Vesting Durations
  • CLUSTERS
    • Function and Formation
      • Fork & Migrate
    • Authorization & Incentives
    • Acceptance & Allocation
  • COMPUTATIONS
    • Identifying a Computation
      • Computation Units
    • Computation Initiation
      • Computation Timeline
      • Computational Input Data
  • TOKENOMICS
    • $HEAI
    • Liquidity Management
  • SOCIALS
    • Website
    • Twitter
    • Telegram
Powered by GitBook
On this page
  1. NODES

Setup & Configuration

When setting up a node, specific metadata must be entered and the node must be linked to a node operator, which represents the party responsible for running the node. Each node has its own specific metadata, even if operated by the same entity, allowing operators to manage multiple nodes independently within the network. Each node has its own unique metadata, distinct from the node operator's metadata, as a single operator can manage multiple nodes in various regions. The metadata for a specific node includes IP & Port details and Jurisdiction.

Node Operators

Node Operators are metadata entities managing the nodes. A Node Operator can control multiple nodes simultaneously and their metadata include the Jurisdiction and URL (similar to a profile showcasing the operator's services and reputation)

PreviousAuxiliary Channel ProtectionNextManagement & Incentives

Last updated 7 months ago