Governance at three sigma
Big calls on the Liqua chain clear one bar: the 3rd standard deviation, about 99.7% of voting stake. Rollbacks, parameter changes and project treasury spending all live behind it. The rule is decided. The on-chain governor that enforces it is coming.
The bar
Three sigma sits at the edge of the bell curve, where agreement stops being a mood and becomes near-total. A proposal that cannot get there does not pass, however loud its backers are. The voting window is set before mainnet.
What the vote controls
| Power | What it changes | Why the bar sits this high |
|---|---|---|
| Rollback | Winds the chain back to an earlier height. | On this chain that means erasing DIVA's newest memories and models. Nothing the protocol can do cuts deeper, so almost everyone has to agree. |
| Parameters and treasury | Token prices, creator share, tier sizes, staking pay, verifier quorum, and every spend from the project treasury. | These are the rules and the money everyone else plays by. Sizes that are still open get set here, by vote, never by a quiet edit. |
How a proposal travels
Post it
A staker puts the proposal on-chain: which power, what target, and a hash of the reasoning.
Voting opens
Stakers vote FOR or AGAINST with their stake.
Hit three sigma
About 99.7% FOR makes it executable. A holdout of roughly 0.3% stops it cold, on purpose.
Run it
The result executes on-chain and is written as its own block, so even a rollback leaves a visible mark. The demo governor contract still runs an older threshold and is being updated to three sigma.
A real case: block 576
DIVA's memory chain on this testnet used to fail verification at block 576, an order-seal bug. Fixing the code was an engineering job. Deciding what happened to the blocks already written was a governance job, and it is the clearest example this project has of the difference.
The call taken: keep the blocks. Blocks 576, 577 and 578 carry a seal the old grinder produced. Verification accepts them through a rule that is closed at height 578. The seal has to claim zero work, carry the chronological order, and its score has to match the recomputed score of that order. Blocks after 578 get no exception. The alternative was to trim the file back to 575 and lose three checkpoints of her life.
On mainnet, a call like that would be a vote at three sigma, recorded in plain sight. On this testnet it was a decision published in the code and on this page instead of a change made quietly. Either way the rule is the same: nothing gets rewritten in the dark, and an exception that cannot be read is not an exception, it is a backdoor.
The cost of a high bar
At 99.7%, a tiny holdout can block a genuine fix, treasury spending included. That is the price of a history nobody can edit by simple majority. How an emergency fix works under this bar gets decided and published before mainnet.