- Cardano’s Van Rossem hard fork was enacted in epoch 644, with GovTool and Koios showing protocol version 11.0.
- The scheduled epoch boundary was 21:44:51 UTC, while the first checked block and GovTool enacted_time were 21:53:13 UTC.
- Koios showed 13 checked epoch-644 blocks at protocol 11.0, with continuity limited to that sequence.
July 18, 2026 (Crypto-News.Net) – Cardano’s Van Rossem hard fork was enacted in epoch 644, with governance and network data showing mainnet running protocol version 11.0 after the scheduled July 18 epoch boundary.
Direct GovTool Outcomes data showed the hard-fork initiation action was enacted in epoch 644 with a target of major version 11 and minor version 0, while Koios epoch-644 parameters showed the active protocol version as 11.0.
The timing record has two separate points. According to Intersect’s upgrade page, Intersect, Cardano’s member-based ecosystem organization coordinating the upgrade, scheduled the epoch boundary for 21:44:51 UTC on July 18. Koios epoch data placed the first checked epoch-644 block at 21:53:13 UTC, and GovTool listed the same time as enacted_time. That distinction separates the planned epoch start from the first checked post-fork block timestamp in the data.
Koios block data showed 13 checked epoch-644 blocks from height 13695759 through 13695771. The sequence carried protocol 11.0 throughout and showed matching parent hashes between consecutive blocks, linking each block to its predecessor. That supports continuity only within the checked set.
What the Van Rossem hard fork changed
According to Intersect’s upgrade overview, protocol version 11 adds Plutus smart-contract changes along with ledger and node updates. GovTool and Koios provide the post-event basis for the epoch-644 status and active protocol version reported here.
Cardano’s June background post described Van Rossem as part of a rollout that included governance actions and testing on Preview and Preprod before mainnet. The mainnet status in this story comes from the later GovTool and Koios checks after the epoch change.
The upgrade is a hard fork, a coordinated change to protocol rules. Crypto-News.Net’s hard fork mechanics explainer covers the general process, while this story reports the Cardano-specific post-event status from GovTool and Koios.
User guidance
Intersect’s upgrade FAQ said Van Rossem does not require token migration. The FAQ also said token holders have no specific action beyond keeping wallets and tools updated.
The status claim covers governance enactment, active protocol version 11.0 in epoch 644 and continuity for the checked 13-block Koios sequence. It does not cover exchange, wallet, operator or user experience across the network.
Reporting by Zoran Spirkovski; Editing by Zoran Spirkovski
Sources
GovTool Outcomes – Owner: Cardano GovTool Outcomes. Supported claim: hard-fork initiation action identity, enacted_epoch 644, enacted_time 21:53:13 UTC and target protocol version 11.0. URL: https://outcomes.mainnet.gov.tools/governance-actions/fdd468da5cc4ac8431dcd7e2b3211666c73bc229f85879469f67f1d9d51d344d?index=0
Koios epoch parameters – Owner: Koios. Supported claim: active epoch-644 protocol_major 11 and protocol_minor 0. URL: https://api.koios.rest/api/v1/epoch_params?_epoch_no=644
Intersect upgrade page – Owner: Intersect. Supported claim: Van Rossem schedule, scheduled epoch-boundary time and Intersect’s coordinating role. URL: https://www.intersectmbo.org/news/cardano-upgrade-van-rossem-hard-fork
Koios epoch info – Owner: Koios. Supported claim: epoch 644 start_time 21:44:51 UTC and first_block_time 21:53:13 UTC. URL: https://api.koios.rest/api/v1/epoch_info?_epoch_no=644
Koios block_info – Owner: Koios. Supported claim: checked 13-block epoch-644 sequence, protocol 11.0 on those blocks and parent-hash continuity within that set. URL: https://api.koios.rest/api/v1/block_info
Intersect upgrade overview – Owner: Intersect. Supported claim: source-described protocol version 11 scope, including Plutus, ledger and node changes. URL: https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/van-rossem-upgrade-overview.md
Cardano background post – Owner: Cardano. Supported claim: Van Rossem rollout background, governance-action context and Preview and Preprod testing context before mainnet. URL: https://cardano.org/news/2026-06-16-van-rossem-hard-fork/
Intersect upgrade FAQ – Owner: Intersect. Supported claim: no-token-migration guidance and user-action boundary for wallets and tools. URL: https://cardanoupgrades.docs.intersectmbo.org/van-rossem-upgrade/van-rossem-upgrade-faq.md
