About the Validator Profiles category
What are validators? Validators run the blockchain’s software (for Cosmos Hub this is in the Gaia repository ) to produce and verify new blocks. You can find a list of all of the current Cosmos Hub validators using a block explorer like Mintscan . Validators guarantee security to the blockchain network by “staking”, i.e., putting up their own ATOM or ATOM that has been delegated to them, to produce or verify blocks. If they incorrectly verify a block (by signing the same block twice) or fail to produce blocks (by going offline), they are “slashed” for their misbehavior. In return for correctly verifying and producing blocks, they receive block rewards. When you stake ATOM by ‘delegating’ to a validator (or validators), your ATOM is also put up alongside the validator’s own ATOM (if they are self-delegating). You also receive rewards for the ATOM you have staked. In this way a delegator is sharing in both the risks and rewards of staking and securing the network. For more information on the relationship between delegators and validators take a look at the Delegator FAQ on the Cosmos Hub site. What is their role in governance? Although some other blockchains set direction…
Excerpt (1198 of 2936 characters). Read the whole post on the forum ↗
This is a very useful category. Validator profiles add important context on top of raw metrics, especially given how much responsibility validators carry in Cosmos - block production, security guarantees, and on-chain governance. When delegators stake ATOM, they’re explicitly sharing both risk and reward with their validator. Slashing, downtime, governance votes - all of these have real consequences not just for validators, but for delegators as well. So it makes sense that delegators want to understand how validators operate, how they make decisions, and how they handle incidents. Reading different profiles, one thing stands out: a lot of this trust is still implicit. When something goes wrong - missed blocks, slashing events, disputed governance outcomes - verification usually falls back to dashboards, explorers, or ad-hoc data collected from RPCs. Depending on data sources and timing, the same validator behavior can look different to different observers. That’s how two honest investigations of the same incident can arrive at different conclusions. This feels less like a lack of transparency and more like a gap in verifiability. In other parts of infrastructure, we’re…
Excerpt (1198 of 2042 characters). Read the whole post on the forum ↗