A Practical Way To Avoid a Chance of Downtime Penalty in Cosmos Network

Mira Nugumanova
Apr 18 · 3 min read

One of the most important factor to consider when staking in Cosmos is a probability of being penalized when a validator does not follow protocol rules. There are two types of events that will trigger the slashing of the stake: double-signing and unavailability. It is crucial to note that these penalties affect not only validators self-delegated stake but also tokens bonded by delegators. This punishment can be as high as 5% for double-signing and 0.01% if a validator misses 95% of blocks in a rolling 10,000 block window.

The illustration is taken from https://www.gettyimages.ae/detail/illustration/astronaut-in-open-space-eliminates-the-royalty-free-illustration/841653254

Current average time for a block in the network is 6.85 seconds. This equates to about 18 hours of consecutive downtime (10,000 x 0.95) x 6.85s = 65075 seconds = 1084.58min = 18.07hr

This means that there is enough time for you to act and redelegate tokens before the penalty occurs.

4 Easy Steps to Set up Validator Monitoring

  1. Step one is to set up monitoring of your validator uptime.

To do so, navigate to Hubble Explorer and select validator you have delegated your $ATOMs to https://hubble.figment.network/chains/cosmoshub-1

2. Scroll down to “Event History” and click “Subscribe

3. You will be asked to create an account with the email where you want notifications to be sent to.

4. On the next screen, there will be 4 different metrics, which you might want to subscribe to. The one that is most relevant to track to avoid at being slashed is “Misses N of Last M Precommits”

It is important to note that missing 150 blocks out of last 1,000 blocks, might not be a deal breaker to take out your stake but it is the only number that Hubble team offers. The tool will send you an alert email to keep an eye/ping validator to find out what is happening.

Remember that the slashing will occur only when 9,500 blocks missed.

After receiving an alert email, it is a good practice to monitor if and when the team is able to bring it back up in a timely manner. If the node has been down for more than 16 hours with no update from the team when it will be back up, you should consider redelegating $ATOMs staked.


If you want to learn how to do redelegate tokens staked, read our previous medium post: How to Re-Delegate Cosmos $ATOMs with Lunie Web-Wallet.

If you still have not decided who you should delegate your hard-earned $ATOMs to, consider reading the following article: How to Choose Cosmos Validator.

If you are having trouble with the guide or simply want to stay in the loop, please follow us on Twitter or join our Telegram channel.

Mira Nugumanova

Written by

PoA and PoS node operator. https://ztake.org/