HyperCluster Documentation

Complete technical documentation for HyperCluster blockchain, HYPEC token, validator nodes, and Quipu Protocol decentralized storage.

Get Started Block Explorer Join as Validator

Introduction

HyperCluster is a high-performance EVM blockchain built on Hyperledger Besu, combined with Quipu Protocol — a private IPFS network for decentralized storage.

This documentation covers:

  • What HyperCluster is and its core components
  • How the blockchain consensus and staking work
  • How HYPEC (the native token) is used for gas, staking, and rewards
  • How validators participate in securing the network
  • How Quipu Protocol enables decentralized storage
  • How developers can build dApps on HyperCluster
Important:
HyperCluster is infrastructure, not an exchange, broker, or issuer. Applications built on HyperCluster are operated by independent teams and institutions.

Network Specifications

Chain Information

  • Network Name: HyperCluster Mainnet
  • Chain ID: 838838
  • Currency Symbol: HYPEC
  • RPC URL: https://rpc.hypercluster.org
  • WebSocket: wss://ws.hypercluster.org
  • Block Explorer: https://explorer.hypercluster.org
  • Client: Hyperledger Besu

Add to MetaMask

Add HyperCluster to your MetaMask wallet with these settings:

Network Name: HyperCluster
RPC URL: https://rpc.hypercluster.org
Chain ID: 838838
Currency Symbol: HYPEC
Block Explorer: https://explorer.hypercluster.org

HYPEC Token

What is HYPEC?

HYPEC is the native token of the HyperCluster network.

It powers:

  1. Gas & Transaction Fees
    • All transactions and smart contract calls pay gas in HYPEC
    • Fees prevent spam and provide economic sustainability
  2. Validator Staking
    • Validators stake HYPEC to participate in block production
    • Staking provides economic security for the network
  3. Quipu Protocol Rewards
    • Storage node operators earn HYPEC for providing capacity
    • Rewards are recorded on-chain and distributed automatically
  4. Storage Payments
    • Users pay for additional Quipu storage in HYPEC
    • First 5GB is free for all users
Disclaimer: HyperCluster does not provide investment advice. HYPEC is a utility token used to operate the network.

Consensus Mechanism

Overview

HyperCluster uses IBFT 2.0 (Istanbul Byzantine Fault Tolerant) consensus, provided by Hyperledger Besu.

Key Features

  • Immediate Finality: Blocks are final once added — no reorganizations
  • Byzantine Fault Tolerant: Network can tolerate up to ⅓ faulty validators
  • Deterministic Block Times: Consistent block production for predictable performance
  • Energy Efficient: No proof-of-work mining required

Consensus Parameters

  • Block Time: 2 seconds
  • Minimum Validators: 4 for Byzantine fault tolerance
  • Block Reward: Distributed to block proposer
  • Gas Limit: 30,000,000 per block

Validator Participation

Validators in HyperCluster:

  • Must be approved through the validator program
  • Stake HYPEC as economic security
  • Run Besu nodes with proper hardware specifications
  • Participate in block production and consensus voting

Validator Program

Managed VM Arrangement

HyperCluster offers a managed validator program where participants can run validator nodes without managing their own hardware.

Benefits

  • No hardware procurement or maintenance required
  • Professional infrastructure management
  • 24/7 monitoring and support
  • Automatic software updates

Requirements

  • Stake minimum required HYPEC
  • Complete validator onboarding process
  • Agree to validator terms of service

Self-Hosted Validators

For advanced operators who prefer running their own infrastructure:

Hardware Requirements

  • CPU: 8+ cores, modern x86_64 processor
  • RAM: 32GB minimum, 64GB recommended
  • Storage: 1TB+ NVMe SSD
  • Network: 1Gbps connection, low latency

Software Requirements

  • Ubuntu 22.04 LTS or compatible Linux distribution
  • Hyperledger Besu 24.x or later
  • Java 21+ runtime
