The governance system contract is based on the default implementation of the Compound’s Alpha governance, where voting power depends on the total delegated amount of the validator. The validator’s owner is responsible for voting in favour of or against the proposals on governance. Presently, the required quorum to be reached is ⅔.

Under which circumstances is the proposal applied?

Chiliz implements the default Compound’s Alpha governance, where voting power is distributed amongst validators' owners based on their total delegated amount. Once a quorum of ⅔ is reached, a proposal can be applied.

This governance is fully compatible with the compound's version. However, it has only one improvement: it allows proposal creation with a custom voting period.

For some methods, it is important to have a shorter voting period. For example, when some emergency actions need to be applied. To achieve this, we can extend the original implementation by adding the method proposeWithCustomVotingPeriod. This allows for specifying the voting period for the proposal.

Under which circumstances is the proposal defeated?

Once the quorum is reached and more than 50% of voting power is given for the proposal then it can be executed right after the voting period is done. If a proposal can’t reach the required quorum in the voting period then it becomes defeated.

Consensus params

struct ConsensusParams {
    uint32 activeValidatorsLength;
    uint32 epochBlockInterval;
    uint32 misdemeanorThreshold;
    uint32 felonyThreshold;
    uint32 validatorJailEpochLength;
    uint32 undelegatePeriod;

BSC compatibility

Chiliz Chain is compatible with BSC and Parlia consensus. In an EVM executor, the only new additions are the hooks for checking ACL policies, which are about 40 lines of code.

Last updated