Governance & Treasury

Relevant source files

The following files were used as context for generating this wiki page:

• X3_END_TO_END_GAPS_MASTER_PLAN.md
• MAINNET_LAUNCH_CHECKLIST.md
• plans/PHASE_4_STRATEGIC_OVERVIEW.md
• knowledge-audit-report.md
• reports/prompt-runs/prompt-full-20260427T225413Z.md
• pallets/x3-governance/Cargo.toml
• pallets/x3-treasury-policy/Cargo.toml

Introduction

The Governance and Treasury systems within the X3 project serve as the foundational control and economic management layers of the network. These systems ensure that protocol upgrades, emergency interventions, and capital allocations are executed through verifiable, proof-gated mechanisms rather than arbitrary operator intuition. Governance defines the "runtime law," establishing who can execute privileged actions and under what evidence thresholds, while the Treasury manages the allocation of protocol funds and enforces economic invariants.

Sources: X3_END_TO_END_GAPS_MASTER_PLAN.md:27-40, X3_END_TO_END_GAPS_MASTER_PLAN.md:435-442

Governance Architecture

The governance architecture is structured around a "Constitutional Rulebook" that limits the powers of governance participants. It employs a multi-tiered approach to protocol management, distinguishing between ordinary parameter tuning and constitutional amendments that require higher thresholds and longer delays.

Core Governance Components

Component	Function
Constitutional Rulebook	Defines immutable boundaries and amendment paths.
Proof-Carrying Governance	Requires simulation results and impact reports for sensitive proposals.
Emergency Powers Map	Explicitly defines pause, degrade, quarantine, and kill actions.
Challenger Rights	Enables minority stakeholders to surface issues or pause unsafe changes.

Sources: X3_END_TO_END_GAPS_MASTER_PLAN.md:300-315, X3_END_TO_END_GAPS_MASTER_PLAN.md:325-330

Emergency Response Flow

The governance system includes an emergency framework designed to contain incidents using specific evidence standards.

This flowchart shows the lifecycle of an emergency governance action, from detection to resolution.
Sources: X3_END_TO_END_GAPS_MASTER_PLAN.md:195-200, X3_END_TO_END_GAPS_MASTER_PLAN.md:445-450

Treasury and Economic Policy

The Treasury system focuses on the preservation of economic invariants and the management of protocol reserves. It is governed by policies that prevent unauthorized capital movement and ensure that the total supply remains consistent with the sum of all balances.

Treasury Protection Mechanisms

Treasury operations are integrated into several pallets to ensure shared rails for disputes and compliance.

• Cap-Based Settlement: High-level settlement logic enforces hard caps to protect treasury assets.
• Treasury Policy Pallet: Manages allocation and ensures that revenue-sharing splits are validated (e.g., enforcing exactly 10,000 bps).
• Dispute Paths: Pallets like pallet-x3-auction include force_cancel paths to protect the treasury during contested events.

Sources: MAINNET_LAUNCH_CHECKLIST.md:175-185, MAINNET_LAUNCH_CHECKLIST.md:198-205

Economic Invariant Verification

The system enforces a "Canonical Supply" invariant, which is a hard rule preventing the minting of assets without permission.

This diagram represents the supply ledger invariant check performed during state transitions.
Sources: knowledge-audit-report.md:160-168, MAINNET_LAUNCH_CHECKLIST.md:95-100

Implementation Gaps and Hardening

Current project documentation identifies several "Band 0" and "Band 1" gaps that must be addressed for the governance and treasury systems to be considered production-ready.

Critical Readiness Gates

1. Enforceable Invariants: Invariants must be written as enforceable runtime rules, not just implied by code.
2. Explicit Emergency Powers: Documentation must define who can stop what, under what evidence threshold, and with what expiration rules.
3. Governance Delays: Implementing constitutional limits and mandatory delays for sensitive parameter changes.
4. Security Audit: The pallet-x3-governance and pallet-x3-treasury-policy require formal audits covering route dispatch and supply invariants.

Sources: X3_END_TO_END_GAPS_MASTER_PLAN.md:27-40, MAINNET_LAUNCH_CHECKLIST.md:130-145

Summary

The Governance and Treasury modules of X3 provide the necessary "runtime law" and economic guardrails for the network. By utilizing proof-carrying state transitions and explicit emergency powers, the system moves away from trusted operator intuition toward machine-enforced policy. The treasury ensures that the protocol's economic integrity is maintained through strict invariant checks and cap-based settlement protections, which are essential for mainnet launch.

Sources: X3_END_TO_END_GAPS_MASTER_PLAN.md:180-185, MAINNET_LAUNCH_CHECKLIST.md:230-240