Hypha Quarterly Report: 2025-Q2

Context Proposal 985 ratified Hypha as the Hub’s testnet and mainnet operations team for 2025, with a budget of 650k from the community pool. This continued Hypha’s role as a community-funded team, carrying on our work from 2024. Our mandate this year is to steward the Hub’s testnet, train validators, coordinate mainnet upgrades, provide ICS support for new and existing consumer chains, and work closely with the Interchain Labs team. This report summarizes our work throughout 2025-Q2 and plans for the coming quarter, per our commitment to transparency reporting on work performed with community-disbursed funds. You can give us feedback on our work via our form here . Highlights Reduced governance voting period to reduce need for emergency coordination • The Hub has had six emergency upgrades in the last six months, many of which have required a chain halt faster than the existing governance cadence can accommodate • Coordinated chain halts without using governance are demanding and risky for validators and the Hub as a whole - any time a chain halts, there is the risk that something will go wrong and it will not start again • There are many potential solutions to the…

Excerpt (1199 of 9497 characters). Read the whole post on the forum ↗

Thanks.
About FORGE,Are there any improvements planned? We notice that Forge has disappeared from the Cosmos website and been replaced by “solution for institutions”? A few words on that?
Are new chains in the process of joining ICS (Intento for example)?
The development of Mesh Security has been granted and retained. Are you on the case?

Hello! Thanks for sharing!

Thanks for the report Lexa

Forge is/was a core part of Interchain Security as the product vision for the Hub and was the dev responsibility of the last product team.

My assumption (not official, not speaking on behalf of either Hypha or ICL) is simply that Forge was Informal’s project to support the product vision they put forward, and further developing and promoting that product vision isn’t on the roadmap going forward.

Hypha specifically is not developing/maintaining Forge and we are not working with any new chains looking to onboard through ICS, though we are still supporting Elys and offer support to any of our existing consumer chains. Not sure about Mesh Security - that wasn’t part of our mandate as a maintenance team.

Excellent report! Reading through this report, especially the sections on emergency upgrades, halt recovery drills, and the v23.1.1 incident, a clear pattern emerges. Operational readiness on the Hub has significantly improved: validators are trained, rollback procedures are exercised, upgrade coordination is tighter, and response times are faster. This work clearly reduces risk at the moment of failure. However, once an incident is over and the ecosystem moves into retrospectives or governance discussions, there is still no reproducible way to independently verify what exactly happened at the validator and consensus level. In practice, post-incident understanding still depends on dashboards, RPC views, and trusted summaries, which can differ while remaining internally consistent. This creates ambiguity when questions of responsibility, behavior, or decision-making arise - even when all parties are acting in good faith. That suggests the remaining gap is not operational, but architectural: the absence of a deterministic verification layer that turns public chain data into reproducible evidence that anyone can independently re-check after the fact. Without such a layer,…

Excerpt (1199 of 1341 characters). Read the whole post on the forum ↗