Cumulo

🚀 Celestia Labs acquires @sovereignxyz Labs, marking a fundamental evolution in its strategy. Celestia is expanding from a Layer 1 focused on blockspace into a full-stack blockchain infrastructure provider, covering: 🔹 Data availability 🔹 Execution 🔹 Application layer @celestia moves from selling only the foundation to offering the complete chain, designed and built end to end. A major new chapter starts for Celestia 🌌⚡and from Cumulo, as Celestia validators since its earliest testnet stages, we will continue supporting the network through every new challenge.

We’ve published a new post on the @cosmos Forum sharing our current Cumulo IBC Relayer Infrastructure ⚛️ At Cumulo, we run IBC relayer infrastructure alongside our validator operations, covering multiple paths across mainnet and testnet. Current setup: 🔁 22 active IBC channels 🌐 8 networks ⚙️ Hermes v1.13.2 📡 Live monitoring dashboard 📊 On-chain relay activity tracker 📖 Public technical documentation The setup includes paths across @celestia , @cosmoshub Hub, XRPL EVM by @Peersyst , @injective , @osmosis , @sedaprotocol and @dymension . We also directly opened two IBC channels: 🔹 Celestia mainnet <> Cosmos Hub 🔹 Celestia mainnet <> XRPL EVM Both registered in the Cosmos chain-registry. The goal is simple: make our relayer work more visible, monitorable and useful for validators, node operators and teams building across the Interchain. Full post on the Cosmos Forum 👇 forum.cosmos.network/t/cumulo-ibc-r…

🏛️ Internet Court is now live. Led by the @GenLayer Foundation and backed by a consortium of 27 companies, it brings the fragmented agentic commerce stack into one open, interoperable flow. 🤝 Identity 💬 Negotiation 📜 Contracts 💸 Payments & escrow ⚙️ Execution ⚖️ Verification & disputes Any two AI agents can now structure a deal, secure funds, and agree in advance on what happens when things go wrong. At the core, @GenLayer provides the missing adjudication layer through decentralized AI-powered validator consensus. As a Genlayer validator, at Cumulo we’re proud to support the infrastructure providing the missing adjudication layer for agentic commerce. 🤝 🚀 Machine-speed commerce needs machine-speed adjudication.

⚡️ @Starknet v0.14.3 is now live on Mainnet A significant upgrade for builders, infrastructure providers, and validators: 🔹 Dynamic L2 gas pricing for more predictable fees 🔹 1.5-second block times to reduce network latency 🔹 Prover and verifier improvements supporting future privacy flows 🔹 BLAKE-based SNOS hashing, advancing Starknet’s path toward quantum resistance ⚠️ RPC 0.8 is now deprecated. Operators and developers should migrate to RPC 0.9 or 0.10.x. As an active Starknet validator, Cumulo continues monitoring the network through every protocol release. 🤝

