A source of truth for network-level governance, written by its stakeholders.
✦ ✦ ✦
AWAITING ON-CHAIN CREATIONSIGNATURES —SUPPORT —
Preamble
The Solana Constitution outlines the principles and operational guidelines for network-level
Solana governance. It was written collaboratively by a broad range of network stakeholders and acts
as a network source of truth for governance that will facilitate coordination of network upgrades
amongst stakers, validators, and developers. This Constitution decentralizes power, enforces staker
sovereignty, and empowers validators to be active stewards of the network.
Article I
Core Principles
I.1
Stake Sovereignty. Every staked SOL token carries proportional voting power.
I.2
Validator Stewardship. Validators translate stakeholder will into action, run the network securely and transparently, and are collectively accountable to stakers through governance participation and open performance data.
I.3
Network Level Control. Developers write proposals, validators endorse them, and all stakers have the ability to vote on them. Validators and stakers hold developers accountable and steward the network to optimal outcomes, thus mitigating the threat of a network fork.
I.4
Transparency & Auditability. Every vote and vote override is recorded on-chain and publicly visible.
I.5
Optimistic, Agile, and Consent-Driven. The governance system is tuned to maximize holder consent, while balancing rapid development and iterative improvements, and limiting spam proposals and excessive voting.
I.6
Decentralization, Positive-Sum Economics and Neutrality. Permissionless validation and governance are foundational to the network. Censorship-resistance, positive-sum economics, and neutrality are paramount.
Article II
Proposal Submission & Support
II.1
Solana Governance follows two tracks: a Solana Improvement Document (SIMD) — a technical specification document following the implementation pathway of SIMD-001, not voted upon — and a Solana Governance Proposal (SGP) — a more expansive proposal establishing consensus for a development or strategic network trajectory. All SGPs are voted on at the network level.
II.2
Systemic Changes Should Trigger SGPs. To eliminate overvoting and to maintain core developer agency and agility, SGPs should be limited to systemic network changes only, meaning a fundamental change to network economics or system architecture.
II.3
Draft SGP to SGP Conversion. A Draft SGP is created and iterated in the SGP repository; authors signal Final Draft status; a validator holding at least 100,000 SOL of active stake creates the on-chain proposal. Once the draft exceeds the Proposal Sponsor Threshold, it becomes an official SGP and the Review Period is triggered.
II.4
SIMD to SGP Elevation. All SIMDs pass optimistically, ensuring rapid development paths, unless sufficient stake signals that a SIMD is systemic or contentious — in which case elevation to a network-wide vote is triggered by the Proposal Sponsor Threshold. If quorum is not met, the SIMD continues to pass optimistically.
II.5
Drafting and Numbering. SIMDs and SGPs are numbered and sequenced by the maintainers of the SIMD repository, who inherit the practices of SIMD-001 and publish reasoned justifications for exclusions.
II.6
Format. All SGPs follow the structure of the Solana Governance Proposal Template (Appendix I).
II.7
Official Discussion Channels. The canonical sites of deliberation are the proposals' GitHub repositories; community discussion elsewhere is welcomed as advisory input.
Article III
Roles & Responsibilities
III.1
Staker. Each stake account may cast a vote For, Against, or Abstain on every SGP. By default a staker's vote is delegated to their validator; stakers retain vote sovereignty and may vote before, after, or in the absence of validator turnout, overriding their validator.
III.2
Validator. A group of validators with at least 15% of staked SOL may elevate an SGP to a network-wide vote. Validators cast their full or split stake in the final vote.
III.3
Maintainers. The procedural and operational stewards of the framework: editorial control of proposals, maintenance of the governance process, and publication of the formal record — with justifications for classification decisions stated for the network record.
Article IV
Validator Voting Process
IV.1
Review Period. A review period of 7 epochs follows on-chain proposal creation. The proposal's GitHub commit SHA is immutable from the moment of creation; the review period exists to study the frozen text, not to amend it.
IV.2
NCN Snapshot Period. A snapshot period of 1 epoch follows the Review Period, during which the Node Consensus Network establishes the canonical stake snapshot fixing voting weights for the duration of the vote.
IV.3
Vote Quorum. Each vote requires a quorum of one-third of network stake to be considered a valid signal. Participating stake is the sum of For, Against, and Abstain allocations.
IV.4
Supermajority Threshold. A supermajority of two-thirds yes votes among the participating quorum is required to pass. Abstain counts as participation but not as a For vote.
IV.5
Voting Period. A voting period of 3 epochs occurs for each SGP.
IV.6
Voting Options. Validators may Block Vote — 100% of stake on one option — or Split Vote, allocating stake across options in basis points summing to 10,000.
IV.7
Quorum Failure. Quorum failure signals network indifference rather than proposal failure. This governance process is a veto process: an SGP passing indicates the network will not veto a change. Inconclusive proposals leave development free to continue at its own risk.
IV.8
Lifecycle States. Draft → Final Draft → Support → Voting → Accepted | Rejected → Implemented → Activated; with the side states Withdrawn, Expired, and Inconclusive.
Article V
Amendment Process
V.1
Network Sovereignty. The Solana Constitution is a living document, and the network, and the network alone, has full sovereignty over its articles and their application.
V.2
SGP Directed. Changes to articles and Key Governance Parameters are governed by the SGP process articulated in this Constitution.
V.3
The Amendment Process. Minor amendments — language and articulation — may be batched as a single SGP. Major amendments — Key Governance Parameters, or addition or deletion of entire articles — must be standalone SGPs.
V.4
Justification. All amendment SGPs must arrive with clear justification and empirical evidence for the change.
Article VI
Key Governance Parameters
Parameter
Default
Proposal Sponsor Threshold
15% of active stake
Proposal Submission Floor
100,000 SOL active stake
Quorum
⅓ of network stake
Supermajority Threshold
⅔ of participating stake
Review Period
7 epochs
NCN Snapshot Period
1 epoch
Voting Period
3 epochs
✦ ✦ ✦
In Witness Whereof
We, the validators of the Solana network, by our signatures affixed on-chain,
do sponsor this Constitution to a vote of all staked SOL — and in voting, ratify it —
that the network may govern itself by no authority other than its own stake.
The first signatures belong to the validators who sponsor the proposal on-chain.
Every signature below is a live on-chain act — a support_proposal or
cast_vote transaction — recorded here in the order it lands, permanently
verifiable on the ledger.
The ledger awaits the proposal's creation on-chain.
✦ ✦ ✦
The Vote
Sponsorship carried the proposals to a vote of all staked SOL. Here every validator's
ballot is recorded — for, against, or abstaining — alongside the stakers who exercised their right
to override their validator and vote their own stake directly.
reading the ledger…
The Roll of Validators
How each validator voted across the three proposals — by active stake.
Staker Participation
—stakers voted by override
—SOL reclaimed from validators
A staker may reclaim their share of the vote from their validator and cast it directly.
Those who voted against their validator's own choice are marked in red.
To Sign — Validators
# Sponsor the Constitution to a network vote (sign with your validator identity keypair)
svmgov -k /path/to/validator-identity.json \
--rpc-url https://api.mainnet-beta.solana.com \
support-proposal --proposal-id 4aFA8K65zYZjmx16qaXhMLW9QY7URRvwyk4KQo2zLz8k
Your validator's signature is appended to this page automatically, in the order it lands on-chain.
Supporting is sponsorship — it says "this deserves a vote," not "yes."