Cardano Activates Van Rossem PV11 on Preview as Hard Fork Testing Enters Execution Phase

Cardano’s Van Rossem hard fork has moved from governance procedure to live testnet execution, with Protocol Version 11 now active on the Preview network.

The difference is important. Earlier coverage focused on the PV11 governance action entering the Preview process. This stage is no longer only about whether the action can move through governance. It is about how the upgrade behaves once node software, DB Sync, SPO infrastructure and developer tooling begin supporting it under live testnet conditions.

Van Rossem is not designed to move Cardano into a new ledger era. Cardano remains in the Conway era, while PV11 introduces a targeted set of protocol improvements through an intra-era hard fork. That makes the upgrade relevant for a different reason: it tests whether Cardano can deliver meaningful protocol changes without forcing the ecosystem through the heavier operational burden of a full era transition.

For builders and infrastructure teams, this is where the upgrade becomes practical. PV11 is no longer just a proposal waiting inside the governance process. It is now active protocol behavior on Preview, and the software stack around Cardano has to prove that it can absorb the change cleanly before the process advances toward PreProd and, later, mainnet.

Cardano PV11 Moves From Governance Action to Preview Testing

The Van Rossem hard fork is named in honor of Max van Rossem, a long-time Cardano community contributor and governance participant. But the immediate importance of this stage is operational, not symbolic.

Preview is the first environment where the upgrade can be tested under network conditions before broader rollout. Intersect previously outlined a phased path for the hard fork, with Preview first, PreProd expected roughly two weeks later and a mainnet hard fork submission targeted for May 29, 2026. That staged approach gives the ecosystem time to detect issues, validate tooling and coordinate infrastructure before any mainnet decision.

This matters because PV11 depends on multiple parts of the Cardano stack moving together. Stake pool operators need compatible node software. Indexing infrastructure needs DB Sync support. dApp teams need time to test scripts and tooling. Wallets, explorers and backend services also need confidence that the upgrade does not create unexpected behavior in the systems they depend on.

The official cardano-node 11.0.1 release is central to that process. It is the first node release to support the PV11 intra-era hard fork, enabling the upgrade to protocol version 11 once the relevant governance action has been voted on by SPOs, DReps and the Constitutional Committee, and enacted on-chain.

That makes Preview testing more than a technical checkpoint. It is the first stage where governance approval, release engineering and ecosystem readiness have to meet in practice.

Van Rossem PV11 Targets Plutus and Cardano Infrastructure

PV11 is a focused protocol upgrade. It does not change Cardano’s transaction shape and it does not move the ledger into a new era. Its importance sits in targeted improvements to Plutus performance, ledger consistency and node-level security.

For developers, the most visible area is Plutus. Intersect’s PV11 proposal outlined several Plutus upgrades, including broader availability of built-in functions across Plutus V1, V2 and V3, case expressions for built-in types, and new built-ins connected to CIPs such as CIP-0109, CIP-0132, CIP-0133, CIP-0138 and CIP-0153.

In practical terms, the goal is to make Cardano’s smart contract environment more consistent and more efficient. Existing Plutus V1 and V2 scripts can benefit from broader built-in function availability, while new primitives improve what developers can express on-chain. Intersect has described these changes as increasing script performance, reducing execution cost and expanding what builders can accomplish in Plutus.

PV11 also includes ledger and node-level changes. These include VRF key uniqueness enforcement, revised reference input rules for Plutus V1 and V2, clearer predicate handling and improved reporting around protocol parameter hash mismatches. These are not headline features for everyday users, but they matter for the systems that keep the network predictable and easier to operate.

DB Sync is another key part of the rollout. The official cardano-db-sync 13.7.0.5 release supports node version 11.0.1 and the PV11 intra-era hard fork.

That matters because DB Sync is used by infrastructure that reads and indexes Cardano chain data, including explorers, analytics platforms, backend services and applications that depend on reliable historical and current network data.

PV11 should therefore not be judged only by what appears on the surface. Much of the upgrade is about making Cardano easier to maintain, easier to index, safer to operate and more capable for Plutus-based applications.

Why Preview Enactment Matters Before Cardano Mainnet

Preview activation does not mean PV11 is ready for mainnet. It means the hard fork has entered the stage where assumptions must be tested against software, infrastructure and real testnet behavior.

That is the value of this phase. If problems appear, they can be found before the upgrade moves closer to mainnet. If the process runs cleanly, Cardano gains stronger evidence that its intra-era hard fork model can support meaningful protocol upgrades without requiring a full era transition each time the network needs targeted improvements.

For SPOs, the message is straightforward: node readiness matters. For dApp teams, Preview is the time to test compatibility, especially where tools rely on fixed cost models, protocol parameters or assumptions about Plutus behavior. Intersect has already noted that some previous Preview issues were linked to tooling using hardcoded parameters, with fixes in progress across affected developer tooling.

For Cardano’s broader roadmap, PV11 is not a marketing event. It is a coordination test. Governance has to approve the path, release engineering has to deliver the software, infrastructure providers have to upgrade, and developers have to confirm that applications behave as expected.

That is what makes this phase important. PV11 is no longer a proposal waiting inside the governance process. It is now a live test of whether Cardano’s operators, tooling and application layer can move together before the upgrade reaches mainnet.