Correcting the sequence

The automated Simba signal feed elevated a July 8 merge in Intersect's governance-actions repository as an early indication that the van Rossem hard fork was being staged. That framing was behind the public governance record.

Intersect's upgrade overview says the mainnet hard-fork initiation action had been approved for submission in epoch 637, with June 16 as the proposed submission date. Its July 3 weekly update was already reporting live voting progress.

The July 3 governance snapshot

At the time of Intersect's update, DRep support stood at 66.60% against a 60% threshold. SPO support was 43.37% against 51%, and the Constitutional Committee count was one constitutional vote with six members yet to vote; five were required.

Intersect also reported that 89% of block production was on node version 11 in epoch 640 and that its exchange and dApp readiness thresholds had been met. These numbers are a dated snapshot, not a substitute for checking the live action before making an operational decision.

Why this matters to operators

Cardano upgrades now combine technical readiness with explicit on-chain governance. Repository commits remain useful receipts, but they answer a different question: what changed in the supporting materials, not whether an action has been submitted, ratified, or enacted.

For stake-pool operators, the practical work is to verify node readiness, inspect the action itself, and participate in the SPO vote. For publishers, the lesson is equally concrete: join code-level signals to live governance state before calling them breaking news.

What to watch

Check the live GovTool action for current voting and status; use the dated Intersect updates for sequence and context, not as a live tally.

Receipts

Sources

  1. 1
  2. 2
  3. 3
  4. 4

Published after human review of the linked sources. Analysis is informational and is not financial advice.