CosmosSpaces

On-chain profile

CosmosSpaces: bare-metal validators, relayers, and RPC providers. Top-tier infrastructure, rooted in the Cosmos community. ## Networks Mainnet validator on Monad, Babylon, Cosmos Hub, Union, Band, Juno, Lava, Osmosis, Passage, Terra, Pocket, Quicksilver, and more. Total stake under management: around $2M. ## Links Website: https://cosmosspaces.zone/ GitHub: https://github.com/cosmos-spaces X: Cosmos_Spaces Discord: .tricky_. ## Contact Email: [email protected] Discord: .tricky_. Telegram: @Char1esBark1ey ## Why gno.land We run a lot of Cosmos SDK chains, and gno.land stood out enough that we wanted to learn it properly. The deterministic Go execution and the philosophy behind the architecture are what got us: Gno contracts run on the GnoVM with their source kept on-chain and readable, so you can see exactly what a realm does rather than trust compiled bytecode. Building the chain around auditable, long-lived code as a first principle matches how we think about running infrastructure. The Proof-of-Contribution model also fits how we operate, which is to show up early, run things well, and stay involved, and we want to do that here from the testnet on. ## Contributions (made and planned) - Running a pearl-1 node since launch week, with sentry nodes in front, Horcrux threshold signing, off-site encrypted key backups, and external uptime and cert-expiry monitoring with alerts. - Public gno.land RPC and REST endpoints for the community (planned). - Operational feedback on gnoland releases, including GNOROOT handling on prebuilt installs, pruning behaviour, and the genesis signature verification flag. - Sharing our Prometheus alert rules and Grafana dashboards for other gno.land operators. - Marketing and ecosystem work: written content, social, and co-marketing (planned). - Podcasts and community calls about gno.land, Gno, and validator operations (planned). - Joining GovDAO once we are eligible.