🚀 Cumulo weekly validator & infrastructure report At Cumulo, we are taking on new challenges with the same excitement as always. Happy to work with projects that are building real solutions for real problems. That mindset is also reflected in our weekly activity, combining technical operations, incident response, deployments, and infrastructure evolution across multiple networks. 🟣 @dymension / mainnet: deployed new IBC relaying infrastructure, enabling paths with Celestia, Osmosis, and Cosmos Hub, using Hermes v1.13.2 with full client and channel verification 🟠 @cosmoshub / mainnet: voted YES on Prop #1044 for the Gaia v27.5.0 upgrade 🟠 @cosmos Hub / mainnet: migrated public RPC infrastructure to a new server, reconfiguring endpoints, reverse proxy, SSL, and supporting services 🌌 @celestia / Mocha testnet: migrated validator and RPC nodes from goleveldb to pebbledb ahead of the v10 requirement 🟠 @cosmoshub / testnet: resolved a P2P connectivity incident on the RPC node, restoring block publication and normal synchronization 🍋 @LimoDev / testnet: deployed and activated a new validator, synced via state-sync and brought to BOND_STATUS_BONDED 🔷 @GenLayer / Asimov testnet: investigated and resolved an internal validator process hang, restoring metrics, logs, and RPC connectivity 🍋 @LimoDev / testnet: voted YES on Prop #2 to enable real gas fees and activate validator fee economics 🐒 @monad / testnet: upgraded our full node to v0.15.0, applying a database schema migration and verifying all services active 🟢 @wardenprotocol / mainnet: quickly recovered the validator after a temporary jail by submitting the unjail transaction and resuming block production without slashing 🍋 @LimoDev / testnet: executed the validator and public RPC upgrade to limonatad v0.2.0 at the scheduled height, with full post-upgrade verification ⚡ @Starknet / mainnet: detected and corrected an attestation incident caused by insufficient balance on the operational address 💠 XRPL EVM by @Peersyst / testnet: voted YES on Prop #46 for the v11.0.0 software upgrade At Cumulo, we treat validation as production infrastructure work: deployments, upgrades, incident response, relaying, migrations, governance, and continuous operations. It is not just about keeping nodes online, but about building and running useful, resilient, and auditable systems for networks that keep evolving. That is why we maintain our Activity Tracker: a public, JSON-backed record where we continuously document upgrades, governance votes, incidents, deployments, and operational changes in a transparent and auditable format. 📍Follow our activity here: cumulo.pro/services/activ…

AI agents will increasingly transact, negotiate and make decisions autonomously. But what happens when they disagree? GenLayer is building the infrastructure to resolve those disputes through intelligent contracts capable of interpreting context and judging what is fair. A clear introduction to why this new adjudication layer matters and how it works 👇

🚀 Celestia v9 is now live on Mainnet The upgrade cuts block time from 6 seconds to 3 seconds ⚡ What this means: ✅ Faster confirmations ✅ More blockspace ✅ Better performance for networks publishing data to Celestia Cumulo participated in the upgrade as an active-set validator on @celestia, helping support a coordinated and secure network transition 🌌 A major step forward for the modular ecosystem. 🚀

🔐 XRPL EVM v11 is coming, and this is an important one. From Cumulo, as validators on XRPL EVM, we see this upgrade as a strong step toward a safer and more resilient network. Not every upgrade needs to bring visible new features. Sometimes the most valuable work happens under the hood: reducing risk, strengthening validator operations, and improving the security of the infrastructure that supports real activity. With v11, @Peersyst is focusing on: ✅ Longer unbonding period: from 1 day to 7 days ✅ ICA host disabled to reduce unnecessary attack surface ✅ Outbound IBC rate limits for safer cross-chain flows ✅ PoA validator management hardening ✅ Recovery of stranded Elys escrow funds ✅ Additional security fixes and AI-assisted auditing For validators and infrastructure providers, this kind of release matters. It reinforces the foundations that developers, institutions, users, and node operators depend on every day. At Cumulo, we welcome this security-first approach and will follow the testnet proposal closely before mainnet rollout. Stronger infrastructure. Safer connectivity. More resilient XRPL EVM. 🌊 For more details, check here 👇

@nodesync_top @_gnoland You're welcome 😄. We're happy that the resources we generate are useful to the community. 🤝

@Cumulo_pro Thanks for sharing your public RPC for Test13 @_gnoland ! We've added it to our community dashboard. Appreciate your contribution! 🙌

