Impossible Cloud Network Documentation
  • Welcome to the Impossible Cloud Network
  • Introduction
    • Introduction
    • ICN Protocol Overview
    • Key Features
    • Key Concepts
    • FAQs
    • Legal Disclaimer
  • ICN Glossary
  • ICN Protocol Smart Contracts
  • ICN Participation
    • Stake and Earn
    • Become a Hardware Provider
    • Run a HyperNode
  • Network Architecture
    • Design Overview
    • ScalerNode Network
    • HyperNode Network
    • Satellite Network
    • Services and Apps
    • Smart Contracts
  • ICN Economics
    • Tokenomics
      • The ICNT
        • Circulating Supply
        • Total Supply
        • Token Minting
        • Burn Mechanisms
      • Initial Allocation
      • Token Unlock Schedule
      • Token Utility
    • Builders
      • Access to Network Resources
      • Capacity Allocation
    • Hardware Providers (HPs)
      • HP Rewards
      • Collateral
        • Delegation
        • Slashing
    • ICN Link
  • MiCA Whitepaper
    • Link to MiCA Whitepaper Download (published on May 7, 2025)
Powered by GitBook
On this page
  • HyperNode
  • Challenges
  1. Network Architecture

HyperNode Network

PreviousScalerNode NetworkNextSatellite Network

Last updated 11 days ago

The HyperNode Network operates in a decentralized manner, relying on a global community of individuals on the Internet. A single HyperNode Operator can deploy multiple HyperNodes, each requiring activation through staking at least one ICN Link. On a regular basis, HyperNodes conduct challenges using cryptographic signatures against ScalerNodes to monitor key performance metrics.

HyperNode

HyperNode Operators are responsible for the registration and management of HyperNodes, ensuring that HyperNodes are accessible from the Internet. The registration process of HyperNodes should specify:

  1. Address: Blockchain address for the HyperNode. The private key of this account is used for signing challenges exchanged between daemons and HyperNodes.

  2. Location: Geographic location of the HyperNode following ISO 3166.

  3. Endpoint: FQDN or IP address of the HyperNode, which is reachable from the Internet.

Once registered, the HyperNode Operator launches HyperNode passing the private key as argument. From this point, when one or more ICNLs are staked to the HyperNode, this becomes active and the challenges are started.

Challenges

Challenges within the protocol occur at scheduled intervals known as eras. Each era lasts approximately one hour, measured in blocks. The challenge execution within an era is illustrated below:

To synchronize challenge execution, both Daemons and Hypernodes retrieve data from the era manager smart contract. This data indicates the era’s duration in number of blocks and the starting block; which allows for the approximate calculation of the era’s end time. During each era, the daemon initiates a challenge with every active HyperNodes in ICN. Specifically, each daemon sends one challenge to each active HyperNode per era which follows as:

  1. Daemon sends a challenge request to HyperNode 1.

  2. HyperNode 1 signs the challenge and returns the response to the Daemon.

  3. Both Daemon and HyperNode submit a report to the Satellite Network (for reports, see Satellite Network section)

The ICN protocol currently assesses ScalerNode availability as the percentage of time a daemon is reachable and responds to challenges correctly. To achieve that, HyperNodes must be accessible via the Internet to receive challenges from daemons. Each HyperNode must respond to one availability challenge from each ScalerNode in every era.

Fig. Challenges