Cardano's next upgrade is now up for approval. The waiting window is the real test.
Van Rossem is less about one upgrade and more about whether Cardano's new governance path can ship on a real calendar.

CryptoVibe Desk · cardano · governance · hard-fork

- →Cardano submitted the van Rossem upgrade action during epoch 637 after working-group and steering-committee checks cleared readiness.
- →The upgrade is the first real hard fork process under post-Chang governance, without IOG acting as the single coordinator.
- →Watch the June 23 to July 18 ratification window because delay now becomes a visible governance cost.
- Hard fork → A hard fork is a planned software change that network operators must adopt for the chain to keep moving together.
- Epoch → An epoch is a fixed block of time Cardano uses to organize rewards, voting, and network operations.
- Node → A node is software that checks blocks, follows network rules, and helps keep the blockchain running.
- Hydra → Hydra is Cardano's scaling system for moving some activity off the main chain while keeping settlement tied to Cardano.
Cardano's van Rossem upgrade is now in governance's hands.
The hard fork action hit Mainnet during epoch 637 on June 16. U.Today said that followed a positive go/no-go assessment from the Hard Fork Working Group on June 15. The Technical Steering Committee then ratified readiness on June 16.
The mechanism matters more than the name. Van Rossem is an intra-era upgrade, not a full era jump. But it is moving through the governance path Cardano set up after Chang. That means IOG is no longer the only coordinator for a protocol upgrade.
As of June 20, U.Today reported that 62% of Cardano nodes self-reported v11.0.1 through PoolTool. The same report showed 81% of current epoch block production on Protocol Version 11. Cexplorer data cited in the report put v11 nodes at 89% of block production over the prior five days.
Those numbers say the operator side is mostly ready. They don't prove governance is fast. The earliest possible ratification date is June 23, per the briefed timeline. The earliest enactment date is June 28.
And that's the catch. The window can stretch much longer. Ratification can run as far as July 18, with enactment pushed to July 23. If you're an ADA holder watching upgrades as a sign of execution, that spread is the only number that matters.
This is a coordination problem, not a code problem. Single-team chains hide this inside a release manager and a Telegram room. Cardano is trying to expose the process, with committees, readiness criteria, and an on-chain action.
The tradeoff is visibility over speed. You can inspect who signed off and when. You also inherit the waiting room. That is cleaner governance, but it is still latency.
Hydra 2.2.0 landed in the same week, with Partial Fanout removing the old UTxO-per-head cap. That is useful engineering work, but it is not the main test here. Van Rossem is testing whether Cardano can upgrade predictably when governance is part of the runtime.
Read the calendar, not the thread. If van Rossem lands near June 28, post-Chang governance gets a serious proof point. If it drifts toward late July, Cardano will have proven decentralization can coordinate, but not yet that it can move cleanly.
Intersect is right to run van Rossem through the full post-Chang process because predictable upgrades matter more than IOG-era speed.
Before July 18, watch whether van Rossem reaches ratification with v11 block production still above 85% and no reset to the governance action timeline.
Primary links and supporting reads used by the desk for this story.
Forward this.











