Change: raise MaxValidators parameter from 50 to 65 on Axone Network.
Goal: improve validator diversity and decentralization with minimal impact on network performance.
Scope: parameter-only change; no modifications to slashing, unbonding, or block timing.
Context and Motivation
The active validator set is currently capped at 50, sorted by total stake. Following stronger-than-expected traction at Mainnet launch, there is significant demand to expand the active set.
Raising the cap to 65 will:
diversify validators
enhance decentralization
avoid dramatic changes that could create p2p issues
Parameter Change
MaxValidators: 50 → 65
Expected Impact
Positive: broader validator participation and improved resilience.
Neutral: no change to slashing parameters, unbonding period, or block time.
Low risk: limited effect on performance and networking.
Governance Voting Options
Below are the voting choices for this proposal and what each option mean
Vote YES – You support increasing MaxValidators from 50 to 65.
Vote NO – You oppose increasing MaxValidators from 50 to 65.
Vote NO WITH VETO – This indicates that you consider the proposal irrelevant to Axone, harmful to minority interests, or in violation of (or encouraging violation of) Axone’s code of conduct. If “No with Veto” votes exceed one‑third of the total votes, the proposal is rejected and all deposited funds are burned.
Vote ABSTAIN – You participate in reaching quorum but choose not to take a position for or against the proposal.
after long time of waiting, now the active set finally expanded.
but the amount of active set still low. while axone should have a total 82 validator (active and inactive).
Since the beginning of the delegation program, many validators should have been in the active set (as most were early supporters). However, due to the active set limit of 50, and this prolonged period, most validators received nothing, despite receiving substantial delegations from the team. This is tantamount to giving something that doesn’t exist.
Perhaps some validators are also application developers, and perhaps some have an ecosystem ready to integrate with the Axone blockchain, but in reality, the support provided is not optimal, and perhaps some simply remain silent, afraid that their delegations will be taken away and not included in the active set.
And of course, with this kind of situation, validators who intend to develop something on Axone may feel lazy and unappreciated from the start.