Skip to content

Governance and control

Juris governance contracts support proposals, voting and execution of approved actions. Staking includes voting-power accounting that can be connected to those contracts.

On September 22, 2026, the configured mainnet staking contract returned governance=null. The Juris UI’s mainnet configuration also had no governance contract address. These observations do not establish an active voting route for mainnet stakers.

The chain query was not pinned to a block height. The deployment reference lists the configuration and query methods.

The governance implementation supports simple proposals containing Cosmos messages and multiple-choice proposals. Its rules include quorum, deposits, voting periods, tallying and closing proposals.

A proposal can change a target contract only when governance has the required execution permissions. Voting-power accounting alone does not transfer administrative authority.

Juris contracts have administrative and operating roles:

  • Margin administration controls module links, collateral thresholds and fees.
  • Oracle administration assigns authorized price feeders.
  • Vault administration controls roles; bidder and allocator roles manage bids and inventory.
  • A Wasm migration administrator can authorize code upgrades separately from application-level settings.

These permissions can affect market access, risk parameters and positions. See Security and administrative controls for the contract-level details.