Mainchain
Mainchain is the glossary term for the primary Bittensor blockchain network. The official glossary describes it as the primary Bittensor network used for production purposes (Glossary: Mainchain, Bittensor Networks).
The term is network-context vocabulary. It should be read separately from localnet, testnet, Subtensor as the chain layer, and public access surfaces that connect to the chain.
Network Context
The Bittensor Networks reference lists mainnet alongside testnet and localnet. Mainchain belongs to the primary network side of that vocabulary, while testnet and localnet name separate contexts.
Relationship to Subtensor
Mainchain and Subtensor name related but distinct concepts. Mainchain names the primary network context, while Subtensor names Bittensor’s layer 1 blockchain and system of record for transactions and rankings (Glossary: Mainchain, Glossary: Subtensor).
Reading the two terms together keeps the network-context meaning of Mainchain distinct from the chain-layer meaning of Subtensor.
Relationship to Bittensor Networks
Bittensor Networks is the broader environment label, while Mainchain names the primary network context inside that picture (Bittensor Networks, Glossary: Mainchain).
This boundary keeps Mainchain from being used as a synonym for every Bittensor network environment.
Relationship to Public Subtensor
Public Subtensor is related to Mainchain, but it is not the same term. The glossary describes Public Subtensor as publicly reachable access to the Subtensor chain layer (Glossary: Public Subtensor, Glossary: Mainchain).
Mainchain names the primary network context. Public Subtensor names a public access surface for the chain layer.
Relationship to Local Blockchain
Mainchain and local blockchain name different sides of Bittensor network context. The glossary describes local blockchain as a private chain used for development and testing (Glossary: Local Blockchain, Glossary: Mainchain).
That makes local blockchain useful as isolated development context, while Mainchain names the primary network context. The two should not be used as interchangeable evidence.
Subnet Development Endpoint Context
The Bittensor introduction describes subnet development as moving from localnet to testnet and then mainnet (Introduction to Bittensor: Subnet development).
Mainchain belongs to the final network context in that sequence. That does not prove a subnet’s mechanism quality or outcome; it only places the activity in the primary Bittensor network rather than a local or test network.
That distinction also narrows what a Mainchain article should imply. Calling something mainchain context does not prove that a subnet’s mechanism is well designed. It only places the activity in the primary network rather than in local or test context.
Reader Boundary
Mainchain does not name endpoint status, a connection guide, local development behavior, a subnet quality claim, or every detail of the Subtensor layer (Glossary: Mainchain, Bittensor Networks).
Keeping that boundary preserves the term’s narrower meaning. Mainchain identifies the primary Bittensor network context, while Subtensor, Public Subtensor, local blockchain, testnet, and subnet-development references describe neighboring parts of the system.