Cardano reached protocol version 11 on July 18 after its first major upgrade approved through onchain governance. The visible result is modest. ADA transfers, wallets and transaction formats work as before. The consequential change sits underneath: protocol upgrades now have a defined route from proposal to vote, ratification, software deployment and activation.
CoinDesk reported that the Van Rossem hard fork activated at 21:44 UTC on July 18, moving Cardano from protocol version 10 in epoch 643 to version 11 in epoch 644. The governance action had been ratified on July 13. DReps supported it by 78.97%, above a 60% threshold. All seven Constitutional Committee members found it compliant, where five approvals were required. Stake pool operators approved it by 53.02%, the narrowest of the three margins.
Those figures are the story. Not because 53.02% is a commanding mandate. It plainly is not. The number matters because it shows that Cardano’s operators can now express a view separate from the network’s founding developer, Input Output. Previous upgrades could be technically complex, heavily tested and widely coordinated. They were still, in practical terms, directed from the top. Van Rossem changed the route by which a change becomes a rule that every block producer must follow.
The hard fork is named for Max van Rossem, a Cardano governance contributor who helped shape the network’s constitution and died in October 2025. There is some symmetry in that. The first system-wide protocol change approved through the governance structure he helped build now carries his name.
For ADA holders, the difference today is mostly procedural. For node operators, application developers and anyone proposing the next hard fork, it is operational.
A protocol upgrade is now a governance action
A blockchain upgrade has two jobs. First, it must change the rules correctly. Second, it must persuade enough of the network to run those rules at the same time. Missing either job produces trouble. A proposal that passes a vote but lacks compatible node software is not an upgrade. It is an instruction nobody can safely execute. Software that exists but cannot clear governance is code waiting on a shelf.
Van Rossem connects those jobs.
The process begins with a protocol-change action. That is not simply a software release note or a developer’s roadmap item. It is a formal governance object that specifies a proposed change to the protocol and is submitted for consideration under Cardano’s governance rules. The action needs an anchor to documentation, a defined purpose and the information voters need to assess it. That sounds bureaucratic because it is. A chain should be bureaucratic before it is irreversible.
The proposal then goes to three constituencies with different responsibilities. DReps represent delegated ADA holders. The Constitutional Committee assesses whether an action complies with Cardano’s constitution. Stake pool operators, or SPOs, represent the people and organizations running the infrastructure that makes blocks and validates the chain.
This is deliberately not one-token, one-switch governance. DReps answer the representative question: do delegated holders support the action? The Constitutional Committee answers a narrower legal question: is it consistent with the constitution? SPOs answer the infrastructure question: are the operators responsible for block production prepared to accept the change?
Each role has a blind spot if used alone. Token voting can favor holders with no operational exposure. Operators can prefer stability even when the wider community supports a change. A constitutional body can determine procedural compliance without deciding whether a technical trade-off is wise. Cardano’s design puts those limitations in conversation rather than pretending any one group is the network.
The result is slower than a company deciding what ships. It is also more explicit about who bears the risk.
DReps vote with delegated ADA, not with a blank check
The delegated representative model is the political layer. ADA holders can delegate governance voting power to DReps, who publicly take positions on proposals. It is a practical response to a familiar problem. Most holders will not read ledger specifications, assess cryptographic primitives or inspect the operational effects of revised execution budgets. They may still want a say in who does.
Delegation does not remove concentration risk. Large holders can delegate large voting weight. Nor does it guarantee informed participation. A DRep can become a recognizable name without becoming a diligent reviewer. The mechanism does, however, create a clearer accountability path than informal social-media consensus or a founder’s announcement.
Van Rossem’s 78.97% DRep support cleared its threshold comfortably. That number should not be misread as 78.97% of every ADA holder personally studying the code. It is a measure of the delegated voting power that supported the action under the relevant rules. That is still meaningful. It is not the same thing as universal technical consent.
The more difficult test comes with changes that have visible winners and losers. Lower smart-contract costs are easy to frame as a benefit. Treasury spending, fee policy, staking incentives or changes that shift costs from one class of user to another will be harder. A governance system earns its reputation when the proposal is unpopular with somebody important.
The committee is a constitutional check, not a technical steering group
The Constitutional Committee is easy to misunderstand because its members also vote. Its job is not to decide whether a protocol idea is commercially attractive, whether Leios will produce the expected throughput or whether a developer prefers one programming interface to another. Its job is to determine whether the action fits Cardano’s constitutional rules.
That distinction matters. A committee that can veto any change it dislikes becomes a second development company. A committee that does only a compliance review can serve as a procedural safeguard without replacing elected or delegated judgment.
For Van Rossem, all seven committee members agreed that the action was constitutional. That unanimous result does not mean the upgrade was technically risk-free. It means the committee found no constitutional reason to block it.
This separation also changes the incentive for future proposals. Proponents cannot rely only on technical merit. They need a case that can survive constitutional scrutiny, persuade representatives and meet the practical concerns of operators. That may sound like friction. It is friction. In protocol governance, friction is often the product.
SPOs supply the last practical constraint
Stake pool operators do more than vote. They run the nodes that produce blocks. Their support therefore has a quality that a wallet vote does not: it is tied to the cost of deployment, monitoring, rollback planning and responding if things go wrong.
CoinDesk reported that the constitution required at least 85% of active stake to be running compatible node software before ratification. Network telemetry showed roughly 93% of block production on version 11 approaching activation. That prerequisite separates theoretical approval from deployable approval.
An operator must obtain the compatible node release, test its environment, update configuration and ensure its operational keys and systems remain secure. With Van Rossem, the upgrade also included a security change requiring each stake pool to use a unique cryptographic key, according to Decrypt’s report. That is the unglamorous side of governance. A vote does not patch a server.
The SPO vote was close. At 53.02%, it passed, but it showed a genuine gap between broad DRep approval and operator comfort. That gap is useful information. It tells future proposers that code quality, release timing and operational communication are not implementation details to be solved after governance. They are part of the governance case.
What version 11 changes, and what it does not
Van Rossem is an intra-era upgrade. It does not redesign Cardano’s basic transaction experience or split everyday users into a new asset and an old asset. ADA remains ADA. Wallet users do not need to learn a different payment flow. The transaction shape remains the same, and ordinary transfer fees are unchanged.
The immediate technical gains sit in Plutus, Cardano’s smart-contract environment. The upgrade adjusts the Plutus cost model, the rules used to calculate the computational resources and fees for executing scripts. A lower or more accurate execution cost can make a contract interaction cheaper. It does not make every app cheaper by the same percentage, and it does not promise that applications will pass savings through to users.
Decrypt reported that version 11 adds constant-time array indexing, native Value handling, faster list traversal and new cryptographic primitives across Plutus V1, V2 and V3. Those are builder-facing tools. Their importance depends on what developers actually deploy with them.
A Minswap contract written in an older Plutus version can now, in principle, access built-ins once reserved for newer versions, potentially reducing execution work. That is a potential benefit, not a published fee measurement. None of that follows automatically from the hard fork. Code needs to be rewritten, tested and deployed. Liquidity needs to arrive. Users need a reason to transact.
That is the distinction between live and used. Van Rossem is live. The cheaper execution environment is available. Whether the Cardano application layer uses it enough to change fees, volumes or product design is a separate question.
Leios is the next claim, not the delivered result
The other purpose of Van Rossem is preparation for Ouroboros Leios. Cointelegraph reported that Input Output described the upgrade as groundwork for the Dijkstra era hard fork, which is intended to introduce Leios.
Leios is a scaling proposal for Cardano’s Ouroboros proof-of-stake consensus. Its aim is to increase throughput by separating some of the work involved in producing and validating transaction data. The claim is not that Van Rossem itself makes Cardano process a radically higher number of transactions per second. It does not. The claim is that version 11 adds ledger and governance machinery needed on the road to that later change.
That distinction is not pedantry. A chain can be technically prepared for a scaling upgrade without receiving its throughput. It can activate the scaling upgrade without generating sustained demand. And it can generate demand without producing profitable, durable applications. Each stage needs separate evidence.
Decrypt cited a target of 30 to 65 times current throughput, with an ambition to exceed 1,000 transactions per second. Those are future targets, not July 18 results. The relevant evidence later will be public test results, block propagation behavior, node resource requirements, failed transaction rates, fees under load and the extent to which smaller operators can remain competitive.
The risk is that higher throughput raises hardware, bandwidth or operational complexity enough to push block production toward better-capitalized operators. The upside is that Cardano can accommodate more activity without turning routine onchain actions into a fee auction. Both claims can be tested. Neither was settled by Van Rossem.
The new authority comes with a higher burden
For developers, Van Rossem means tracking the hard-fork governance action itself: a future fork must clear the DRep threshold, win constitutional committee approval and secure SPO consent, while at least 85% of active stake runs a compatible node release before ratification. That replaces the earlier Input Output-led model, in which the company coordinated the upgrade path; it can now supply the code and case for change, but cannot activate a network-wide rule without those separate onchain mandates and operator readiness.
For operators, the responsibility is sharper. Running a node no longer means merely adopting a centrally coordinated technical release. Operators are voters in the upgrade path and deployers after the vote. Their role carries both power and accountability.
For ADA holders, delegation becomes more than a staking decision. Choosing a DRep is a choice about who will assess protocol changes on their behalf. The useful question is not whether a representative votes yes often. It is whether the representative explains the trade-offs before voting.
Van Rossem did not prove that Cardano governance will be quick, harmonious or correct. It proved something narrower and more valuable: the network can move version 10 to version 11 through its own formal constitutional process, while keeping ordinary transactions running.
The next fact that would change the reading is simple: whether the first contentious, economically meaningful protocol change can clear this same path without a founder-led rescue or an operator revolt.
Daniel Freedman writes about the Cardano ecosystem as it is used: the DeFi protocols, the stablecoins, the exchanges and the markets for ADA. He compares Cardano's numbers with other chains without sentiment either way, and says what would change his mind.
This article was written with the assistance of an AI system and published automatically.