Validator Update #2 — A fresh start

The Problem

Simplified illustration of the issue

The Solution

  1. We set up additional monitoring regarding differences in block height between our validators. If our validators diverge too much, our system is going to alert us immediately.
  2. We configured our Raft Housekeeper to keep a minimum of 7200 entries in the permission log at all times. For an average block time of six seconds, this gives us at least 12 hours to react to incidents like this. This definitely gives us enough leeway in the long run.

Our New Validator

--

--

--

Validator operator in 20+ PoS blockchains. Visit us at www.blockscape.network.

Love podcasts or audiobooks? Learn on the go with our new app.

Recommended from Medium

SOLID Software Design Principles-Write better code(OOP)

The Coding Pattern Guide: Why You Should Follow Patterns While Coding

Importance of Math in C.S.

Format dates in Python using f-strings

How to Port Python on iMX6Q Development Board

I’ve Cracked the Code, Please Call Tech Support- Episode 27, The Six Logins

Redshift Table Design Best Practices

RabbitMQ Spring Boot #03 — Exchange configuration

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store
blockscapeLab

blockscapeLab

Validator operator in 20+ PoS blockchains. Visit us at www.blockscape.network.

More from Medium

Deflationary token, inflationary APR: CHANGE tokenomics, Leveraged Staking, and burn mechanism

KavaiiSwap: A DEX on Kava EVM

sNSBT_TCI is growing up!

How To Stake NYM (without bridging)