Loading
Loading

Blockchain-backed cloud: storage, VMs, and apps with unmatched transparency, trust, and power.
Neuron registration trends
Organizations managing distributed storage and compute resources face coordination challenges: proving node performance across geographies, settling payments fairly when capacity is shared, and preventing bad actors from degrading service. Traditional centralized infrastructure operators own hardware outright, but decentralized operators pool resources and need cryptographic proof that work was actually performed and rewarded proportionally.
A decentralized infrastructure network solves this through reputation tracking, byte-block accrual (storing work performed), and onchain settlement. Miners earn rewards by pinning files (storage) or running virtual machines (compute); validators earn by securing the network and verifying miner performance. Rewards flow from a marketplace that prices storage and compute requests, with stakers earning from the network's economic activity through era-based distribution.
Hippius implements this pattern as a Substrate blockchain integrated with Bittensor. Storage miners run IPFS nodes; compute miners operate as hypervisors; validators collect offchain metrics and propose era payouts. The arion pallet tracks byte-blocks (storage × time) and settles miner payments monthly. The marketplace pallet prices requests and routes revenue to validators and miners. The alpha-bridge pallet ensures daily emission from Bittensor is backed by a multisig escrow and distributed via guardian attestation—no single actor can mint tokens without observed escrow activity.
Use cases were auto-generated from the GitHub repository and may not reflect the latest changes.
Hippius is a Bittensor subnet providing decentralized infrastructure through a Substrate-based blockchain. It enables distributed file storage via IPFS integration, virtualized compute resources, and marketplace capabilities with reputation-based worker management, while using a Proof-of-Stake consensus model with era-based reward distribution to validators and miners.
Hippius operates as a Substrate-based blockchain with storage miners running IPFS nodes and compute miners operating as hypervisors. Validators verify network operations and collect performance metrics via offchain workers. The marketplace pallet handles storage/compute requests; the arion pallet tracks byte-block accrual and settlement; the bank pallet manages payouts with existential deposit guards; the alpha-bridge pallet gates daily emission distribution from Bittensor multisig with guardian attestation.
Era payouts sweep accumulated rewards to validators every 6 hours; miner payments settle asynchronously through the hippocampus deposit system. RPC API provides comprehensive metrics access for monitoring node performance, file distribution, VM deployments, and reward tracking.
Validators receive 75% of marketplace revenue split equally across all active validators in each 6-hour era. Miners accrue rewards through byte-blocks (bytes × blocks held), which are converted to tokens using the formula: tokens = byte_blocks × price_usd_per_gib_block × 10^18 / (2^30 × token_price_usd). When payout pool is insufficient for total due, pro-rata allocation ensures each miner receives (their_due × pool / total_due) rounded down, with arrears deferred.
Blockchain-backed cloud: storage, VMs, and apps with unmatched transparency, trust, and power.
This information was auto-extracted from the GitHub repository and may be incomplete or out of date. Always refer to the subnet's GitHub repository for the latest instructions.
Slashing penalties apply for validator misbehavior. Storage miners also earn from file replication and pinning verification.
The sections above were auto-generated from the GitHub repository and may not reflect the latest changes. View repository
FAQs were auto-generated from the GitHub repository and may not reflect the latest changes.
Holder & total-staked metrics as of 1h ago (hourly snapshot)
Storage miners require IPFS node; compute miners operate as hypervisors for virtualized resources
Validators require archive mode pruning and run offchain workers for monitoring
Clone the Hippius repository
git clone https://github.com/thenervelab/thebrain.git && cd thebrain
Build the Hippius node binary in release mode
cargo build --release
Download custom chain specification file
wget <url_to_get_customSpec_file>
Run miner node with bootnodes and offchain worker enabled
./target/release/hippius --bootnodes /ip4/57.128.82.161/tcp/30333/p2p/<Node_Identity_of_Validator> --chain customSpec.json --offchain-worker Always
Insert miner keypair using author.InsertKeys RPC with key type 'hips'
Submit JSON-RPC: {"jsonrpc": "2.0", "method": "author_insertKey", "params": ["hips", "<mnemonic or seed>", "<public_key>"], "id": 1}Register miner node on-chain with network information
Register via registration pallet with Node Identity, IPFS Node ID, and node type 'miner'
Clone the Hippius repository
git clone <repository_url> && cd <repository_name>
Build the Hippius node binary, generating executable at ./target/release/hippius
cargo build --release
Clean up old chain data and database files to avoid conflicts
rm -rf /root/.local/share/hippius/chains/hippius-testnet/db && rm -rf /root/.local/share/hippius/chains/hippius-testnet/frontier
Generate custom chain specification file
rm -rf customSpec.json && ./target/release/hippius build-spec --disable-default-bootnode --chain testnet > customSpec.json
Create folder and place validator keypair files
mkdir /path/to/keypair && cp <keypair_files> /path/to/keypair/
Insert validator keypair using author.InsertKeys RPC with key type 'hips'
Submit JSON-RPC: {"jsonrpc": "2.0", "method": "author_insertKey", "params": ["hips", "<mnemonic or seed>", "<public_key>"], "id": 1}Start validator node with validator flag, archive pruning, and offchain workers enabled
./target/release/hippius --chain testnet --validator --base-path /path/to/keypair --unsafe-rpc-external --rpc-cors all --telemetry-url "wss://telemetry.polkadot.io/submit/ 1" --offchain-worker Always --pruning=archive
Register validator node on the network
Register validator on-chain using Registration Pallet with node identity (from startup logs), IPFS node ID, and node type 'validator'
Stake and activate validator in the network
Bond sufficient funds for staking and set validator as active