Cardano activates Van Rossum hard fork, shifting mainnet to protocol v11
The upgrade is Cardano’s first hard fork proposed, debated, and ratified entirely through onchain governance voting.
Cardano activated the Van Rossum hard fork on July 18 at 21:44 UTC, moving mainnet to protocol version 11. The upgrade also marked the first time Cardano pushed a hard fork end-to-end through onchain governance rather than a founder-led coordination process.
Key Takeaways
- Van Rossum activated on July 18 at 21:44 UTC, moving Cardano mainnet to protocol version 11.
- Cardanoscan shows the protocol version flipped from v10 in epoch 643 to v11 in epoch 644.
- The hard fork was proposed, debated, and ratified entirely through Cardano’s onchain governance system rather than coordinated by Input Output.
- Voting support varied across governance bodies, with stake pool operators providing the narrowest approval margin at 53.02%.
Van Rossum Goes Live: Cardano Flips to Protocol v11
Cardano’s Van Rossum hard fork went live on July 18 at 21:44 UTC, shifting the network to protocol version 11.
Onchain confirmation tied the change to a clean epoch boundary. Cardanoscan data shows Cardano moved from protocol version 10 in epoch 643 to version 11 in epoch 644.
For traders, the immediate market relevance is less about a new feature headline and more about upgrade execution risk. A hard fork that lands on schedule and cleanly at an epoch transition tends to reduce near-term tail risk around chain instability, even if it does not create instant demand.
The First Fully Onchain-Governed Hard Fork: Who Signed Off and By How Much
Van Rossum was the first Cardano hard fork initiated, debated, and ratified entirely through the network’s onchain governance framework introduced in the Voltaire era. That is a structural shift in who controls protocol change, moving the process away from founder-led coordination and toward coalition-building across voting blocs.
Ratification required approvals across three bodies, and the margins were not uniform. Delegated representatives, elected by ADA holders to vote on their behalf, approved the proposal with 78.97% voting yes against a 60% threshold. The constitutional committee, which evaluates compliance with the Cardano Constitution rather than the proposal’s merits, voted 7/7 in favor where five votes were required.
Stake pool operators, the infrastructure operators producing blocks under Cardano’s proof-of-stake model, approved with 53.02% voting yes. That was the tightest margin of the three, and it matters because it hints at a future where operational readiness and political support can diverge.
The constitution also imposed a readiness gate: at least 85% of stake pools by active stake had to run compatible node software before ratification. Network telemetry showed roughly 93% of block production already on version 11 heading into activation, suggesting the network can be technically prepared even when governance support is less overwhelming.
What v11 Changes for Plutus and the Ledger — and What Stays the Same for ADA Transfers
Protocol version 11 is described as an intra-era hard fork, meaning it stays within Cardano’s current era and does not change the structure of transactions. That design choice reduces ecosystem-wide upgrade friction.
For everyday ADA transfers, there were no visible changes cited: transactions work the same way, wallets do not need updating, and the fee to send ADA is unchanged. The near-term impact is therefore concentrated in developer tooling and application economics, not in wallet UX.
On the smart contract side, v11 adds capabilities to Plutus by unifying built-in functions across Plutus’s three versions so older applications can access newer features. The upgrade also tightens ledger validation rules, including preventing two stake pools from reusing the same cryptographic identity key.
While the fork is positioned as lowering smart contract execution costs via Plutus cost model enhancements, the packet provides no quantified estimate of the reduction. It also notes the savings are not automatic because developers must rebuild contracts to capture them, leaving the timing of real fee relief as an adoption question rather than a protocol guarantee.
Roadmap Context: v11 as Groundwork for Dijkstra and Ouroboros Leios
Input Output linked Van Rossum directly to the next roadmap step in a development report, writing: "As well as Plutus improvements and Plutus Cost Model enhancements, this upgrade lays the foundation for the next upgrade, the Dijkstra era hard fork, which will introduce Ouroboros Leios to Cardano,"
Ouroboros Leios is described as a scaling proposal for Cardano’s proof-of-stake consensus model, expected later in 2026, aimed at sharply increasing transactions per second without weakening security guarantees. Van Rossum is framed as both technical groundwork and a governance precedent for that future upgrade.
The fork’s name also signals the governance emphasis. It was named for Max van Rossem, a Cardano governance contributor who helped shape the network’s constitution and died in October 2025.
Governance Decentralization Becomes the New Variable for ADA Traders
The governance shift is the durable change. With Van Rossum, Cardano demonstrated it can upgrade itself by vote, which can reprice “upgrade risk” from engineering execution to political coordination.
The threshold that matters is whether future hard forks can clear all three approval paths with less friction than this one. Delegated representatives and the constitutional committee delivered decisive margins, but stake pool operators only narrowly cleared majority support at 53.02%. If that pattern persists, the setup starts to look structural rather than narrative-driven: high technical readiness, but a governance process where timelines hinge on coalition-building.
The real test is whether developers move quickly enough to rebuild and redeploy contracts to realize Plutus cost-model savings, since the packet makes clear those savings are not automatic. Traders also need concrete milestones for the Dijkstra era hard fork and Ouroboros Leios, which are described as expected later in 2026 but without firm dates.
If post-upgrade telemetry and incident reporting continue to show stable block production after the epoch 643 to 644 transition, the market can treat Van Rossum as a clean governance execution proof point. What would make this development matter in practical terms is a repeatable onchain upgrade process that delivers Leios-era throughput without governance gridlock.
