Protocol
How Bittensor actually works underneath the registry — stake weighting, UID registration and permits, weight setting, proxies, and root delegation.
Last updated
The chain mechanics the rest of these docs assume. Each page explains one part of Bittensor's protocol as it behaves today, with the on-chain fields and thresholds named so a claim here can be checked against the API.
- Stake weight — the two-component formula, and why root TAO counts differently from subnet Alpha.
- Registration and permits — what a UID costs, and why holding a validator permit is a different thing entirely.
- Weight setting and rewards — how validators score miners and how that becomes emission.
- Proxies — delegating scoped, revocable authority to another key without a multisig ceremony per action.
- Root delegation — how
set_childrenbacks child hotkeys across many subnets at once.
Audit an account's history
Three MCP tool calls to reconstruct what one SS58 address has actually done on-chain — activity summary, native transfers, and stake re-delegation — with a real, executed transcript.
Understanding stake-weight
How Bittensor actually weighs stake per subnet — the two-component stake_weight formula, why root TAO counts differently than subnet Alpha, and what that means practically for anyone staking or validating.