Sudo
Sudo is Bittensor governance vocabulary for privileged administrative authority. In Bittensor’s governance model, the term points to an older single-key authority pattern that governance replaces with proposal review (Glossary: Sudo, Governance Overview).
The term is a contrast point for the governance system. It helps explain why privileged changes are described through proposals, Senate review, and governance approval rather than direct unilateral control.
Governance Context
Bittensor governance moves privileged network changes away from direct single-authority control. The Triumvirate creates proposals, and the Senate reviews them before privileged changes can proceed (Governance Overview, Glossary: Triumvirate).
That makes Sudo a contrast term. It helps explain what the governance process replaced, while Triumvirate, Senate, and proposal vocabulary describe the review path used by the governance model (Senate, Glossary: Proposal).
Security Transition
The security transition is central to the term. Sudo points to privileged administrative authority, while Bittensor governance distributes privileged-change review across proposal origin and Senate approval (Governance Overview: security, Glossary: Sudo).
This does not make Sudo a separate governance body. It is the legacy authority concept that helps frame why proposal review and Senate approval matter.
Proposal Review Context
The governance replacement for Sudo is not just a new key name. A proposal identifies the requested privileged action, the Senate supplies the approval gate, and the governance process determines whether the approved action is applied (Governance Overview, Senate).
That path separates authority into stages. Sudo vocabulary points to the older single-authority model, while proposal-review vocabulary points to a staged path with named governance bodies. The term therefore should not be used as shorthand for any current proposal, Senate vote, or governance body (Governance Overview).
The Senate context also separates visibility from authority. Proposals before the Senate can be viewed publicly, but approval and disapproval votes belong to senators (Senate). That distinction keeps public review separate from the authority to approve privileged changes.
Bicameral Boundary
Sudo is adjacent to bicameral governance but not the same term. Bicameral legislature names the two-body structure that separates proposal creation and proposal approval, while Sudo names the legacy privileged-authority concept that the governance design replaces (Glossary: Bicameral Legislature, Glossary: Sudo).
This keeps the replacement story precise. Bicameral governance explains the structure; Sudo explains the authority model being moved away from.
Network Scope
Bittensor documentation separates localnet, testnet, and mainnet environments (Bittensor Networks, Introduction to Bittensor). Sudo and governance examples need the environment attached because local testing, testnet examples, and mainnet governance activity have different scope.
A local example can illustrate mechanics. Testnet behavior can show shared non-production governance flow. Mainnet governance is the production context for proposal review and privileged changes.
Development Stage Context
The Introduction to Bittensor describes subnet development as moving from localnet to testnet and then mainnet. For Sudo, that sequence changes how an example should be read, because the surrounding network state differs at each stage.
In localnet, sudo can be exercised in an isolated development environment, where the surrounding chain state reflects local configuration rather than production history.
On testnet, sudo can be observed in a shared, non-production network whose state is kept separate from mainnet.
On mainnet, sudo applies on the live, production Bittensor network, where the surrounding state is real and persistent.
The Bittensor Networks reference separates mainnet, testnet, and localnet. A sudo example from one environment should not be read as representing another environment.
Reader Boundary
Sudo should be read as historical authority vocabulary inside Bittensor governance. It does not identify an administrative key holder, expose key material, or provide instructions for privileged actions (Glossary: Sudo).
When the focus is proposal creation, Triumvirate is more precise. When the focus is voting and approval, Senate is more precise. When the focus is the item under review, proposal is more precise.
The stable reference point is the replacement of single-authority control with governance review.
Proposals Need Senate Majority and Triumvirate Close
The Governance Overview states that proposals execute only after two conditions: the proposal obtains a majority of Senate approvals, described there as (50% + 1) of the Senate, and a Triumvirate member closes the proposal. Both steps are required before privileged calldata runs.
That staged path replaces the older single-key pattern Sudo names. Privileged changes no longer rely on one administrative approval alone; they pass through proposal creation, Senate review, and close (Glossary: Proposal).
Senate Seats Follow Top Delegate Hotkeys
Official governance material describes the Senate as formed from the top delegate hotkeys on the network. Senators therefore enter governance through delegated stake ranking rather than through the Triumvirate employment path used for proposal origin.
That split keeps bicameral vocabulary precise. Triumvirate members originate proposals; Senate members supply the approval gate based on delegate hotkey standing (Senate).
Compromise Requires Triumvirate Access and Senate Control
The governance security section contrasts the old sudo private-key model with the replacement
design. Under governance, a malicious actor would need to compromise a Triumvirate member and
control a Senate majority to approve a proposal, rather than relying on one privileged key alone.
Sudo vocabulary therefore marks the authority model being replaced. Governance review distributes privileged-change approval across proposal origin and elected Senate consent rather than direct unilateral control (Governance Overview: security).