Validator Commission Changes: How to Do Them Safely

Validator Commission Changes: How to Do Them Safely

Published
AuthorDevansh

Commission is the percentage of staking rewards a validator keeps before the rest is shared with delegators. It pays for the server, the monitoring, the upgrades, and the operator time, and it is also the number delegators watch most closely after uptime. Changing it is therefore not a bookkeeping task, it is a trust event: a fair, announced change keeps delegators, and a sudden jump loses them. This post covers what commission is, the exact rules on Cosmos and Solana, why sudden raises destroy trust, and a checklist for changing it safely.

If the validator and delegator roles are new to you, start with our validator vs delegator guide and our guide to choosing a validator. This post assumes you already run a validator or are about to, and it is about changing the rate, not setting it for the first time.

What commission is and why it changes

When a validator earns rewards, the network first takes the validator commission off the top, then splits the remainder among everyone who staked with that validator, in proportion to their stake. A 5 percent commission means the validator keeps 5 percent of the rewards and delegators share the other 95 percent. Commission is how honest infrastructure gets paid, and it changes for honest reasons: server costs rise, a chain upgrade needs bigger hardware, a team hires someone to watch the node at night, or a validator that launched at 0 percent to attract stake needs a sustainable rate to keep running. The problem is never that commission changes. The problem is how it changes: silently, suddenly, or by an amount no delegator could have expected.

Cosmos: one change per day, and the caps are forever

On Cosmos chains, three numbers govern commission, and two of them are fixed at the moment the validator is created and can never be changed afterwards. The commission rate is the current cut. The commission max rate is the highest the rate can ever go. The commission max change rate is the most the rate can move in a single day. Both caps are permanent: if you set a max rate of 20 percent at creation, you can never charge more than 20 percent, and if you set a max change rate of 1 percent per day, a jump from 5 to 10 percent takes five days of separate changes, not one.

The chain also enforces a pace limit: the commission rate can be changed at most once per 24 hours, and the clock starts at validator creation, so a change in the first 24 hours, or a second change inside 24 hours, fails on chain. On Cosmos Hub the minimum commission is 5 percent, enforced by the chain, and a lower value is rejected when the transaction executes. The command is the validator edit command, and only the flags you pass change:

gaiad tx staking edit-validator   --commission-rate="0.07"   --from=mykey --chain-id=cosmoshub-4

Check the result before you announce anything: query the validator afterwards and confirm the new rate is on chain, because a failed transaction changes nothing and a silent failure looks exactly like a successful one until a delegator checks. The lesson for new validators is to set the caps carefully at creation: a max rate that is too low traps you when costs rise, and a max change rate that is too high lets a mistake, or a compromised key, jump the rate in one move. Our Cosmos validator setup guide covers the creation step where these numbers are chosen.

Solana: the epoch delay, and the new basis-points rules

On Solana, commission lives in the vote account, and only the vote account authorised withdrawer keypair can change it. The classic rule was a timing window: a validator could only raise commission during the first half of an epoch, so a raise could never surprise delegators right before rewards were distributed at the end of the epoch. The command is the vote commission update, signed by the authorised withdrawer:

solana vote-update-commission   ~/vote-account-keypair.json 8   --authorized-withdrawer ~/authorized-withdrawer-keypair.json

That rule has recently changed, and this is where operators need to check their client version before acting. Under SIMD-0249, any commission update, up or down, takes effect only after a full epoch delay, replacing the old first-half-of-epoch window with a stronger rule: a raise filed today applies to the epoch after next, so it is visible on chain a full epoch before it costs a delegator anything. Alongside it, SIMD-0291 moves commission from whole percents to basis points for finer rates, and SIMD-0123 adds a separate commission for block revenue, so a validator now has two commissions to manage: one on inflation rewards and one on block revenue. The Agave 4.4 CLI exposes the new controls with vote-update-commission-bps, with a commission kind of inflation-rewards or block-revenue. If you run an older client, the classic command and the old timing window still apply, so confirm which rule set your version enforces before you file a change, and say which one you used when you announce it.

Why sudden raises destroy trust

Delegators choose a validator on the rate they see, and they stay because the rate is predictable. A validator that advertises 5 percent, attracts stake, and then jumps to 100 percent has not changed a price, it has broken an agreement, and the chain rules above exist precisely because that trick was tried often enough to need protocol-level protection. Even a legal, in-window raise can do damage if it is large and unexplained: delegators read it as a signal that the operator is in trouble or does not care, and they redelegate, which on Cosmos takes 21 days of unbonding to complete and on Solana takes until the end of the epoch. A lost delegator rarely comes back, and a validator that loses stake loses voting power, rewards, and position in the set, which makes the next raise more likely, not less. The economics are simple: a sustainable rate that keeps delegators is worth more than a high rate that empties the validator. Our slashing explainer covers the other way operators lose delegators, and the pattern is the same: trust is the product, and the node is only the delivery mechanism.

A safe change checklist

One, know your current rate, your max rate, and your max change rate before you touch anything, and check whether the change you want is even allowed in one step. Two, decide the new rate from costs, not from what other validators charge: if the current rate does not cover the server, say so, and pick a rate that does, because a validator that cannot pay its bills will shut down, which costs delegators more than a fair raise. Three, announce the change before you file it, in every channel your delegators actually read: the new rate, the date it takes effect, the reason, and what it means for a typical delegator reward. Give at least a full epoch, or a full day on Cosmos, of notice. Four, file the change with the correct key, in the correct window, and verify on chain or in an explorer that the new rate is live. Five, watch what happens next: stake movement, delegator questions, and your own reward flow, and answer questions publicly instead of letting rumours fill the gap. If the change was a raise and stake falls, that is data, not betrayal, and the right response is to explain the costs again, not to raise the rate further to compensate.

Commission is the price of honest infrastructure, and a fair price, changed fairly, is something delegators accept. Set your caps carefully at creation, respect the chain pace limits, announce before you act, and verify after you file. If you are setting up a validator, or your current rate no longer covers the cost of running it properly, book a free infra audit with DevOpsBY. We run nodes, RPC, and validator infrastructure for Web3 teams, and we will help you price the operation so the rate is sustainable without losing the delegators who fund it.

Disclaimer: This post is educational only, not financial advice. Figures are listing or project data as of 2026-11-11 and may change - always confirm version numbers, requirements, and dates in the official docs before acting on them.

Related Articles

DevOps & Infrastructure Services

Need hands-on help? We build and manage the infrastructure behind the concepts covered in this article.

DevOpsBy Assistant

How can we help?

Select a topic to get started: