Bittensor Governance
Bittensor Governance
Bittensor governance is the network process for reviewing and executing privileged changes. The
current model moves administrative authority away from a single sudo key and toward a bicameral
structure: the Triumvirate creates proposals, and the Senate approves or rejects them.
References: Governance Overview, Senate
Why governance matters
Privileged network changes can affect subnet creation, runtime parameters, chain upgrades, and other configuration that shapes how Bittensor operates. Governance raises the review threshold for those changes by separating proposal creation from Senate approval.
Reference: Governance Overview
Proposal flow
A proposal wraps the call data for a privileged action. It does not execute immediately when it is created. The official governance docs describe two required steps before execution:
- A majority of the Senate must approve the proposal.
- A Triumvirate member must close the proposal after approval.
When a proposal is closed successfully, the proposal call data is executed in the same block as the close action. This gives the Senate a review gate while leaving final execution with the Triumvirate-controlled proposal process.
Reference: Governance Overview
The Senate
The Senate is the governance body that reviews Triumvirate proposals. The official Senate docs describe membership as stake-based and explain how senators view proposals, vote, and participate in the approval process.
For readers, the practical point is that governance participation is not just a social process. It is tied to Bittensor account roles, wallet permissions, and proposal records. The BTCLI permissions guide documents the CLI permission model for governance-related actions.
References: Senate, BTCLI Permissions Guide
Viewing and voting
Proposal visibility is public. Anyone can inspect proposals currently before the Senate without special permissions. Voting is restricted to senators, and senators use the proposal hash to cast an approval or disapproval vote.
Reference: Senate
Practical implications
- For stakers: Delegation can affect governance because Senate participation is stake-based.
- For senators: Proposal review requires understanding the call data and operational impact of the proposed change.
- For subnet creators and operators: Governance can affect network parameters, subnet configuration, and the rules that determine who can participate.
- For readers: Governance claims should be checked against official docs, proposal details, and implementation behavior rather than social claims alone.
References: Governance Overview, Senate