Cardano's van Rossem hard fork clears governance vote, enactment set for July 18

Cardano's next network upgrade, the van Rossem hard fork, has passed its governance stage. Intersect, the member-based body that stewards Cardano's development, said the hard fork initiation action was ratified at the epoch boundary on July 13, 2026 at 21:45 UTC. Enactment — the point at which the new rules actually take effect on-chain — is scheduled for July 18, 2026 at 21:45 UTC.

Ratification came through Cardano's on-chain governance, which requires separate approval from three groups. Per the voting tally Intersect published, Delegated Representatives (DReps) approved with 77.63% against a 60% threshold; Stake Pool Operators (SPOs) approved with 52.7% against a 51% threshold; and the Constitutional Committee (CC) recorded six of seven members voting in favor, with one member not voting. The Cardano Foundation reposted the results on July 14, adding "a final call to action" for operators who have not yet updated their infrastructure to a hard-fork-compatible node version to do so.

Neither Intersect nor the Foundation detailed the specific protocol changes van Rossem introduces in the posts here; that information sits in Cardano's node release notes and governance action, which weren't reproduced.

Key facts

• Ratified: July 13, 2026, 21:45 UTC, at the epoch boundary (Intersect, @IntersectMBO).
• Enactment scheduled: July 18, 2026, 21:45 UTC (Intersect; Cardano Foundation, @Cardano_CF).
• DRep vote: 77.63% in favor vs. 60% threshold (Intersect).
• SPO vote: 52.7% in favor vs. 51% threshold (Intersect).
• Constitutional Committee: 6 in favor, 1 did not vote (Intersect).
• Operator action: update nodes to a hard-fork-compatible version before enactment (Cardano Foundation).

The real-world read

The headline number to watch isn't the lopsided DRep approval — it's the stake-pool vote. SPOs cleared the bar by 52.7% to a 51% threshold, a margin of under two points. Intersect's figures don't break out participation or how much stake abstained, so the tally alone doesn't tell you whether the closeness reflects genuine division among operators or simply low turnout. Either way, it's the tightest of the three gates, and it's the group whose nodes have to be upgraded for the fork to go smoothly.

That's also why both posts lean on the "update your infrastructure now" message. A hard fork that ratifies on-chain still depends on operators running compatible software by enactment; nodes that don't upgrade risk falling off the network's consensus. Intersect's own sign-off — "no other governance actions were harmed during this ratification" — is a light touch on a real point: this action moved through the same on-chain process as any other, and cleared it.

Worth noting on sourcing: both accounts here are Cardano's own institutions describing Cardano's own upgrade. The vote counts are on-chain and independently checkable, but the "final call to action" framing is the project's, not a neutral party's.

Opinion, and whose

Neither Intersect nor the Cardano Foundation offered a forecast of network impact or price effect in these posts, and none is asserted here. The only implicit claim — that unpatched nodes should upgrade promptly — comes from the Cardano Foundation, an interested party stewarding the network.

Sources

• Intersect (@IntersectMBO), Nitter, July 13, 2026 — primary governance body; provided the ratification and enactment timestamps and the full DRep/SPO/CC vote tally. Project-run account.
• Cardano Foundation (@Cardano_CF), Nitter, July 14, 2026 — reposted and confirmed the timeline; added the operator upgrade call. Project-affiliated account, not independent.

This is news, not financial advice.