🚀 Cumulo weekly validator & infrastructure report While our servers run in data centers where summer heat does not hit nearly as hard, a special mention goes to our node operators, who keep performing at full capacity despite the temperatures. The best way to start the week is still by reviewing all the technical work delivered in the previous one. 🟠 @cosmoshub / testnet: voted YES on Prop #316 to recover an expired IBC light client and restore the active mocha-4 ↔ provider relay channel ☕ @EspressoSys / Decaf testnet: configured a public HTTPS endpoint and updated the validator metadata URI on-chain ☕ @EspressoSys / mainnet: fixed peer configuration, deployed a public endpoint via nginx, and recovered the Weekly Score to 100/100 ☕ @EspressoSys / Decaf testnet: resolved a full validator outage caused by an L1 provider policy change by migrating the endpoint to Alchemy Sepolia and restoring normal operation 🔁 @cosmos / mainnet: expanded our Hermes IBC relayer from 15 to 19 active channels after a full path audit and updated the dashboard to reflect the new state 🟠 @cosmos Hub / testnet: submitted Prop #316 to recover the expired client affecting our IBC testing infrastructure 🟠 @cosmos Hub / testnet: voted YES on Prop #317 for the Gaia v27.5.0-rc0 upgrade 🟠 @cosmoshub / testnet: executed the provider node upgrade to Gaia v27.5.0-rc0 during Testnet Tuesday, with validator, RPC, and backup infrastructure verified without incidents 🟠 @cosmos Hub / testnet: voted YES on Prop #319 to enable burn_vote_quorum for future proposals that fail to reach quorum 🟠 @cosmoshub / mainnet: voted YES on Prop #1043 to fund the public testnet program ⚡ @Starknet / mainnet: voted YES on Prop #15 for the updated v0.14.3 upgrade scope ⚡ @Starknet / mainnet + testnet: upgraded our RPC nodes to Juno v0.16.4, adding pruning support and reducing database size 🧪 @_gnoland / Test13: deployed a full validator node, registered the validator profile on-chain, and initiated the process to join the active set 🧪 @_gnoland / Test13: deployed a public RPC node 🧪 @_gnoland / Test13: deployed a public snapshot service with automatic rotation and HTTPS access ☕ @EspressoSys / Decaf testnet: upgraded the node to release 20260624, including reward distribution changes, light-client catchup, and database migration For us, validation is not just uptime: it is disciplined infrastructure operations across upgrades, incidents, and day-to-day maintenance. That is why we maintain our Activity Tracker: a public, JSON-backed record where we continuously document upgrades, governance votes, incidents, deployments, and operational changes in a transparent and auditable format. 📍Follow our activity here: cumulo.pro/services/activ…

✅ Signal complete! Celestia v9 upgrade is locked in The required 83.33% voting power threshold has been reached, meaning the v9 upgrade process is now officially locked in for @celestia mainnet. The upgrade to app version 9 is scheduled at block #11771698, approximately 7 days from now. This is a major step for the network: faster blocks are coming to @celestia mainnet, with block times moving to 3 seconds ⚡ From Cumulo, we’re tracking the countdown in real time so validators, developers, and the community can follow the upgrade as it approaches: ⏳ Countdown to block #11771698: 👉 #block-11771698" target="_blank" rel="nofollow noopener">cumulo.pro/services/celes… The next Celestia upgrade is on the way 🌌

it's final countdown scientists @RoboMcGobo will soon be grading your hackathon submissions