Note: Contact us at [email protected] to apply for the validator program.

Quipu Protocol

Overview

Quipu Protocol is HyperCluster's private IPFS network designed for decentralized storage. Our vision is to make traditional datacenters obsolete by distributing storage across a global network of nodes.

For Node Operators

Participate in Quipu Protocol by running a storage node:

Hardware Nodes

  • Purchase official Quipu hardware node
  • Pre-configured for optimal performance
  • Plug-and-play setup
  • Includes warranty and support

Staking & Rewards

  • Stake HYPEC to activate your node
  • Node heartbeats tracked via dashboard
  • Rewards recorded on-chain in real-time
  • Payments in HYPEC distributed automatically

Dashboard Features

  • Real-time node status and heartbeat monitoring
  • Storage capacity utilization
  • Earnings history and projections
  • Network statistics

View Public Dashboard

For Storage Users

Store your data on the decentralized Quipu network:

Storage Tiers

  • Free Tier: 5GB included for all users
  • Basic Tier: 50GB - paid in HYPEC
  • Pro Tier: 500GB - paid in HYPEC
  • Enterprise: Custom capacity - contact us

Benefits

  • Censorship Resistant: No single point of failure
  • Always Available: Data replicated across multiple nodes
  • Privacy First: Your data, your control
  • Pay As You Go: Only pay for what you use
Coming Soon: Quipu Protocol documentation with API reference and integration guides.

Stablecoin Bridge

Overview

HyperCluster operates a Stablecoin bridge for seamless cross-chain transfers, enabling easy on-ramp and off-ramp to the HyperCluster network.

Supported Networks

  • Ethereum Mainnet
  • Base
  • Arbitrum
  • TRON
  • Solana
  • Additional networks coming soon

Bridge Process

  1. Connect your wallet to the bridge interface
  2. Select source and destination networks
  3. Enter amount to bridge
  4. Approve and confirm transaction
  5. Receive hUSD on HyperCluster
Security Note: Always verify you're using the official bridge at bridge.hypercluster.org. Never share your private keys.

Developer Guide

Smart Contract Development

HyperCluster is fully EVM-compatible. Deploy your contracts using standard tools:

Hardhat Configuration

// hardhat.config.js
module.exports = {
  networks: {
    hypercluster: {
      url: "https://rpc.hypercluster.org",
      chainId: 838838,
      accounts: [process.env.PRIVATE_KEY]
    }
  },
  solidity: "0.8.20"
};

Foundry Configuration

# foundry.toml
[rpc_endpoints]
hypercluster = "https://rpc.hypercluster.org"

# Deploy with Foundry
forge create --rpc-url hypercluster \
  --private-key $PRIVATE_KEY \
  src/MyContract.sol:MyContract

Web3.js Example

const Web3 = require('web3');

const web3 = new Web3('https://rpc.hypercluster.org');

// Get latest block
const block = await web3.eth.getBlockNumber();
console.log('Latest block:', block);

// Get HYPEC balance
const balance = await web3.eth.getBalance(address);
console.log('Balance:', web3.utils.fromWei(balance, 'ether'), 'HYPEC');

Developer Program

Apply for our developer program to receive:

  • Gas subsidies for development and testing
  • Technical support from our team
  • Early access to new features
  • Potential grant funding for innovative projects

Security Considerations

Technology Risks

  • Protocol bugs or vulnerabilities
  • Smart contract risks in dApps
  • Bridge security and cross-chain risks

Economic Risks

  • Token price volatility
  • Liquidity conditions
  • Staking and slashing risks

Best Practices

  • Keep your private keys secure
  • Verify contract addresses before interacting
  • Use hardware wallets for large holdings
  • Stay updated on security announcements

Responsible Disclosure

Found a security issue? Report it to [email protected]

This documentation covers HyperCluster powered by Hyperledger Besu with IBFT 2.0 consensus and Quipu Protocol for decentralized storage.