
Who says there's not much going on?!! 👩🔧🧑🔧
🚀 Cumulo weekly validator & infrastructure report: May 15–23
Over the last week, our team executed validator operations, upgrades, governance actions, and incident-aware infrastructure work across multiple networks, check what we did? 👀👇
☕ @EspressoSys / Mainnet: upgraded our mainnet node to 20260424, applying query and pruning optimizations and verifying healthy peer connectivity and consensus progression
📖 @StoryProtocol / Aeneid testnet: upgraded our validator to Story v1.7.0 (Seneca) ahead of the scheduled hardfork, with full sync and post-upgrade consensus validation
🛡️ @cosmoshub: voted NO WITH VETO on Prop #1037, a spam/scam proposal with no legitimate onchain purpose
🟣 @massachain / Mainnet: executed the mandatory MAIN.5.0 hard fork upgrade and rejoined the corrected network after the illegal minting fix
🔷 @GenLayer / Asimov: upgraded our validator to v0.5.11
💠 XRPL EVM by @Peersyst / Mainnet: voted YES on Prop #31 to recover expired IBC light clients for Injective and Elys
🟠 @cosmoshub Hub / Mainnet: executed the Gaia v27.3.0 upgrade at the scheduled height, covering validator, RPC, and backup infrastructure with post-upgrade verification
🔷 @GenLayer / Bradbury: upgraded our validator to v0.5.11
🐒 @monad / Testnet: upgraded our full node to v0.14.4 following the release window and verified full operational status
At Cumulo, validator operations are handled as production infrastructure work: upgrade readiness, governance monitoring, incident response, controlled execution, and post-upgrade verification across live environments.
That is also why we maintain our Activity Tracker: a public, JSON-backed operational log where we document upgrades, governance votes, incidents, and infrastructure actions in a transparent and auditable format.
📍Follow our activity here:
cumulo.pro/services/activ…

English













