Voting on cheqd

Learning the basics

Before you dive into this section, we suggest that you familiarise yourself with the basic concepts surrounding Governance which can be found here.

How do I Vote?

Voting on cheqd is a core part of the Network and how each individual User can influence the direction of change. cheqd voting is based on a liquid democracy model, whereby Users can vote unilaterally or delegate their votes to a Node Operator of their choice.


Participants are Users that have the right to vote on proposals. In the cheqd Network, participants are bonded CHEQ holders. Bonding means something different for Node Operators and for everyday Users:
    Node Operators can ‘self-bond’ their staking tokens in order to vote on governance matters;
    Everyday Users can ‘bond’ their tokens to a Node Operator, this is known as delegation.
Unbonded CHEQ holders and other Users do not get the right to participate in voting on Proposals. However, they can submit and deposit on Proposals.
Note that some participants can be forbidden to vote on a proposal under a certain Node Operator if:
    Participant has bonded or unbonded CHEQ to a particular Node Operator after the proposal has entered its voting period.
    Participant set up a node and became a Node Operator after the proposal entered its voting period.
This does not prevent the participant voting with CHEQ bonded to other Node Operator. For example, if a participant bonded some CHEQ to Node Operator A before a proposal entered voting period and other CHEQ to Node Operator B after proposal entered voting period, only the vote under Node Operator B will be forbidden.


If a Participant does not vote, it will inherit the Node Operator's vote which it is bonded to.
If the Participant votes before its bonded Node Operator, it’s vote will take precedence; the Node Operator will not inherit the Participant's vote.
If the Participant votes after its Node Operator, it will override its Node Operator vote with its own. If the Proposal is urgent, it is possible that the vote will close before Proposal has a chance to react and override their Node Operator's vote.

Voting period

Once a proposal reaches MinDeposit, it immediately enters Voting period. We define Voting period as the interval between the moment the vote opens and the moment the vote closes. Voting period should always be shorter than the Unbonding period to prevent double voting.
The initial value of the cheqd Voting period is 2 weeks.

Unbonding period

Unbonding period is defined as the time to withdraw your bonded tokens from a Node Operator to gain full access to these tokens in liquid form.
The initial value of the cheqd Unbonding period is 3 weeks.

Option set

The option set of a proposal refers to the set of choices a participant can choose from when casting its vote.
The initial option set includes the following options:
NoWithVeto counts as No but also adds a Veto vote. This is significant because a 33.34% veto will burn the tokens in the ModuleAccount. This means that the tokens will be destroyed and put beyond use. For this reason, it is important that Participants make reference to cheqd's Principles before using the veto vote.
Abstain option allows voters to signal that they do not intend to vote in favor or against the proposal but accept the result of the vote.

Weighted Votes

Note: Weighted voting may not be available in the first iteration of the cheqd Network
Users casting a vote on a proposal have the option to split their votes into several voting options. For example, a User could use 70% of its voting power to vote Yes and 30% of its voting power to vote No.
Often, the entity owning a particular governance address might not be a single individual. For example, a company might have different stakeholders who want to vote differently, and so it makes sense to allow them to split their voting power. Currently, it is not possible for them to do "passthrough voting" and give their users voting rights over their tokens. However, with this system, exchanges can poll their users for voting preferences off-chain, and then vote on-chain proportionally to the results of the poll.
For a weighted vote to be valid, the options field must not contain duplicate vote options, and the sum of weights of all options must be equal to 1.


Quorum is defined as the minimum percentage of voting power that needs to be cast on a proposal for the result to be valid.
The quorum as a default setting is 33.34%.
Going forward, more complex quorum mechanisms, such as Adaptive Quorum Biasing should be considered.


Threshold is defined as the minimum proportion of Yes votes (excluding Abstain votes) for the proposal to be accepted.
Initially, the threshold is set at 55% with a possibility to veto if more than 33.34% of votes (excluding Abstain votes) are NoWithVeto votes. This means that proposals are accepted if the proportion of Yes votes (excluding Abstain votes) at the end of the voting period is superior to 55% and if the proportion of NoWithVeto votes is inferior to 33.34% (excluding Abstain votes).

Node Operator's punishment for non-voting

At present, Node Operators are not punished for failing to vote.

Governance address

At launch, the Governance address will be the main Node Operator address generated at account creation. This address corresponds to a different PrivKey than the Tendermint PrivKey which is responsible for signing consensus messages. Node Operators thus do not have to sign governance transactions with the sensitive Tendermint PrivKey.

Burned deposits

Deposits are burned when proposals:
    Expire - deposits will be burned if the deposit period (2 weeks) ends before reaching the minimum deposit (8000 CHEQ);
    Fail to reach quorum - deposits will be burned for proposals that do not reach quorum within the 2 week voting period, i.e. 33,34% of all staked CHEQ must vote;
    Are vetoed - deposits for proposals with 33.4% of voting power backing the 'no-with-veto' option are also burned.
To learn more about when you should exercise the veto vote, refer to our Second Foundational Principle, the Balancing Principle.

Software Upgrade

If proposals are of type SoftwareUpgradeProposal, then nodes need to upgrade their software to the new version that was voted. This process is divided into two steps:


After a SoftwareUpgradeProposal is accepted, Node Operators are expected to download and install the new version of the software while continuing to run the previous version. Once a Node Operator has downloaded and installed the upgrade, it will start signaling to the network that it is ready to switch by including the proposal's proposalID in its precommits.
Note: There is only one signal slot per precommit. If several SoftwareUpgradeProposals are accepted in a short timeframe, a pipeline will form and they will be implemented one after the other in the order that they were accepted.


Once a block contains more than 2/3rd precommits where a common SoftwareUpgradeProposal is signaled, all the nodes (including Node Operator nodes, non-validating full nodes and light-nodes) are expected to switch to the new version of the software.
Last modified 10d ago