Hard Fork to Protocol Version 11 ('van Rossem' Hard Fork)
190 DReps voted · 47 with a rationale · 5 changed their vote
Open a row to read the rationale.
- Yes320.4K ₳No rationale
- Yes313.4K ₳No rationale
- Yes298.9K ₳Rationale
What is there to say other than YES?
- Yes294.4K ₳No rationale
- Yes285.3K ₳No rationale
- Yes279.8K ₳No rationale
- Yes271.8K ₳No rationale
- Yes270.1K ₳Rationale
I am voting YES on “Hard Fork to Protocol Version 11 (‘van Rossem’ Hard Fork)” because it is a focused intra‑era protocol upgrade that improves Plutus performance and capabilities, strengthens ledger correctness, and enhances node diagnostics, while keeping the ledger in the Conway era and preserving transaction shape. The action adds useful new Plutus built‑ins, unifies built‑in availability across Plutus versions, and introduces case expressions in UPLC, which together reduce execution cost and extend what builders can do on‑chain.
It also enforces VRF key hash uniqueness, clarifies reference input rules, promotes the Constitutional Committee voting restriction into a formal ledger predicate, and improves PPView mismatch reporting, all of which contribute to more robust and transparent consensus and governance behavior. The hard fork is contingent on at least 85% of active stake pools upgrading to a compatible node and has been recommended by Intersect’s Hard Fork Working Group and Technical Steering Committee, which satisfies my requirements around readiness and technical review for protocol changes.
- AbstainChanged261K ₳Rationale
Governance Action Report [EN]
1. Introduction
This governance action proposes upgrading Cardano Mainnet to Protocol Version 11 through an intra-era hard fork named “van Rossem.” The ledger remains in the Conway era, with no era transition, while the protocol moves from Major Version 10 to Major Version 11 and Minor Version 0. The upgrade introduces new Plutus primitives defined in CIP-0109, CIP-0132, CIP-0133, CIP-0138, and CIP-0153, makes all Plutus built-in functions consistently available across Plutus V1, V2, and V3, and adds case expressions for built-in types in Untyped Plutus Core.
The action also includes ledger and node-level changes: VRF key hash uniqueness enforcement at the ledger level, revised reference input rules for Plutus V1/V2, promotion of the Constitutional Committee voting restriction from a mempool-only check to a ledger predicate, clearer validation of non-matching withdrawals, and improved reporting for protocol parameter hash mismatches. At least 85% of stake pools by active stake should have upgraded to a node version capable of supporting Protocol Version 11 before ratification, with readiness reports from Intersect’s Hard Fork Working Group supporting verification by the Constitutional Committee and SPOs.
2. Governance Action Analysis
Positive aspects
The governance action was recommended by the Hard Fork Working Group, endorsed by the Technical Steering Committee, and accompanied by claims of tests, audits, and benchmarks without regressions.
No NO vote or strong technical objection indicating imminent risk or a clear basis for rejection was identified in the reviewed DREP rationales.
The abstentions found appear to reflect mainly an institutional position of deference to SPOs and infrastructure operators, who are more directly exposed to the operational risk of hard fork activation.
Risks and concerns
The governance action concerns a deep technical upgrade of the Cardano protocol, involving an intra-era hard fork, new Plutus primitives, changes to ledger rules, node behavior, cost model requirements, and operational readiness of the network.
A complete independent evaluation would require substantially greater technical capacity and time than were available for this analysis.
3. Vote and Rationale
Vote: ABSTAIN
The most responsible position for Agora is ABSTAIN. The governance action concerns a deep technical upgrade of the Cardano protocol, involving an intra-era hard fork, new Plutus primitives, changes to ledger rules, node behavior, cost model requirements, and operational readiness of the network.
Although the proposal was recommended by the Hard Fork Working Group, endorsed by the Technical Steering Committee, and accompanied by claims of tests, audits, and benchmarks without regressions, a complete independent evaluation would require substantially greater technical capacity and time than were available for this analysis.
No NO vote or strong technical objection indicating imminent risk or a clear basis for rejection was identified in the reviewed rationales. The abstentions found appear to reflect mainly an institutional position of deference to SPOs and infrastructure operators, who are more directly exposed to the operational risk of hard fork activation.
The abstention does not express opposition to the upgrade. It expresses recognition of the limits of a dRep’s technical competence in the face of a highly specialized decision, while respecting the role of SPOs, the Hard Fork Working Group, the Technical Steering Committee, and the Constitutional Committee in validating the network’s technical and operational readiness.
4. Conclusion
The position is ABSTAIN because the action is highly technical, no clear basis for rejection was identified, and the validation of readiness depends on actors more directly equipped to assess operational and protocol-level risk. The abstention reflects institutional restraint, not opposition to the upgrade.
Relatório de Ação de Governança [PT]
1. Introdução
Esta ação de governança propõe atualizar a Mainnet da Cardano para a Versão de Protocolo 11 por meio de um hard fork intra-era chamado “van Rossem”. O ledger permanece na era Conway, sem transição de era, enquanto o protocolo passa da Versão Maior 10 para a Versão Maior 11 e Versão Menor 0. A atualização introduz novos primitivos Plutus definidos nas CIP-0109, CIP-0132, CIP-0133, CIP-0138 e CIP-0153, torna todas as funções built-in de Plutus disponíveis de forma consistente em Plutus V1, V2 e V3, e adiciona expressões case para tipos built-in em Untyped Plutus Core.
A ação também inclui mudanças no ledger e no node: aplicação da unicidade do hash da chave VRF no nível do ledger, revisão das regras de reference inputs para Plutus V1/V2, promoção da restrição de voto do Comitê Constitucional de uma checagem apenas de mempool para um predicado de ledger, validação mais clara de non-matching withdrawals e melhoria nos relatórios de divergências de hash de parâmetros de protocolo. Pelo menos 85% dos stake pools por stake ativo devem ter atualizado para uma versão do node capaz de suportar a Versão de Protocolo 11 antes da ratificação, com relatórios de prontidão da Hard Fork Working Group da Intersect apoiando a verificação pela Constitutional Committee e pelos SPOs.
2. Análise da Ação de Governança
Aspectos positivos
A governance action foi recomendada pela Hard Fork Working Group, endossada pelo Technical Steering Committee e acompanhada de alegações de testes, auditorias e benchmarks sem regressões.
Não foi identificado, nos racionales revisados, nenhum voto NO ou objeção técnica forte que indique risco iminente ou fundamento claro para rejeição.
As abstenções encontradas parecem refletir principalmente uma posição institucional de deferência aos SPOs e operadores de infraestrutura, que estão mais diretamente expostos ao risco operacional de ativação do hard fork.
Riscos e preocupações
A governance action trata de uma atualização técnica profunda do protocolo Cardano, envolvendo hard fork intra-era, novos primitivos Plutus, mudanças em regras de ledger, node behavior, requisitos de cost model e prontidão operacional da rede.
Uma avaliação independente completa exigiria capacidade técnica e tempo substancialmente maiores do que os disponíveis para esta análise.
3. Voto e Racional
Voto: ABSTAIN
A posição mais responsável para Agora é ABSTAIN. A governance action trata de uma atualização técnica profunda do protocolo Cardano, envolvendo hard fork intra-era, novos primitivos Plutus, mudanças em regras de ledger, node behavior, requisitos de cost model e prontidão operacional da rede.
Embora a proposta tenha sido recomendada pela Hard Fork Working Group, endossada pelo Technical Steering Committee e acompanhada de alegações de testes, auditorias e benchmarks sem regressões, uma avaliação independente completa exigiria capacidade técnica e tempo substancialmente maiores do que os disponíveis para esta análise.
Não foi identificado, nos racionales revisados, nenhum voto NO ou objeção técnica forte que indique risco iminente ou fundamento claro para rejeição. As abstenções encontradas parecem refletir principalmente uma posição institucional de deferência aos SPOs e operadores de infraestrutura, que estão mais diretamente expostos ao risco operacional de ativação do hard fork.
Portanto, a abstenção não expressa oposição ao upgrade. Expressa reconhecimento dos limites de competência técnica de um dRep diante de uma decisão altamente especializada, ao mesmo tempo em que respeita o papel dos SPOs, da Hard Fork Working Group, do Technical Steering Committee e da Constitutional Committee na validação da prontidão técnica e operacional da rede.
4. Conclusão
A posição é ABSTAIN porque a ação é altamente técnica, nenhum fundamento claro para rejeição foi identificado, e a validação da prontidão depende de atores mais diretamente capacitados para avaliar riscos operacionais e de protocolo. A abstenção reflete contenção institucional, não oposição ao upgrade.
Earlier votes
Yes15d agoSuperseded
Governance Action Review
- Yes260.2K ₳No rationale
- Yes245.5K ₳Rationale
Cardano Protocol Version 11 delivers technical improvements including a Plutus cost model update for more accurate smart contract pricing, better ledger consistency, and stronger node-level security, while laying the groundwork for the upcoming Dijkstra era and eventual Leios scaling upgrade - all as a low-disruption intra-era change that avoids launching a new ledger era, minimizing impact on wallets, exchanges, and dApps.
- Yes234.2K ₳No rationale
- Yes233.2K ₳No rationale
- Yes232.7K ₳No rationale
- Yes215.5K ₳No rationale
- Yes191.1K ₳No rationale
- Yes182.4K ₳No rationale
- Yes182.2K ₳No rationale
- YesRevoted178.9K ₳History
Earlier votes
Yes1mo agoSuperseded
- Yes171.1K ₳No rationale
- Yes142.5K ₳No rationale
- Yes131.9K ₳No rationale
- Yes129.1K ₳No rationale
- Yes118.7K ₳Rationale
I am voting yes on the van Rossem Hard Fork because it delivers meaningful improvements to Cardano's performance, developer capabilities, ledger consistency, and security while minimizing disruption through an intra-era upgrade. The addition of new Plutus primitives, expanded cryptographic functionality, unified built-ins across Plutus versions, improved data handling, and stronger ledger-level validation rules strengthen Cardano's technical foundation and expand what developers can build on-chain. Importantly, these enhancements are paired with extensive testing, security review, and ecosystem readiness requirements to support a smooth transition.
I am also pleased to support a hard fork named in honor of Max van Rossem. Having served alongside Max during the Constitutional Convention in Buenos Aires, I witnessed firsthand his passion for Cardano, governance, and the long-term success of the ecosystem. He was thoughtful, engaged, and deeply committed to building something that would outlast any one individual. Naming this upgrade after Max is a fitting tribute to someone who dedicated so much of his time and energy to Cardano's future, and a reminder that our ecosystem is ultimately built by people willing to contribute, collaborate, and serve.
- Yes110.9K ₳No rationale
- Yes108.3K ₳Rationale
This is a needed upgrade to the chain and I support this fork.
- Yes107.2K ₳No rationale
- Yes92.6K ₳No rationale
- Yes72.1K ₳No rationale
- Yes71.3K ₳No rationale
- Yes67.1K ₳No rationale
- Yes55.9K ₳No rationale
- No50.5K ₳No rationale
- Yes45.2K ₳No rationale
- Yes31.7K ₳No rationale
- Yes10.8K ₳No rationale
- Yes8.1K ₳No rationale
- Yes6.7K ₳No rationale
- Yes682 ₳No rationale
- Yes0 ₳No rationale