SwssChain governance is on chain. Protocol changes are proposed, voted on by the validator set, subject to a Foundation veto window and a timelock, and then executed by the contract, not by an administrator with a key.
What Governance Decides
| Proposal type | Tier | Decides |
| PROTOCOL_UPGRADE | 1 | A change to the protocol itself |
| VALIDATOR_ADMISSION | 2 | Admission of an operator to the validator set |
| VALIDATOR_ROTATION | 2 | Rotation of a validator's keys to new ones |
| JURISDICTION_SCOPE | 2 | The jurisdictions settlement is scoped to |
| DEED_CATEGORY | 2 | A new deed class in the registry |
| FEE_ADJUSTMENT | 2 | Settlement fee parameters |
| ADVISORY | 3 | A motion that records a position without binding execution |
The Three Tiers
- Tier 1: protocol upgrades. Foundation only. A change to the settlement layer is not a matter on which an operator who joined last month gets an equal vote.
- Tier 2: the operating set. The Foundation and validators granted Tier 2 rights. Admission, rotation, jurisdiction, deed categories and fees.
- Tier 3: advisory. All validators holding granted rights. Records a position; executes nothing.
Voting rights are granted per tier, per validator address. Holding stake does not confer them, and neither does running a node: see Developer and Validator Access for how an operator is admitted in the first place.
Why a Veto Window Exists
Between a proposal passing and executing, the Foundation has a window in which it can veto. On a general-purpose chain that would be a centralisation complaint, and on a settlement network it is a legal requirement: the entities relying on a Finality Certificate need someone accountable if a passed proposal would put the network outside the frameworks it settles under. The window is bounded, see Governance Parameters, and every veto is an on-chain event with the vetoing address recorded.
The veto can stop a proposal. It cannot pass one, and it cannot execute anything.
Next Steps