№ 11·0411 · Governance and Compliance2 min read · Section 4 of 6
11.4 What should never be put to a public vote
The six items the Constitution places outside any vote: core privacy, AML and compliance, formed PoB records, signed legal agreements, the interests of absent minorities, and long-term sustainability.
Updated
11.4 · Never-votable items
Six items can never be put to a vote. Knowing what cannot be voted on is as important as knowing what can.
The Constitution places six items outside any vote. This is not a stance against participation. It recognizes that certain decisions, once overridden by majority weight or short-term pressure, would damage the existence or legitimacy of the network. The list sits beside the responsible layers and forms part of governance itself.
Core answerWhich decisions can no majority override?
Why a fixed listTo stop the network legitimizing harm under pressure
ReferenceWhitepaper v2.1 §9.3, the six never-votable items
The six never-votable items
The Constitution (L0) defines these six items. No node vote, token weight, or majority decision can override them. They remain with the responsible layers under the framework of law and charter.
1 · Core privacy rightsA node's core privacy rights cannot be violated by majority vote. A majority cannot expose or strip the privacy that membership protects.
2 · AML and complianceAML and compliance enforcement cannot be bypassed. No vote can exempt the network from anti-money-laundering obligations or sanctions screening.
3 · Formed PoB recordsA formed PoB record cannot be altered after the fact. Once an outcome is verified onto the proof ledger, no vote can rewrite it.
4 · Signed legal agreementsA signed legal agreement cannot be unilaterally breached. A majority cannot vote to walk away from a binding commitment.
5 · Absent minority nodesAn emergency motion that harms absent minority nodes cannot pass. Urgency cannot be used to strip the interests of nodes not in the room.
6 · Long-term sustainabilityA short-term payout that damages long-term sustainability cannot pass. The network cannot vote itself a near-term gain at the cost of its future.
Why these items stay outside any vote
Each item protects something a majority could otherwise damage under pressure. Three forces make open voting unsafe in these domains.
Short-term pressure can push a majority to override actions that are legally necessary but locally unwelcome. A fixed list removes that option before the pressure arrives, rather than during it.
Rights are not majority-disposablePrivacy, signed agreements, and the interests of absent nodes are commitments. A vote cannot dissolve a duty the network already owes.
Records are settled, not reopenedA formed PoB record is the network's memory of a verified outcome. Reopening it to a vote would make every record provisional.
Compliance is not optionalAML and sanctions obligations bind the responsible parties under law. A community vote cannot waive them without creating real liability.
The future has no votePeople in the room can favor a payout today. The list protects the long-term interest that absent and future participants depend on.
How the list is enforced
A list is only as strong as its enforcement. WCN binds it in writing and at the technical layer, and lets it grow but never shrink without due process.
Written and disclosed
The non-votable items appear in the charter, the governance materials, and the node documents. They are not informal red lines.
Enforced in the system
Permissions and contracts are configured so a single proposal cannot reach a non-votable item. The block is structural, not procedural.
Can grow, not shrink
As compliance requirements change, the list can expand. It contracts only through a formal charter revision and the proper legal process.
Knowing what cannot be voted on protects the network from legitimizing harm under pressure. The six items guard privacy, compliance, settled records, signed commitments, absent minorities, and the long term.
