With the amount of new subnets being added it can be hard to get up to date information across all subnets, so data may be slightly out of date from time to time
With the amount of new subnets being added it can be hard to get up to date information across all subnets, so data may be slightly out of date from time to time
Hippius (Subnet 75) is a decentralized cloud storage subnet within the Bittensor ecosystem. It was introduced in March 2025 as the “missing piece” to provide persistent memory/storage for Bittensor’s decentralized AI network. In essence, Hippius offers blockchain-backed distributed storage services (and in the future, compute) that complement Bittensor’s machine-learning focused subnets. By delivering transparent, decentralized, and anonymous cloud storage, Hippius enables Bittensor to retain data, models, and other assets in a trustless manner, filling a role similar to the “memory” of Bittensor’s “decentralized mind.”
Within the Bittensor ecosystem, each subnet produces a specific digital commodity. Hippius’s commodity is cloud storage: it allows users and dApps to store files and data across a distributed network of nodes, with all usage and payments recorded on-chain for transparency. This subnet’s purpose is to provide reliable and censorship-resistant storage for AI applications and beyond, tightly integrated with Bittensor’s incentive and reward mechanisms. As the official documentation states, “Hippius is the solution to storage on Bittensor,” delivering decentralized file hosting (via IPFS) and an S3-compatible object storage service, all underpinned by blockchain trust.
Hippius (Subnet 75) is a decentralized cloud storage subnet within the Bittensor ecosystem. It was introduced in March 2025 as the “missing piece” to provide persistent memory/storage for Bittensor’s decentralized AI network. In essence, Hippius offers blockchain-backed distributed storage services (and in the future, compute) that complement Bittensor’s machine-learning focused subnets. By delivering transparent, decentralized, and anonymous cloud storage, Hippius enables Bittensor to retain data, models, and other assets in a trustless manner, filling a role similar to the “memory” of Bittensor’s “decentralized mind.”
Within the Bittensor ecosystem, each subnet produces a specific digital commodity. Hippius’s commodity is cloud storage: it allows users and dApps to store files and data across a distributed network of nodes, with all usage and payments recorded on-chain for transparency. This subnet’s purpose is to provide reliable and censorship-resistant storage for AI applications and beyond, tightly integrated with Bittensor’s incentive and reward mechanisms. As the official documentation states, “Hippius is the solution to storage on Bittensor,” delivering decentralized file hosting (via IPFS) and an S3-compatible object storage service, all underpinned by blockchain trust.
Hippius extends Bittensor by offering:
Decentralized data storage: A network of storage nodes (miners) store and serve data, ensuring no single point of failure. This benefits Bittensor by giving AI models and services a place to persist datasets, model checkpoints, or outputs in a distributed way.
On-chain transparency and incentives: Usage of Hippius is metered and logged on its Substrate blockchain, with a crypto-economic model rewarding those who provide storage resources. This aligns with Bittensor’s broader tokenomics, using blockchain incentives (in $TAO and subnet-specific tokens) to sustain the service.
Integration with Bittensor’s network: Hippius is not a standalone Layer-1 but a Bittensor subnet (network ID 75) that connects to the Bittensor metagraph (main chain). Its validators report performance metrics (so-called “weights”) back to the main Bittensor chain, allowing Hippius to participate in Bittensor’s consensus-based reward distribution (Dynamic TAO). This means a portion of Bittensor’s TAO token emissions is allocated to Hippius’s contributors based on the quality and usage of the storage service they provide.
By fulfilling these roles, Hippius aims to become the decentralized storage layer for all Bittensor applications, and eventually a general-purpose decentralized cloud (including computation). Community members have emphasized that Hippius brings “true decentralized storage with a bulletproof economic model” to the $TAO ecosystem, akin to how Filecoin or Arweave provide decentralized storage but with the key difference of being natively integrated into Bittensor’s AI-driven network.
Technical Architecture and Functioning
Hippius is built on a custom Substrate blockchain (a standalone chain) that operates as Subnet 75 within Bittensor. This design gives Hippius its own ledger, consensus, and token, while still linking it to Bittensor’s main chain through a bridge and shared incentive model. Below are key technical aspects of how the subnet functions:
Consensus and NPoS: Hippius uses the Blind Assignment for Blockchain Extension (BABE) consensus algorithm for block production, and Nominated Proof-of-Stake (NPoS) for security. This means a set of validators produce blocks and finalize the Hippius chain, and token holders (nominators) can stake to elect/secure these validators. The validator set in Hippius maintains the chain and also coordinates storage tasks. Validators earn rewards for block production and for faithfully reporting storage performance to Bittensor’s main chain.
Native Token (“Alpha”) and Dynamic TAO: The native currency on the Hippius chain is informally called Alpha (α). Under Bittensor’s Dynamic TAO system, each subnet has its own token that is backed by and convertible to TAO through a reserve pool. In Hippius’s case, users obtain Alpha by staking TAO into Hippius’s reserve (via the bridge) and can convert back by redeeming Alpha for TAO. The on-chain automated market maker determines the price of Alpha based on the ratio of TAO staked vs. Alpha in circulation. This dynamic token design allows Hippius’s value to be directly tied to the broader TAO economy, and it enables cross-chain transfers. (Phase 4 of the launch is enabling this Alpha–TAO bridge, allowing Alpha to move between Hippius and the main Bittensor chain.)
Storage Services (IPFS and S3): Hippius provides two types of storage for clients:
Both storage systems run in parallel, giving users a choice between content-addressed IPFS (useful for public or static content) and bucketed object storage (useful for private or mutable data). In both cases, data is encrypted and anonymized; the network supports end-to-end encryption so that miners cannot read user data, and user identity is handled via cryptographic keys (mnemonics) rather than accounts/passwords.
Miner and Validator Roles: Hippius nodes can take on specialized roles, each with off-chain workers that integrate with on-chain logic:
Storage Miners: These are subdivided into IPFS miners and S3 miners as described. They run the storage infrastructure – for IPFS, running go-ipfs nodes; for S3, running storage servers – and continuously report their capacity and performance. Off-chain worker processes on miners handle tasks like monitoring file health, ensuring replication (making multiple copies across nodes), and responding to read/write requests from clients. Miners must also prove uptime and reliability; if they go offline or lose data, the network can detect this (through validators) and apply penalties (slashing).
Compute Miners (Future): The architecture anticipates compute miners, which will provide virtual machine environments and possibly GPU-accelerated compute in the future. These miners would act as decentralized cloud “VM” providers, running sandboxed computations or hosting applications. (Support for compute is planned but not active at initial launch – see Roadmap below.)
Validators: Validators form the backbone of the Hippius blockchain and also coordinate the marketplace. A validator’s duties include verifying blocks and transactions, maintaining consensus, and critically, assigning storage tasks and evaluating miners’ performance. When users make storage requests, validators receive these requests (via the marketplace) and decide which miners will serve the data or store new data. They gather metrics from miners (e.g. response times, uptime) and compute “weights” – a performance score for each miner over time. These weights are reported to the Bittensor main chain as part of the Yuma consensus, which in turn influences how much TAO emission Hippius miners and validators earn from the network. Validators are also responsible for enforcing rules (they can blacklist/ban misbehaving nodes and trigger slashing if a miner loses data or cheats).
Marketplace and Usage Flow: Hippius features a built-in marketplace system that intermediates between clients (users) and the storage miners. When a client uses the Hippius dashboard or API to purchase storage, the process is as follows:
Security and Reliability: Hippius is designed with multiple security measures. Identities are secured by Bittensor’s mnemonic authentication (wallet seed-phrases serve as both identity and encryption keys for users), meaning users do not rely on passwords or third-party accounts – losing your secret key means losing access, enforcing self-custody of credentials. All data can be encrypted client-side using those keys, providing end-to-end security. On the network side, communication between validators and miners is secured (they likely use encrypted channels and handshakes to prevent tampering). The chain implements slashing of misbehaving nodes – for example, if a validator detects that a miner who was supposed to store a file is unreachable or has lost the file, that miner’s stake can be slashed as a penalty. There are also reputational mechanisms: validators can ban or blacklist miners that repeatedly fail or provide poor service, ensuring the storage remains reliable for users. By having multiple miners replicate the same data, Hippius provides redundancy: even if some nodes go offline, data is not lost. This distributed design naturally protects against censorship and server outages, as no single miner controls the availability of content.
In practical terms, the Hippius network has quickly grown to significant capacity. Within a couple of weeks of launch, it reached its initial limit of 256 registered miner seats (UIDs) and achieved nearly 900 TB of aggregate storage provided by the community’s miners. This demonstrates a high supply of storage ready to be utilized. All operations (storage deals, node performance, etc.) can be monitored via Bittensor’s block explorer and the Hippius dashboard, giving a clear view into the subnet’s functioning. Overall, the technical architecture of Hippius combines a blockchain (for consensus, accounting, and coordination) with off-chain storage tech (IPFS, S3 servers) and clever incentive alignment to create a decentralized storage cloud that is both useful and economically sustainable.
Hippius extends Bittensor by offering:
Decentralized data storage: A network of storage nodes (miners) store and serve data, ensuring no single point of failure. This benefits Bittensor by giving AI models and services a place to persist datasets, model checkpoints, or outputs in a distributed way.
On-chain transparency and incentives: Usage of Hippius is metered and logged on its Substrate blockchain, with a crypto-economic model rewarding those who provide storage resources. This aligns with Bittensor’s broader tokenomics, using blockchain incentives (in $TAO and subnet-specific tokens) to sustain the service.
Integration with Bittensor’s network: Hippius is not a standalone Layer-1 but a Bittensor subnet (network ID 75) that connects to the Bittensor metagraph (main chain). Its validators report performance metrics (so-called “weights”) back to the main Bittensor chain, allowing Hippius to participate in Bittensor’s consensus-based reward distribution (Dynamic TAO). This means a portion of Bittensor’s TAO token emissions is allocated to Hippius’s contributors based on the quality and usage of the storage service they provide.
By fulfilling these roles, Hippius aims to become the decentralized storage layer for all Bittensor applications, and eventually a general-purpose decentralized cloud (including computation). Community members have emphasized that Hippius brings “true decentralized storage with a bulletproof economic model” to the $TAO ecosystem, akin to how Filecoin or Arweave provide decentralized storage but with the key difference of being natively integrated into Bittensor’s AI-driven network.
Technical Architecture and Functioning
Hippius is built on a custom Substrate blockchain (a standalone chain) that operates as Subnet 75 within Bittensor. This design gives Hippius its own ledger, consensus, and token, while still linking it to Bittensor’s main chain through a bridge and shared incentive model. Below are key technical aspects of how the subnet functions:
Consensus and NPoS: Hippius uses the Blind Assignment for Blockchain Extension (BABE) consensus algorithm for block production, and Nominated Proof-of-Stake (NPoS) for security. This means a set of validators produce blocks and finalize the Hippius chain, and token holders (nominators) can stake to elect/secure these validators. The validator set in Hippius maintains the chain and also coordinates storage tasks. Validators earn rewards for block production and for faithfully reporting storage performance to Bittensor’s main chain.
Native Token (“Alpha”) and Dynamic TAO: The native currency on the Hippius chain is informally called Alpha (α). Under Bittensor’s Dynamic TAO system, each subnet has its own token that is backed by and convertible to TAO through a reserve pool. In Hippius’s case, users obtain Alpha by staking TAO into Hippius’s reserve (via the bridge) and can convert back by redeeming Alpha for TAO. The on-chain automated market maker determines the price of Alpha based on the ratio of TAO staked vs. Alpha in circulation. This dynamic token design allows Hippius’s value to be directly tied to the broader TAO economy, and it enables cross-chain transfers. (Phase 4 of the launch is enabling this Alpha–TAO bridge, allowing Alpha to move between Hippius and the main Bittensor chain.)
Storage Services (IPFS and S3): Hippius provides two types of storage for clients:
Both storage systems run in parallel, giving users a choice between content-addressed IPFS (useful for public or static content) and bucketed object storage (useful for private or mutable data). In both cases, data is encrypted and anonymized; the network supports end-to-end encryption so that miners cannot read user data, and user identity is handled via cryptographic keys (mnemonics) rather than accounts/passwords.
Miner and Validator Roles: Hippius nodes can take on specialized roles, each with off-chain workers that integrate with on-chain logic:
Storage Miners: These are subdivided into IPFS miners and S3 miners as described. They run the storage infrastructure – for IPFS, running go-ipfs nodes; for S3, running storage servers – and continuously report their capacity and performance. Off-chain worker processes on miners handle tasks like monitoring file health, ensuring replication (making multiple copies across nodes), and responding to read/write requests from clients. Miners must also prove uptime and reliability; if they go offline or lose data, the network can detect this (through validators) and apply penalties (slashing).
Compute Miners (Future): The architecture anticipates compute miners, which will provide virtual machine environments and possibly GPU-accelerated compute in the future. These miners would act as decentralized cloud “VM” providers, running sandboxed computations or hosting applications. (Support for compute is planned but not active at initial launch – see Roadmap below.)
Validators: Validators form the backbone of the Hippius blockchain and also coordinate the marketplace. A validator’s duties include verifying blocks and transactions, maintaining consensus, and critically, assigning storage tasks and evaluating miners’ performance. When users make storage requests, validators receive these requests (via the marketplace) and decide which miners will serve the data or store new data. They gather metrics from miners (e.g. response times, uptime) and compute “weights” – a performance score for each miner over time. These weights are reported to the Bittensor main chain as part of the Yuma consensus, which in turn influences how much TAO emission Hippius miners and validators earn from the network. Validators are also responsible for enforcing rules (they can blacklist/ban misbehaving nodes and trigger slashing if a miner loses data or cheats).
Marketplace and Usage Flow: Hippius features a built-in marketplace system that intermediates between clients (users) and the storage miners. When a client uses the Hippius dashboard or API to purchase storage, the process is as follows:
Security and Reliability: Hippius is designed with multiple security measures. Identities are secured by Bittensor’s mnemonic authentication (wallet seed-phrases serve as both identity and encryption keys for users), meaning users do not rely on passwords or third-party accounts – losing your secret key means losing access, enforcing self-custody of credentials. All data can be encrypted client-side using those keys, providing end-to-end security. On the network side, communication between validators and miners is secured (they likely use encrypted channels and handshakes to prevent tampering). The chain implements slashing of misbehaving nodes – for example, if a validator detects that a miner who was supposed to store a file is unreachable or has lost the file, that miner’s stake can be slashed as a penalty. There are also reputational mechanisms: validators can ban or blacklist miners that repeatedly fail or provide poor service, ensuring the storage remains reliable for users. By having multiple miners replicate the same data, Hippius provides redundancy: even if some nodes go offline, data is not lost. This distributed design naturally protects against censorship and server outages, as no single miner controls the availability of content.
In practical terms, the Hippius network has quickly grown to significant capacity. Within a couple of weeks of launch, it reached its initial limit of 256 registered miner seats (UIDs) and achieved nearly 900 TB of aggregate storage provided by the community’s miners. This demonstrates a high supply of storage ready to be utilized. All operations (storage deals, node performance, etc.) can be monitored via Bittensor’s block explorer and the Hippius dashboard, giving a clear view into the subnet’s functioning. Overall, the technical architecture of Hippius combines a blockchain (for consensus, accounting, and coordination) with off-chain storage tech (IPFS, S3 servers) and clever incentive alignment to create a decentralized storage cloud that is both useful and economically sustainable.
Hippius was developed and launched by a team known as The Nerve Lab, which is responsible for the subnet’s codebase and deployment. The project was initially codenamed “The Brain” during development – an apt nickname given its role as the memory/storage component of Bittensor’s “brain.” The Nerve Lab has open-sourced the core components of Hippius on GitHub for transparency and community involvement. Key repositories include:
The Nerve Lab appears to be a specialized development group within the Bittensor community focusing on infrastructure subnets. While individual team member names are not prominently listed on the public site, the project has been endorsed by Bittensor’s core community and was announced via official channels (e.g., by Bittensor contributors on Twitter/X and Discord). The lead developer or project manager (possibly the person behind the handle “Al” on Discord/Twitter) coordinated public updates about Hippius’s launch. We can infer the team has expertise in both blockchain engineering and distributed storage (given the integration of Substrate, IPFS, etc.).
Importantly, Hippius is a community-driven, open-source project. The code being GPL-3.0 licensed means that others can audit and contribute to it. Already, third-party analytics sites like Backprop Finance have integrated Hippius, and the Bittensor community (miners/validators) is running the network. This decentralized development and operation model aligns with Bittensor’s philosophy. Ongoing development (bug fixes, feature additions) is likely coordinated via the Hippius Discord and GitHub issues, where The Nerve Lab interacts with community developers. The 10% treasury from marketplace revenue provides funding for the team to continue improving the subnet, ensuring a long-term development cycle.
Hippius was developed and launched by a team known as The Nerve Lab, which is responsible for the subnet’s codebase and deployment. The project was initially codenamed “The Brain” during development – an apt nickname given its role as the memory/storage component of Bittensor’s “brain.” The Nerve Lab has open-sourced the core components of Hippius on GitHub for transparency and community involvement. Key repositories include:
The Nerve Lab appears to be a specialized development group within the Bittensor community focusing on infrastructure subnets. While individual team member names are not prominently listed on the public site, the project has been endorsed by Bittensor’s core community and was announced via official channels (e.g., by Bittensor contributors on Twitter/X and Discord). The lead developer or project manager (possibly the person behind the handle “Al” on Discord/Twitter) coordinated public updates about Hippius’s launch. We can infer the team has expertise in both blockchain engineering and distributed storage (given the integration of Substrate, IPFS, etc.).
Importantly, Hippius is a community-driven, open-source project. The code being GPL-3.0 licensed means that others can audit and contribute to it. Already, third-party analytics sites like Backprop Finance have integrated Hippius, and the Bittensor community (miners/validators) is running the network. This decentralized development and operation model aligns with Bittensor’s philosophy. Ongoing development (bug fixes, feature additions) is likely coordinated via the Hippius Discord and GitHub issues, where The Nerve Lab interacts with community developers. The 10% treasury from marketplace revenue provides funding for the team to continue improving the subnet, ensuring a long-term development cycle.
Hippius is in its early launch phase (Q1–Q2 2025) with a roadmap that was publicly shared as a series of phases. According to the official launch announcement, the rollout is staged as follows:
Integration with Other Subnets: Another future consideration is how Hippius might integrate with other Bittensor subnets (besides just via TAO). For example, an AI-focused subnet (like those serving chat completions or vision tasks) could directly use Hippius to store large machine learning models or datasets and retrieve them on-demand. We might see tooling or protocols developed to facilitate this cross-subnet usage. Since validators on Hippius already report performance to the main chain, eventually Bittensor’s scheduler could use Hippius as an external memory for other subnets’ operations. Such deeper integration would solidify Hippius’s role as infrastructure for all dApps in the ecosystem.
Hippius is in its early launch phase (Q1–Q2 2025) with a roadmap that was publicly shared as a series of phases. According to the official launch announcement, the rollout is staged as follows:
Integration with Other Subnets: Another future consideration is how Hippius might integrate with other Bittensor subnets (besides just via TAO). For example, an AI-focused subnet (like those serving chat completions or vision tasks) could directly use Hippius to store large machine learning models or datasets and retrieve them on-demand. We might see tooling or protocols developed to facilitate this cross-subnet usage. Since validators on Hippius already report performance to the main chain, eventually Bittensor’s scheduler could use Hippius as an external memory for other subnets’ operations. Such deeper integration would solidify Hippius’s role as infrastructure for all dApps in the ecosystem.
Keep ahead of the Bittensor exponential development curve…
Subnet Alpha is an informational platform for Bittensor Subnets.
This site is not affiliated with the Opentensor Foundation or TaoStats.
The content provided on this website is for informational purposes only. We make no guarantees regarding the accuracy or currency of the information at any given time.
Subnet Alpha is created and maintained by The Realistic Trader. If you have any suggestions or encounter any issues, please contact us at [email protected].
Copyright 2024