Taopedia
Taopedia is a lightweight, wiki-style site that organizes Bittensor knowledge into interlinked
articles. The public article source lives in the taopedia-articles repository and is published at
taopedia.org.
Article Source Model
Each article is stored as MDX under content/pages/<slug>/index.mdx. The Taopedia website syncs
Bittensor-scoped articles from that repository during the site build. Contributor pull requests
target the test branch; maintainers promote test to main after review.
That workflow makes Taopedia a community-maintained knowledge base rather than a live protocol console. Article changes travel through the same review path as other repository contributions.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Taopedia readers, that sequence matters when article examples cite behavior observed on different Bittensor network environments.
In localnet, Taopedia examples drawn from local development runs describe isolated chain behavior. Those examples help explain concepts but do not represent production network outcomes.
On testnet, examples can reference shared non-production Bittensor state. Testnet observations are useful for integration reading while staying separate from mainnet evidence (Bittensor Networks).
On mainnet, Taopedia articles that discuss live chain behavior should be read against production network context on the connected Bittensor network.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A Taopedia example tied to one environment should not be read as proof of behavior in another environment.
Docs Stay the Mechanism Reference
Bittensor mechanism detail still belongs in Learn Bittensor documentation. Taopedia articles explain terms, boundaries, and relationships; docs explain procedures, APIs, and live protocol behavior (Understanding Subnets, Bittensor Networks).
That split keeps the wiki useful for orientation without replacing subnet, staking, wallet, or emission references when a reader needs executable detail.
Site App and Article Repo Stay Separate
The Taopedia website application handles routing, styling, search, and deployment. Article content changes belong in the articles repository; UI and site-behavior changes belong in the website repository.
For readers, that separation means content corrections and new articles are wiki contributions, while layout or search changes are site-application work.
Distinction from Yuma Consensus
Taopedia is a wiki-style knowledge base that publishes Bittensor articles from the taopedia-articles repository. It names documentation and editorial vocabulary, not the on-chain step that turns validator weight submissions into emission shares (Taopedia).
Yuma Consensus is the on-chain process that converts submitted validator weights into emission shares after evaluation completes on Bittensor subnets. Taopedia articles explain protocol concepts; Yuma Consensus is the live settlement mechanism those articles may describe (Yuma Consensus, Emission).
Readers should keep knowledge-base vocabulary separate from the settlement step. Taopedia answers where explanatory articles are published; Yuma Consensus answers how validator weights become emission shares in a subnet (Yuma Consensus).
- Taopedia — community-maintained Bittensor knowledge base site.
- Yuma Consensus — on-chain weight aggregation that settles emissions.
Reader Boundary
Taopedia should not be read as Bittensor protocol documentation, a live network dashboard, or an operator command reference by itself. It is a curated wiki that links concepts together and points readers toward focused articles and external sources (Introduction to Bittensor).
When a claim depends on current chain behavior, parameter values, or tooling output, the next step is the relevant documentation, glossary entry, or network-specific source rather than treating a Taopedia article as the final authority.