Public Subtensor
Public Subtensor refers to publicly reachable access to the Bittensor chain layer. It is an access context, not a separate blockchain.
The Glossary: Public Subtensor entry defines the term as publicly reachable access to Subtensor. The Subtensor Nodes documentation gives operational context for connecting to the Subtensor chain layer.
What Public Subtensor Means
The public-access part of the term matters. Public Subtensor describes access to Subtensor through a publicly reachable network context, while Subtensor itself names the Bittensor blockchain layer. The Glossary: Subtensor describes that chain layer as Bittensor’s system of record.
This distinction keeps the concept narrow. Public Subtensor does not rename the chain, create a new runtime, or describe every node-deployment detail. It identifies the public-access context for reaching the Subtensor chain layer.
Network Context
Public Subtensor should be read with network context attached. The Bittensor Networks reference separates mainnet, testnet, and localnet as different environments. Public access can expose shared network state, but the selected environment determines what the observed data can support.
A public-access example from one environment should not be treated as a universal Bittensor fact. The relevant network, endpoint context, queried state, and block context determine how strong a claim can be.
Public Access Versus Local Development
Public Subtensor is different from private local development context. The Glossary: Local Blockchain describes a local blockchain as private, isolated, and used for development and testing. That local context can demonstrate chain behavior, but it is not the same as publicly reachable Subtensor access.
The distinction is useful when reading examples. A local run can show how a mechanism behaves in an isolated environment, while Public Subtensor describes access to shared chain context. Those sources should not be collapsed into one evidence category.
Access Versus Mechanism
Public Subtensor names an access context, not a protocol mechanism. Through public access, an observer can inspect chain state exposed by Subtensor, but the access path is not itself the mechanism that creates that state.
For example, the Coinbase Implementation documentation describes a per-block protocol process inside Subtensor. Public Subtensor may expose state affected by that process, but it does not produce emissions, trigger consensus, or replace the mechanism documentation.
Evidence Boundary
The Public Subtensor glossary entry supports claims about public chain access. It does not provide endpoint recommendations, connection procedures, node-management guidance, or private account diagnosis.
That boundary keeps the article conceptual. The Public Subtensor glossary entry supports public-access claims, while mechanism claims should still use the mechanism’s own documentation and identify the relevant network context.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Public Subtensor, that sequence determines which network’s shared chain access is being described.
In localnet, chain access is isolated rather than public. Localnet observations reflect private local chain activity and do not represent publicly reachable Bittensor chain state.
On testnet, publicly reachable access to the testnet chain layer is available. Testnet public chain access exposes testnet state, which is separate from mainnet chain state.
On mainnet, Public Subtensor is the live, publicly reachable access to the production Bittensor chain layer. The Subtensor Nodes documentation describes the connection context for reaching the production network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. Public chain access on one network should not be read as representative of chain state on another network.