Proposal Hash
A proposal hash is the compact identifier used to refer to a proposal in Bittensor governance. It gives Senate review and voting a stable reference for the proposal under consideration (Glossary: Proposal Hash, Governance Overview).
The hash is useful because governance discussions often need to point at the same item across review, voting, and later references. The proposal carries the requested action; the hash keeps references to that proposal compact.
Proposal Identifier
In Bittensor governance, a proposal is the item put forward for review, while the hash is the identifier used to refer to that item (Glossary: Proposal, Glossary: Proposal Hash).
The distinction keeps the article narrow. A proposal hash points to the governance item; it does not contain the full proposal text, vote reasoning, or later outcome (Governance Overview).
Senate Review
Bittensor governance separates proposal creation from Senate approval. Proposal review and voting sit inside Senate review, so proposal hashes belong naturally beside Senate review terms (Governance Overview, Senate).
During review, the same proposal can appear in proposal descriptions, Senate discussions, and later governance references. The hash keeps those references aligned with the same item without restating the whole proposal each time.
Senate review still supplies the governance action. A proposal hash identifies the item under review, while the Senate source explains the approval process and vote result (Senate).
Voting Records
Senate voting centers on the proposal being reviewed. A proposal hash identifies the proposal being referenced, while the surrounding Senate record explains the vote, review state, and later outcome (Senate, Governance Overview).
That separation matters in governance summaries. The hash can tell readers which proposal is in view, but the source using the hash must supply the decision, review state, or applied-change details.
When a hash appears with little surrounding explanation, the narrow reading is usually best: it identifies which proposal is in view, and the neighboring governance material explains why that proposal matters.
Governance Relationships
Proposal hash belongs near proposal, Senate, senator, and Triumvirate language. Proposal names the governance item, Triumvirate names the proposal-origin body, Senate names the review body, and senators are the delegates who vote during Senate review (Governance Overview, Senate).
The hash is not a governance actor. It is the reference attached to the item moving through those relationships (Glossary: Proposal Hash).
Reader Boundary
Proposal hash is proposal-identifier terminology. It is the compact governance reference used during proposal review and voting, while the proposal and governance record carry the requested change, review state, and outcome (Glossary: Proposal Hash, Glossary: Proposal, Senate).
Senators Look Up the Hash Before Casting a Vote
The Senate voting process has senators look up a proposal’s hash from the proposals overview, then supply that hash to cast an approval or disapproval. The vote is counted once it is included in the next block.
That sequence makes the hash an active step in voting, not only a passive label. A senator cannot cast a vote without first identifying the correct proposal hash to vote on (Senate).
Triumvirate Originates, Senate Reviews
Because Bittensor governance separates proposal creation from approval, the Triumvirate originates a proposal and the Senate then reviews and votes on it. The proposal hash is the single reference that points to that same item across both stages, so origination-side and review-side governance records can be tied to one proposal (Governance Overview, Glossary: Triumvirate).
Development Stage Context
Bittensor separates mainnet, testnet, and localnet environments. Governance examples from one environment belong to that environment because proposal records and vote outcomes can differ (Bittensor Networks, Introduction to Bittensor: Subnet development).