Governance
Governance: Overview
Pre-launch
Section
Governance
Documentation category
Type
Guide
Technical reference
Summary
What on-chain governance decides on SwssChain, the three proposal tiers, and why a settlement network keeps a Foundation veto.
SWSS Foundation Notice

This documentation is restricted to authorised members of the SWSS Developer Community. Access is granted exclusively through SWSS DevHub, after KYB and SWSS Foundation approval.

All SwssChain GitHub repositories are private. Significant updates are currently deploying across the full SWSS Ecosystem. SDK and API specifications are subject to change at any time in accordance with security requirements and SwssChain Foundation governance decisions.

Join SWSS DevHub →Have a question? Use the Need Help? button below.
SDK Update Notice

SWSS SDK v2.1 is deploying across the ecosystem. API signatures may change during this period. Ensure your integration uses the latest schema from SWSS DevHub.

Article Content

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 typeTierDecides
PROTOCOL_UPGRADE1A change to the protocol itself
VALIDATOR_ADMISSION2Admission of an operator to the validator set
VALIDATOR_ROTATION2Rotation of a validator's keys to new ones
JURISDICTION_SCOPE2The jurisdictions settlement is scoped to
DEED_CATEGORY2A new deed class in the registry
FEE_ADJUSTMENT2Settlement fee parameters
ADVISORY3A 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