Skip to main content
The Governance overview explains how protocol governance works and what it controls. This page focuses on participating in governance: submitting proposals, voting, software upgrades, and the operational mechanics of the governance module. Lumera uses the Cosmos SDK governance module (x/gov). Protocol proposals are submitted and voted on entirely on-chain, allowing the network to evolve through transparent community coordination rather than centralized administration.

​
Proposal lifecycle

Every governance proposal follows the same lifecycle from submission to execution.
1

Submit

A proposal is submitted with an initial deposit. Once the required minimum deposit is reached, the proposal enters the voting period.
2

Vote

During the voting period, holders of staked LUME cast votes. Validators vote with their delegated stake by default, while delegators may override their validator’s vote for their own stake.
3

Tally

At the end of the voting period, votes are tallied according to the protocol’s governance rules, including quorum, threshold, and veto requirements.
4

Execute

Approved proposals execute according to their proposal type. Parameter changes take effect automatically, while software upgrade proposals schedule coordinated network upgrades.
Supported vote options are:
  • yes
  • no
  • abstain
  • no_with_veto
A no_with_veto vote signals that a proposal is considered harmful or malicious rather than simply undesirable.

​
Voting with lumerad

Query all governance proposals currently on-chain.
Vote on an active proposal.
Replace yes with no, abstain, or no_with_veto as appropriate. For Testnet, replace the chain ID with:

​
Browsing proposals

Governance activity can also be viewed through the Lumera Portal. The Portal displays proposal status, voting windows, deposits, validator voting records, and final vote tallies.

​
Software upgrades

Software upgrades are coordinated through on-chain governance. Upgrade proposals specify the target software version together with an upgrade height. Once the blockchain reaches that height, block production pauses until validators install the approved binary and resume consensus. Operators are encouraged to automate this process using Cosmovisor. See the Validator Operations guide for recommended upgrade procedures.

​
Lumera Enhancement Proposals (LEPs)

Lumera Enhancement Proposals (LEPs) are the protocol’s design documents. They describe architectural changes, protocol improvements, and new capabilities before those changes are proposed through on-chain governance. LEPs are maintained in the Lumera repository: https://github.com/LumeraProtocol/lumera/tree/master/docs/leps A LEP documents the technical design and rationale behind a proposal. When implementation requires protocol changes, the corresponding governance proposal becomes the mechanism through which the network formally adopts that design.

​
Governable protocol parameters

Most protocol behavior is configurable through governance rather than fixed in software. Examples include:
  • Protocol-service pricing
  • Security issuance parameters
  • Transaction fee distribution
  • Everlight funding allocations
  • SuperNode operating parameters
  • Governance thresholds and voting periods
  • Community Pool expenditures
Current parameter values can be queried directly from the network and may change through approved governance proposals.

Protocol Governance

Learn how governance fits into Lumera’s protocol architecture.

Validator Operations

Configure automated software upgrades using Cosmovisor.

Protocol Modules

Explore the modules and parameters governed on-chain.