🚀 Cumulo weekly validator & infrastructure report Summer may be kicking in on this side, but validator infrastructure doesn´t know about seasons: the best way to start the week is still by checking the technical work done in the last one. Even when the market feels quieter on the surface, things remain very active under the hood. 🌌 @celestia / mainnet: submitted the on-chain signal for the v9 upgrade and continued tracking the quorum process for activation 🟡 @AvailProject / mainnet: migrated our validator to a new host, including session key rotation and full verification of block signing on the new environment 🟢 @quicksilverzone / mainnet: monitored the chain halt triggered by the team as an emergency response to an active exploit 🌌 @celestia / Mocha testnet: upgraded validator, RPC, and consensus nodes to celestia-app v9.0.4-mocha 🟠 @cosmos / testnet: voted YES on Prop #302, a text proposal on testnet 🌌 @celestia / Mocha testnet: upgraded the bridge node to celestia-node v0.31.3-mocha 🌌 @celestia / mainnet: upgraded the bridge node to celestia-node v0.31.3 🟠 @cosmoshub / testnet: voted YES on Prop #305 regarding funding for the public testnet program ⚡ @Starknet / mainnet + testnet: upgraded our RPC nodes to Juno v0.16.3, the new minimum required version ahead of the v0.14.3 protocol upgrade At Cumulo, we treat validation as production infrastructure work: upgrade readiness, controlled migrations, governance tracking, incident response, and continuous operational verification. It is not just about keeping nodes online, but about operating critical infrastructure with technical judgment, discipline, and traceability. That is why we maintain our Activity Tracker: a public, JSON-backed record where we continuously document upgrades, governance votes, incidents, and operational changes in a transparent and auditable format. 📍Follow our activity here: cumulo.pro/services/activ…

🚀 Celestia Mainnet v9 signaling is now live! The Celestia Mocha testnet has a new major version coming, and it brings a very important change: blocks will move to 3-second block times. A huge speed boost for the network ⚡ To activate the upgrade, validators need to signal readiness through a MsgSignalVersion transaction. Current status: 🟢 57 / 78 validators signaling 🗳️ 85.03% voting power 🎯 Required threshold: 83.33% ✅ Threshold reached ⚙️ Target version: v9 Once more than 83.33% of voting power has signaled, a 2-day delay begins before the upgrade executes. At Cumulo, we have activated our Upgrade Signal Tracker for Celestia so the community can follow the process in real time: 👉 cumulo.pro/services/celes… Faster blocks are coming to Mocha 🌌

🚀 Cumulo weekly validator & infrastructure report The best way to start the week is by checking the work completed in the last one: a necessary reset that helps set the tone for everything ahead. Although in our case, weekends are just another part of the operational cycle. 💠 XRPL EVM by @Peersyst / testnet: voted YES on Prop #44 to add a new validator to the network ⚡ @Starknet / mainnet: voted YES on the v0.14.3 upgrade proposal, which includes relevant changes to fee dynamics and block frequency ⚡ @Starknet / mainnet + testnet: upgraded our infrastructure first to Juno v0.16.1 and then to Juno v0.16.2, preparing the stack for the upcoming network upgrade 🟠 @cosmoshub / mainnet: executed the Gaia v27.4.0 upgrade at the scheduled height, with full post-upgrade validation ☕ @EspressoSys / Decaf testnet: upgraded our node to 20260605 and verified normal operation without incidents ☕ @espressoFNDN / mainnet: upgraded our infrastructure to 20260605 and confirmed stable post-upgrade operation 🌌 @celestia / Mocha testnet: upgraded the bridge node to celestia-node v0.31.2-mocha, adding improved observability and more fault-tolerant block ingestion 📖 @StoryProtocol / Aeneid testnet: decommissioned the validator after the active set reduction and coordinated the unstake process with the Story team 📖 @StoryProtocol / mainnet: decommissioned our validator infrastructure following the Seneca hardfork and completed an orderly service shutdown At Cumulo, we treat validation as production infrastructure work: upgrade readiness, governance monitoring, controlled execution, lifecycle management, and operational verification. We do not just deploy and upgrade nodes: we also manage migrations, transitions, and infrastructure retirement with the same technical rigor applied to live production environments. That is why we maintain our Activity Tracker: a public, JSON-backed record where we continuously document upgrades, governance votes, operational changes, and infrastructure decisions in a transparent and auditable format. 📍Follow our activity here: cumulo.pro/services/activ…

@dferrersan just shipped coro, a DA library that lets you launch a Commonware chain on Celestia in a day. No validator set needed. One sequencer handles ordering, @celestia handles data availability. That's it. The result: 20ms block times 10x faster than alto + simplex, without the weeks of coordination and infrastructure overhead that launching a chain normally requires.