Local Blockchain
A local blockchain is a private Bittensor chain used for development and testing. The term separates isolated local experiments from public Bittensor network activity (Glossary: Local Blockchain, Bittensor Networks).
The concept is environment vocabulary. It does not name a subnet role, a public network, or a separate tokenomic mechanism.
Private Chain Context
Local blockchain context means the chain is private to the development environment. Work performed there can help test Bittensor components and subnet behavior without making claims about public network state (Glossary: Local Blockchain, Bittensor Networks).
That distinction is the point of the term. A local result can be useful evidence for a local test, but it is not the same kind of evidence as behavior observed in shared network contexts.
The environment label should therefore stay attached whenever a local blockchain example is used.
Localnet is for development and testing in a fully user-controlled environment (Bittensor Networks). That purpose matches the local blockchain glossary entry: both frame local chain activity as isolated development context rather than public network activity.
This also changes how local results should be read. A local blockchain can show whether a component or subnet mechanism behaves as expected inside the private test environment, but it does not prove the same result on testnet or mainnet (Glossary: Local Blockchain, Bittensor Networks).
Localnet Boundary
Bittensor network vocabulary separates mainnet, testnet, and localnet. Localnet is the local environment label, while local blockchain names the private chain used in that environment (Bittensor Networks, Glossary: Local Blockchain).
This keeps the environment and the chain concept aligned but not identical. Localnet names one network context; local blockchain names the isolated chain that supports that context.
Public Access Boundary
Local blockchain and Public Subtensor point in opposite directions. Public Subtensor is public access to the Subtensor chain layer, while local blockchain is private local chain context (Glossary: Public Subtensor, Glossary: Local Blockchain).
This contrast helps avoid mixing local test results with public chain access. Local blockchain context should not be used as evidence about Public Subtensor availability.
Block Timing Context
Fast blocks and non-fast blocks are local-chain timing terms. Fast blocks make local block production faster for testing, while non-fast blocks keep the ordinary twelve-second local interval (Glossary: Fast blocks, Glossary: Non-fast blocks).
Both terms belong under local blockchain context. They describe timing behavior inside an isolated local chain rather than changing the meaning of mainnet or testnet.
Localnet block cadence can be either one block every 0.25 seconds in fast-block mode or one block every 12 seconds in non-fast-block mode (Bittensor Networks). That makes block mode part of the evidence label for local examples.
Mainnet and testnet use one block every 12 seconds (Bittensor Networks). A local fast-block result can therefore arrive much faster than a public-network example without changing what the underlying mechanism means.
For readers, the timing distinction is practical. Fast blocks shorten feedback loops during local testing; non-fast blocks keep the local chain closer to the ordinary 12-second cadence used outside fast-block local mode.
Mainchain and Subtensor Boundary
Mainchain and Subtensor are related network and chain-layer concepts, but they are not synonyms for local blockchain. Mainchain names the primary Bittensor network, while Subtensor names Bittensor’s chain layer and system of record (Glossary: Mainchain, Glossary: Subtensor).
Local blockchain instead names an isolated private chain for development and testing. It can model or exercise Bittensor behavior, but it does not replace Mainchain or public Subtensor context.
Development Path Context
The Bittensor introduction describes subnet development as moving from localnet to testnet and then mainnet (Introduction to Bittensor: Subnet development).
Local blockchain belongs to the isolated local part of that path. Testnet provides shared non-production context, and mainnet provides the primary network context, so local observations should stay attached to their environment.
That sequence gives local blockchain a clear scope. It is useful before shared testing because it lets development work happen without relying on testnet state or mainnet value (Introduction to Bittensor: Subnet development, Bittensor Networks).
Once an example moves to testnet or mainnet, it no longer has the same evidence status as a local blockchain example. The network label, block cadence, and value context should move with the claim.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For local blockchain vocabulary, that sequence is central: a local blockchain belongs to isolated development rather than shared testnet or production mainnet state.
In localnet, a local blockchain is the intended environment for subnet and wallet experiments. Local chain outcomes reflect local configuration and do not represent production Bittensor behavior.
On testnet, developers move from private local runs to a shared non-production network. Testnet state is separate from both local-only chains and mainnet production history (Bittensor Networks).
On mainnet, Bittensor production activity runs on the live production network rather than on a developer’s local blockchain instance.
The Bittensor Networks reference separates mainnet, testnet, and localnet. Evidence from a local blockchain should not be read as proof of behavior on testnet or mainnet.
Relationship to Yuma Consensus
Local Blockchain and Yuma Consensus describe related parts of Bittensor’s incentive system. Yuma Consensus is the on-chain process that aggregates validator weight signals within a subnet into miner incentives and validator dividends, applying consensus clipping, bonding, and emission calculation (Yuma Consensus).
For readers, local blockchain names a specific part of that incentive picture, while Yuma Consensus names the consensus process that turns validator weights into the resulting incentives and dividends.
Reader Boundary
Local blockchain does not name a tutorial, node-operation guide, public network status report, or source for public chain data (Glossary: Local Blockchain, Bittensor Networks).
Local blockchain identifies a private, isolated development chain, while localnet, testnet, mainnet, Public Subtensor, Mainchain, and Subtensor describe neighboring parts of the system.
Fast Blocks Change Local Cadence Only
Fast blocks and non-fast blocks adjust local block timing without turning a local chain into mainnet or testnet evidence (Glossary: Fast blocks, Glossary: Non-fast blocks).