Kleomedes - Validator Profile
Kleomedes: Sovereign Infrastructure for the Cosmos Ecosystem Hello, Cosmonauts! We are Kleomedes, and we operate sovereign, bare-metal infrastructure from Naples, Italy. The Cosmos ecosystem has been our home since early 2020, when we began validating a handful of chains. In January of 2026, we joined the Cosmos Hub active set. We believe that decentralization should extend beyond consensus rules. It should also apply to the physical infrastructure and geographic distribution of the organizations responsible for running the network. There are many qualified providers validating the hub, but let us explain why we bring a few more things to the table beyond simply signing blocks. We hope these contributions are enough to convince you that we are deserving of your delegation. Introduction to Kleomedes Kleomedes was founded in 2020 by Marco Rinaldi with a simple objective: build reliable blockchain infrastructure without depending on a handful of cloud providers and data centers used by much of the industry. Instead of renting our core infrastructure from Hetzner, OVH, AWS, Google Cloud, or other centralized providers, we purchase, assemble, rack, and maintain our own…
Excerpt (1194 of 7993 characters). Read the whole post on the forum ↗
Welcome to the forum. Stake-Hub sounds useful for people trying to compare validators. Does it also explain the different metrics in plain language for newer delegators who may not know what each one means?
Appreciate the question! Right now, stake-hub is essentially another way for users to stake outside keplr wallet. The main thing it adds is the “decentralize delegations” button which randomly picks a few validators within the middle of the pack to delegate to. The goal was to eventually create a feature that helps new validators bootstrap delegations by initially delegating to someone within the middle of the set and once enough commitments have been made to support a new validator, having AuthZ re-delegate to that validator to bring it well into the active set (at least 10-20 spots from the bottom of the set). That way people can continue earning rewards while also signaling support to bring new validators onboard while also decreasing the risk of missing out on rewards if they end up falling out of the set as soon as they get in. This isn’t live yet but if enough users want it, its something we can work on again. Otherwise, all the other features I described (performance for ancillary services and geolocation) are primarily used by foundations when making decisions about foundation delegation programs. Users can still see that data but it’s not necessarily geared towards…
Excerpt (1196 of 1435 characters). Read the whole post on the forum ↗
Thanks for explaining. The “decentralize delegations” option sounds useful. A short, plain-language explanation of why those validators are selected would probably help newer users feel more comfortable using it.
If you look at the bottom of the window there is a blurb there, right above the delegate button. If you feel it could be refined/made better, feel free to suggest any changes and we can implement them!
I see it now, thanks. The explanation itself is clear, but it was easy to miss at the bottom. Maybe placing it closer to the “Selected Validators” heading or making it slightly more noticeable would help newer users understand the selection before delegating.