Skip to main content

Node Architecture

In the HyMatrix network, nodes are the core units of computation and communication. Each node is responsible not only for executing user tasks locally but also for managing virtual machine environments, forwarding messages, assigning transaction order, and generating verifiable logs—ultimately enabling a decentralized, verifiable, and high-performance computing network.

Key Responsibilities​

In HyMatrix’s architecture, nodes are more than just “compute providers”—they are fully decentralized compute service agents that take on the following critical roles:

  • Managing Virtual Machines: Nodes create and manage isolated, standardized, and reproducible VM environments locally (supporting Docker, WASM, EVM, etc.) to run user tasks.
  • Receiving Transactions: Once a VM is instantiated, nodes receive and queue user-submitted task transactions.
  • Transaction Scheduling: Nodes assign strict Nonces (sequence numbers) for each transaction within a VM to ensure consistent and verifiable execution order, avoiding concurrency-induced state divergence.
  • Message Routing: When one VM needs to call or send messages to another, nodes are responsible for routing these cross-VM messages in a decentralized fashion.
  • Executing Tasks: Nodes leverage local hardware (CPU, GPU) to run the VM task logic and complete high-performance computations.
  • Generating Logs: Nodes record input parameters, call sequences, execution steps, and output results to produce structured, replayable, and immutable execution logs, which are uploaded to permanent storage (e.g., Arweave).
  • Participating in the Economic Model: By staking tokens, nodes can freely join or exit the network, earn task fees, and take on the risk of being challenged. Staked assets can be reclaimed upon exit, enabling flexible participation.

The Registry Module​

The Registry is the global directory for all nodes and virtual machines in the HyMatrix network. It ensures discoverability and interoperability in a decentralized environment by maintaining a synchronized registry accessible to all nodes.

  • Node Registration Info: When a node joins the network, it registers its metadata—including name, description, public-accessible URL, and wallet address—into the Registry, allowing other users and nodes to find and interact with it.
  • VM-to-Node Mapping: When a new VM is created, the node registers a mapping between that VM and itself in the Registry. This enables the network to locate the physical node hosting any VM. Since nodes are reachable via public internet addresses, users can easily access these VMs through the Registry.

The Registry acts as a shared directory across the network, allowing decentralized discovery, communication, and collaboration between all nodes and VMs.

Execution Flow (Simplified)​

  1. Registration and Staking

    • Node registers with the network using its wallet address
    • Stakes AX tokens as an economic guarantee
    • Registers node information in the Registry

  2. VM Creation

    • Node launches a VM according to task requirements
    • Records VM-to-node mapping in the Registry

  3. Transaction Reception

    • Users submit task transactions to the node via the network
    • Node receives and records the transactions

  4. Nonce Assignment

    • Node assigns strict Nonce values per VM to enforce deterministic transaction order

  5. Task Execution

    • Executes transactions sequentially inside the VM
    • Uses local hardware acceleration (e.g., GPU) for complex computations

  6. Log Generation and Storage

    • Generates a full execution log
    • Uploads it to immutable, permanent decentralized storage

  7. Message Forwarding

    • If the VM needs to call another VM, the node routes the message to the destination VM/node
    • Ensures verifiable and reachable cross-VM interactions in a decentralized setting

Core Features​

  • Unified Model: No layered roles—any node can receive transactions, create VMs, execute tasks, route messages, and generate logs.
  • Decentralization: Nodes operate independently without centralized orchestration.
  • Permissionless Entry: Nodes can freely join and exit the network via token staking and unstaking.
  • Verifiability: All executions leave behind replayable logs that anyone can validate.
  • Economic Incentives and Penalties: Nodes earn fees for execution, but may be slashed if they misbehave or fail verification.
  • Heterogeneous Task Support: From simple contracts to AI inference, all can be executed inside VMs managed by the node.
  • Global Synchronized Registry: The Registry ensures that all nodes and VMs are discoverable and addressable network-wide, enabling decentralized service discovery and interoperability, and mapping VMs to physical internet-accessible nodes for seamless user interaction.

In summary, a HyMatrix node is not just a compute machine—it’s an all-in-one decentralized computing service provider: creating VMs, receiving and scheduling transactions, assigning Nonces to enforce order, routing messages, executing tasks, registering with the Registry, and generating verifiable logs. The economic model ensures honest, secure, and flexible participation in the network.