Governance
Governance Parameters
Pre-launch
Section
Governance
Documentation category
Type
Guide
Technical reference
Summary
The live SwssChain mainnet governance parameters (quorum thresholds, voting windows and the Foundation veto period) read from the contract.
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

These are the values the governance contract holds on SwssChain mainnet 122605, read from the contract rather than taken from a specification. Testnet 122606 runs the same values.

Live Parameters

ParameterValueApplies to
Upgrade quorum threshold51%Tier 1 protocol upgrades
Admission quorum threshold67%Validator admission and rotation
Standard voting window50,000 blocksApproximately 13.9 hours at one-second blocks
Urgent voting window5,000 blocksApproximately 1.4 hours
Foundation veto period2 hoursAfter a proposal passes, before it may execute
Validator count used for quorum4The quorum denominator

The two thresholds differ on purpose. Admitting a validator changes who signs Finality Certificates, and a certificate is worth what the identity of its signers is worth, so admission requires a higher bar than a protocol upgrade the Foundation can veto anyway.

Voting Windows Are Block Counts

Both windows are expressed in blocks, not hours. At one-second blocks the durations above follow, but the parameter is the block count and it is what the contract enforces. Anything scheduling around a governance vote should compute from block height, not from a clock.

Bounds the Contract Enforces

BoundValueWhy it exists
Quorum threshold range1 to 100Zero makes quorum impossible; above 100 makes it unreachable
Maximum veto period168 hoursBeyond one week the veto-window timestamp check overflows and execution locks permanently
Maximum validator count100A count far above the real set makes quorum permanently unreachable

These are not style guidelines. Each one bounds a value that, set outside it, would permanently disable part of the governance contract, so the contract rejects them rather than accepting a parameter update that bricks itself.

Where the Address Comes From

The governance contract address is not printed here. Contract addresses resolve from the deployment record, never from a document, a published address is a claim that needs a release to correct, and a stale SWSS address usually still has code, so the failure mode is plausible answers from the wrong contract rather than a clean error. Resolve it through your issued SWSS DevHub configuration.

Changing a Parameter Is Itself a Proposal

Parameters are updated through the governance process they configure, a Tier 2 proposal, subject to the quorum and veto rules currently in force. There is no administrative path that sets them directly.

Next Steps

Frequently Asked Questions
6 questions
Are mainnet and testnet parameters the same?

They currently hold the same values. Read them from the contract rather than assuming: parameters are changed by proposal, and a document is a snapshot.

Why is admission quorum higher than upgrade quorum?

Admitting a validator changes who signs Finality Certificates, and a certificate is worth what the identity of its signers is worth. A protocol upgrade can also be vetoed by the Foundation; an admission that has already executed is harder to unwind.

Is the voting window a duration or a block count?

A block count. The hour figures follow from one-second blocks, but the contract enforces blocks: schedule from block height, not from a clock.

Does abstaining help a proposal pass?

No. Quorum is measured against the recorded validator count, not against turnout, so an abstention counts against the proposal.

Where is the governance contract address?

Not published here. Addresses resolve from the deployment record through your issued configuration, a stale SWSS address usually still has code, so the failure mode is plausible answers from the wrong contract rather than a clean error.

Can a parameter be changed without a vote?

No. Parameters are changed by a Tier 2 proposal subject to the rules currently in force. There is no administrative path that sets them directly.