Rivellum uses a three-phase on-chain governance mechanism for protocol parameter changes.

Governance Phases

1. Proposal Phase

Any address holding ≥ the minimum proposal threshold in RIVL can submit a governance proposal. Proposals specify a parameter change, a justification, and a voting window.

2. Voting Phase

Validators and token holders vote during the voting window. Votes are weighted by stake. A proposal passes if it receives >2/3 approval by weighted stake.

3. Enactment Phase

Passed proposals enter a time-lock period before taking effect. This gives operators time to prepare for parameter changes.

Proposal Types

Tunable Parameters

Parameters are grouped into categories:

Fee Parameters

• Base fee multiplier
• Gas-to-RIVL conversion rate
• Minimum and maximum fee bounds

Consensus Parameters

• Committee size
• Batch timeout
• QC threshold adjustments

Admission Parameters

• Rate limits
• Queue depth limits
• Backpressure thresholds

PoUW Parameters

• Job lease duration
• Maximum retries per job
• Reward scaling factors

Immutable Invariants

The following cannot be changed through governance:

These are hardcoded protocol constants, not governance parameters. The fee split validation in GovernanceChangeRequest::validate() rejects any modification.

Emergency Controls

Guardian role can:

• Freeze a specific asset (EmergencyFreeze)
• Pause a specific contract
• Cannot modify fee distribution or supply

Emergency actions require guardian multi-sig threshold and are logged in the governance history.

API Endpoints

For tokenomics details, see Tokenomics.