Subnet 115: HashiChain
HashiChain is Bittensor Subnet 115. Its on-chain identity describes HashiChain as the first public blockchain designed for AI agents and lists hashi115/hashichain as the subnet’s GitHub repository. The public repository currently provides a high-level README, license, and visual asset rather than a full miner or validator implementation.
What HashiChain Provides
The HashiChain README presents the subnet as a sovereign Layer 1 infrastructure for what it calls the agent economy. Its core idea is that autonomous agents often need to coordinate around unstructured or probabilistic intents, rather than only executing deterministic financial transfers. HashiChain frames this as a shift from a ledger of assets toward a ledger of intents.
The README introduces a “Probabilistic State Machine” as the design primitive for this intent ledger. In the published description, agent interactions are evaluated by semantic compatibility: nodes estimate whether private agent intents can successfully match, coordinate, or settle. This is a conceptual protocol description in the current public source, so readers should treat it as the subnet’s stated design direction rather than as a complete public implementation specification.
Miner and Consensus Roles
HashiChain describes miners as solver nodes. In the README, solver nodes run AI models inside trusted execution environments and simulate possible interactions in secure sandboxes. The stated goal is to verify whether two or more agent intents are compatible enough to finalize an update on the intent ledger.
The same source says HashiChain uses Bittensor as its consensus engine and computational substrate. It specifically names Yuma Consensus as the mechanism for reaching network-wide agreement on probabilistic agent interactions, extending Bittensor’s role beyond reward distribution into the subnet’s proposed validation process.
Intent-Ledger Context
The HashiChain README frames the subnet around a shift from an asset ledger to an intent ledger. In that framing, autonomous agents do not only need to transfer fixed amounts between accounts; they need to discover whether private, high-dimensional goals can match, coordinate, or settle. HashiChain describes that problem as probabilistic rather than purely deterministic.
The README names the proposed primitive a Probabilistic State Machine. It also names Proof of Entanglement as the verification idea for semantic compatibility between private agent intents. At Taopedia level, those terms are best read as the project’s stated protocol vocabulary for matching agent intentions, not as a general Bittensor consensus term shared by every subnet.
This context helps explain why HashiChain describes miners as solver nodes. Their role is not presented as ordinary transaction validation or content generation. The public source says they simulate possible interactions in secure sandboxes and estimate whether agent intents are compatible enough to update the intent ledger.
HashiChain also uses the “Hashi” metaphor to explain the intended coordination layer. The README describes Hashi as a bridge between isolated agent silos and as “chopsticks” for paired coordination, meaning agents need a shared settlement fabric to capture value together. In article terms, this places the subnet in the agent-coordination lane rather than in a simple payment, chatbot, or dataset-generation lane.
That framing connects the miner and consensus descriptions. Solver nodes search for compatible agent interactions, secure sandboxes provide the simulation setting, Proof of Entanglement names the compatibility check, and Yuma Consensus is named as the agreement layer. The subnet’s public materials therefore describe a market for evaluating agent-intent compatibility rather than a market for producing one static artifact.
References: HashiChain repository, Yuma Consensus, Subnet 115 on TaoStats
On-Chain Identity
Live SN115 data is available on TaoStats. The live Finney identity for netuid 115 registers the subnet name as HashiChain, with the description “The First Public Blockchain Designed for AI Agents.” The GitHub repository is hashi115/hashichain. The subnet URL and Discord fields are currently blank in the registered identity.
Relationship to Yuma Consensus
Subnet 115 uses Yuma Consensus to convert validator weight vectors into the emission shares distributed to miners and validators within the subnet each tempo. The Yuma Consensus documentation describes how validator weight submissions are aggregated into consensus weights for each miner registered on the subnet.
HashiChain’s public README names Yuma Consensus as the agreement layer for the subnet’s probabilistic agent-coordination protocol, where solver nodes simulate agent-intent compatibility and validators translate those results into weight vectors. The Emission documentation describes how those consensus weights determine each participant’s share of the subnet’s accumulated emission each tempo.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For HashiChain (SN115), that sequence changes how readers should interpret AI agent coordination examples and the subnet’s probabilistic evaluation outcomes.
In localnet, HashiChain-compatible miners and validators can be developed and tested in an isolated environment. Localnet agent interaction results and emission outcomes do not represent production subnet performance.
On testnet, HashiChain-compatible agent coordination workflows can be exercised in a shared, non-production network. Testnet evaluation results and validator weights are separate from mainnet subnet state.
On mainnet, HashiChain (SN115) is the live production subnet where miners and validators operate the agent-coordination protocol to determine real Bittensor emissions. The HashiChain repository is the registered project repository for SN115 on the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. An agent coordination result or emission outcome from one environment should not be read as representing production subnet performance in another environment.
Netuid 115 Identifies the Subnet On-Chain
Bittensor assigns every subnet a unique numeric identifier called a netuid, and Subnet 115 is the subnet registered at netuid 115 (Glossary: Netuid). The Understanding Subnets reference explains that each subnet runs its own incentive mechanism while sharing the same underlying Subtensor chain, so the netuid is the stable handle that distinguishes HashiChain from every other subnet.
For a reader, this means “Subnet 115” and “netuid 115” refer to the same on-chain slot. A claim about HashiChain should be tied to that netuid rather than to the registered name alone, because the name field can be changed on-chain while the netuid stays fixed.
Miner and Validator Roles
Subnet 115 operates under the standard Bittensor two-role structure. Miners supply the subnet’s capability and validators evaluate those contributions and set weights. Reward distribution follows Yuma Consensus.
Reader Boundary
Subnet 115 HashiChain should not be read as generic Bittensor subnet documentation, financial, trading, or investment advice, or a substitute for the subnet’s own primary sources. It names the on-chain subnet registered at netuid 115 under the identity “HashiChain” (Understanding Subnets, Glossary: Netuid).