IO: Hydra
196 DReps voted · 58 with a rationale · 4 changed their vote
Open a row to read the rationale.
- YesRevoted279.8K ₳History
Earlier votes
Yes1mo agoSuperseded
Yes1mo agoSuperseded
- YesRevoted271.8K ₳History
Earlier votes
Yes1mo agoSuperseded
- Yes270.1K ₳Rationale
I am voting YES on “IO: Hydra” because Hydra is already running production workloads on Cardano and this proposal funds the performance, operational, ecosystem, and maintenance work needed to harden Hydra v2 into a practical scaling layer for high-performance applications that L1 cannot currently serve well. Given Hydra’s existing usage and the range of teams already building on it, I view it as strategically important infrastructure for Cardano’s competitive scaling roadmap.
The proposal is milestone-gated, uses independent third-party assurance, and relies on the standard TRSC/PSSC framework with auto-abstain delegation and explicit refund conditions for unused funds, which fits the governance and custody guardrails I’ve been applying across 2026. My main reservations are the still high-level budget breakdown and the reliance on Intersect-administered off-chain contracts and metadata for detailed milestone and cost information rather than publishing more granular figures in the proposal itself. On balance, given Hydra’s existing adoption, IO’s track record on this protocol, and its importance to Cardano’s scaling story, I am supporting this tranche and will be watching for concrete, observable results over the coming year to inform my stance on any future Hydra-related funding requests.
- No261K ₳Rationale
Review Methodology Disclaimer [EN]
Due not only to the unusually high volume of Treasury Withdrawal Governance Actions and budget proposals submitted in April and May 2026, but also to the lack of meaningful incentives for DReps to perform proposal analysis work, it is not feasible to apply my full standard review framework and reporting template to every proposal.
My standard analysis process usually requires approximately four hours of work per Governance Action. During that process, I research the proposal, review supporting materials, compare different perspectives from DReps and other ecosystem participants, and weigh both positive and negative arguments before reaching a reasonably qualified decision. Even with the use of artificial intelligence to automate parts of the workflow and improve productivity, a responsible evaluation still requires substantial human review, judgment, and contextual understanding.
In addition, this work does not end with the vote itself. It also involves writing and publishing rationales, preparing reports or summaries, communicating the reasoning publicly, and socializing the analysis through public channels and social media. This creates a significant workload, especially when dozens of proposals must be reviewed in a short period.
At present, this work carries no clear financial incentive and only limited reputational incentive, despite requiring substantial time, attention, and accountability. In practice, it is not sustainable to dedicate near full-time effort over several weeks or months to this activity without any form of compensation or institutional support.
Since I have a clear standard for my work and do not want to lower the quality of my judgment, I will reduce the scope of my analysis where necessary rather than rush decisions or produce superficial rationales. This means prioritizing focused due diligence over exhaustive review.
Under these constraints, my methodology during this period will focus on identifying critical strategic, operational, governance, reputational, or execution-related risks that could materially compromise a proposal’s viability, accountability, or successful delivery. In practical terms, this means narrowing my research toward the most critical gaps that may make approval unjustifiable. Where such a serious risk is identified, I may use it as the basis for a rejection vote.
This approach also helps reduce review overload: proposals with clear and material gaps would likely require rework regardless, so voting against them when those gaps are significant can be a responsible way to preserve review capacity while maintaining minimum due diligence.
Examples of such high-priority concerns may include, but are not limited to:
- Serious delivery failures in previous funded proposals;
- Significant unresolved delays in ongoing work;
- Major reputational or accountability issues within the ecosystem;
- Lack of credible execution capacity;
- Structural governance or transparency concerns;
- Severe budgetary or coordination risks.
Where I do not have sufficient time for a deeper evaluation, and no significant red flags or imminent execution risks are identified, I may abstain rather than issue an underdeveloped approval or rejection rationale.
This does not mean that other dimensions of proposal quality are unimportant. It means that, under current constraints, I will prioritize a narrower but still responsible review scope that preserves minimum due diligence, avoids rushed decisions, and keeps the quality of my judgment at an acceptable standard.
Governance Action Report
1. Introduction
This Treasury Withdrawal governance action requests ₳5,100,781 to fund Hydra v2 hardening and production readiness. Hydra is Cardano’s Layer 2 state-channel protocol, intended to allow participants to transact with sub-second finality and near-zero fees while settling final outcomes on Cardano L1. The action presents Hydra as the only production-grade Layer 2 currently running live workloads on Cardano, including Delta DeFi, Masumi, Hydra Doom, Glacier Drop, Intersect voting infrastructure, VTech Labs, Blockfrost, and Midgard.
The requested funding covers four workstreams: performance optimization, operational excellence, ecosystem support, and maintenance and developer experience. The performance workstream targets 2x to 10x improvements in snapshot signing and memory profile, together with on-chain contract optimization to reduce L1 fees. Operational work includes runbooks, easier node configuration, observability, logging, and TUI improvements. Ecosystem support includes production-user feature requests, hackathons, workshops, developer relations, and Hydra Alliance facilitation. Maintenance and DevX are scoped over Q3–Q4 2026.
The funding would be milestone-gated, administered through Intersect’s treasury governance process, supported by independent third-party assurance, and subject to refund conditions for undisbursed funds or reduced scope.
2. Governance Action Analysis
Positive aspects
The NO vote does not result from a rejection of Hydra as a technology, nor from a denial of the importance of scalability solutions for Cardano. Hydra can be relevant infrastructure for the ecosystem, especially for use cases that require lower latency, lower transaction costs, and greater operational capacity than the base layer can directly provide.
The proposal presents a technical expectation of performance improvement, including 2x to 10x gains in snapshot signing and memory profile. This is a positive point. Technical improvements are relevant.
Milestone gating, Intersect administration, third-party assurance, and refund conditions help reduce custody risk, non-delivery risk, and improper disbursement risk.
Hydra may deserve funding. Public funding, however, needs to come with a granular budget, clear targets, and a transparency standard compatible with the amount requested.
Negative aspects
A simplified evaluation framework is being applied, suitable for votes where there is not enough time or capacity for a complete analysis of all technical, financial, and operational aspects of the proposal. Even under this reduced framework, two bottlenecks are sufficient to justify a NO vote: lack of budget granularity and absence of KPIs with measurable targets.
The first and most concerning problem is the lack of budget granularity. The proposal requests a multimillion-ADA amount, but presents the budget in a broad, vague, and aggregated way. Most resources are concentrated in a generic development category, without sufficient detail on number of people involved, FTEs, seniority, hourly rates, estimated duration by role, split between internal team and contractors, cost per milestone, or assumptions used to reach the requested amount. This prevents a serious evaluation of proportionality, reasonableness, and spending efficiency.
This level of detail is especially important because the proposal is not being submitted by a small team without structure, but by the main company historically associated with Cardano’s technical development. Precisely because of that position, IO should present a higher transparency standard, not a lower one. In multimillion-ADA proposals, it is not enough to state that resources will be used for development, infrastructure, security, operations, or ecosystem support. It is necessary to demonstrate how the amount was calculated, who will be paid, for how long, in which roles, and with which associated deliverables.
The pattern observed in recent IO proposals also raises concern. Comparing different treasury withdrawals submitted in recent months indicates the use of a standardized budget structure, with similar percentage distributions across categories. This suggests that the budget may be presented more as a simplified template than as a specific estimate built from the real needs of each proposal. For small proposals, this would already be weak. For multimillion-ADA proposals, it is institutionally unacceptable.
The consequence is that DReps and delegators lack sufficient elements to evaluate whether the requested amount is fair. It is not possible to know whether the budget reflects a real engineering need, whether there is excessive padding, whether there is overlap with already funded work, whether the amounts are compatible with market standards, or whether a relevant part of the Treasury is being used to sustain IO’s recurring operational structure without the level of openness expected for public resources.
The point is not to presume bad faith. The point is that there is not enough data to properly evaluate the cost. In at least other proposals, there was some exposure of hourly rate or reference to FTE equivalent. In this proposal, that minimum level of information does not appear. Without this information, it is not possible to evaluate whether personnel costs are reasonable, above or below international benchmarks, reflective of the complexity of the work, or compatible with the economic reality of the ecosystem.
The second problem is the absence of KPIs with clear targets. The proposal mentions alignment with KPIs such as TVL, monthly transactions, active users, throughput, uptime, reliability, and protocol revenue. However, these KPIs appear mainly as narrative alignment categories, not as measurable commitments. There are no clear minimum targets for TVL increase, number of transactions, active users, volume processed by Hydra, number of active integrations, revenue generated for L1, minimum uptime, or verifiable impact on real network usage.
The proposal presents technical expectations of performance improvement, which is positive, but insufficient to resolve the absence of ecosystem-impact targets. Technical improvements are relevant, but a Treasury withdrawal should also explain which observable results would justify public spending after delivery. Without targets, the ecosystem is left only with a general promise that Hydra may contribute to adoption, usage, TVL, revenue, and scalability.
This is a recurring problem in large proposals: there is a strong strategic narrative, but few objective commitments. The proposal states that Hydra can help keep applications on Cardano, attract builders, increase activity, and generate indirect revenue for L1. These possibilities may be true, but they are not sufficient as accountability. For a multimillion-ADA proposal, there should be minimum impact targets, even if adjusted to the stage of the technology. Without this, it becomes difficult to distinguish verifiable success from narrative progress.
The combination of these two problems is decisive. A proposal may have a budget with limited granularity but partially compensate with strong and verifiable impact targets. It may also have immature KPIs but present an extremely transparent and well-justified budget. Here, both sides fail at the same time: the cost is not sufficiently detailed and the expected impact is not sufficiently bound by measurable targets.
Risks and concerns
The current context makes the budget problem more serious. ADA is devalued, several ecosystem projects face difficulties or close operations, and the Treasury needs to be handled with discipline. In this environment, approving multimillion-ADA withdrawals with generic budgets sends a poor signal: small projects and dApps are frequently asked for details, deliverables, and justifications, while large suppliers can access much larger amounts with broad budget descriptions. This creates an accountability asymmetry that should not be normalized.
It is also concerning that ecosystem actors, including dReps do not press more strongly for budget transparency from large suppliers. The technical importance of infrastructure should not reduce the scrutiny standard. On the contrary, the more central the infrastructure and the larger the supplier, the higher the level of public scrutiny should be. Cardano should not accept most Treasury resources being consumed by a few recurring executors without granularity proportional to the amount requested.
Milestone gating, Intersect administration, third-party assurance, and refund conditions do not resolve the budget problem. These mechanisms help reduce custody risk, non-delivery risk, and improper disbursement risk. But they do not replace budget justification before approval. A milestone audit can verify whether something was delivered, but it does not answer whether the approved price was adequate from the start. The Treasury needs execution control, but it also needs cost control.
The central issue is not whether Hydra is important. The issue is whether this governance action presents an acceptable standard for Treasury use. It does not. The strategic relevance of the technology should not be used as a shortcut to reduce the transparency standard required of a multimillion-ADA withdrawal. If Cardano accepts this standard for large suppliers, it tends to repeat. As occurred in 2025, there is a risk that 2026 reproduces a dynamic in which large budget blocks are approved with low granularity, while the community remains without strong mechanisms for comparison, prioritization, and cost control.
Approving proposals of this size based only on institutional trust in IO is not adequate. Cardano’s on-chain governance exists precisely so that Treasury decisions are evaluated with responsibility, transparency, and accountability. Trust can be a contextual factor, but it does not replace detailed budgets, verifiable targets, and clear impact commitments. If the main company in the ecosystem requests public resources, it should demonstrate the best accountability standard, not ask the ecosystem to accept a simplified budget because the technology is important.
A NO vote may be interpreted by some as opposition to Hydra or scalability. That interpretation would be incorrect. The vote is against the structure of this specific withdrawal, not against Cardano’s need for technical evolution.
3. Vote and Rationale
Vote: NO.
The NO vote follows from two sufficient bottlenecks: lack of budget granularity and absence of KPIs with measurable targets. The vote does not reject Hydra as a technology and does not deny the importance of scalability for Cardano. A Treasury withdrawal must be evaluated as an institutional decision to allocate Cardano public resources, not merely as a generic statement of support for an important technology.
The requested amount is multimillion-ADA, while the budget remains broad, aggregated, and concentrated in a generic development category without enough detail on FTEs, rates, seniority, role duration, internal versus contractor allocation, milestone cost, or calculation assumptions. This prevents an adequate evaluation of cost proportionality and spending efficiency.
The proposal also lacks clear KPI targets. Alignment with TVL, transactions, active users, throughput, uptime, reliability, and protocol revenue is presented mainly as narrative alignment, not as measurable commitment. Technical performance improvements are positive, but they do not substitute for observable ecosystem-impact targets.
The decisive issue is the combination of weak financial granularity and absence of objective impact commitments. Even recognizing Hydra’s potential importance for Cardano’s scalability and competitiveness, it is not acceptable to approve a multimillion-ADA proposal with an excessively aggregated budget and KPIs without measurable targets.
Funding could be acceptable if accompanied by a granular budget, clear targets, and a transparency standard compatible with the amount requested.
4. Conclusion
The decision rests on the structure of this specific Treasury withdrawal. Hydra may be important and may deserve funding, but this request does not meet the minimum standard required for support. Low financial granularity and lack of measurable impact commitments make the proposed use of public Treasury resources unacceptable.
Nota sobre metodologia e escopo de análise [PT]
Devido não apenas ao volume excepcionalmente alto de Treasury Withdrawal Governance Actions e propostas orçamentárias submetidas em abril e maio de 2026, mas também à falta de incentivos significativos para que DReps realizem o trabalho de análise de propostas, não é viável aplicar meu framework completo de revisão e meu template padrão de relatório a todas as propostas.
Meu processo padrão de análise normalmente exige aproximadamente quatro horas de trabalho por Governance Action. Durante esse processo, eu pesquiso a proposta, reviso materiais de suporte, comparo diferentes perspectivas de DReps e de outros participantes do ecossistema, e peso argumentos positivos e negativos antes de chegar a uma decisão razoavelmente qualificada. Mesmo com o uso de inteligência artificial para automatizar partes do fluxo de trabalho e aumentar a produtividade, uma avaliação responsável ainda exige revisão humana substancial, julgamento e entendimento contextual.
Além disso, esse trabalho não termina no voto em si. Ele também envolve escrever e publicar rationales, preparar relatórios ou resumos, comunicar publicamente a justificativa e socializar a análise por meio de canais públicos e mídias sociais. Isso cria uma carga de trabalho significativa, especialmente quando dezenas de propostas precisam ser avaliadas em um curto período.
Atualmente, esse trabalho não possui incentivo financeiro claro e oferece apenas incentivo reputacional limitado, apesar de exigir tempo, atenção e responsabilidade substanciais. Na prática, não é sustentável dedicar um esforço próximo de tempo integral durante várias semanas ou meses a essa atividade sem qualquer forma de compensação ou apoio institucional.
Como tenho um padrão claro para o meu trabalho e não quero reduzir a qualidade do meu julgamento, irei reduzir o escopo da minha análise quando necessário, em vez de tomar decisões apressadas ou produzir justificativas superficiais. Isso significa priorizar uma diligência focada em vez de uma revisão exaustiva.
Sob essas restrições, minha metodologia durante este período se concentrará em identificar riscos críticos estratégicos, operacionais, de governança, reputacionais ou relacionados à execução que possam comprometer materialmente a viabilidade, a accountability ou a entrega bem-sucedida de uma proposta. Na prática, isso significa concentrar minha pesquisa nos gaps mais críticos que possam tornar a aprovação injustificável. Quando um risco sério desse tipo for identificado, poderei usá-lo como base para um voto de rejeição.
Essa abordagem também ajuda a reduzir a sobrecarga de revisão: propostas com gaps claros e materiais provavelmente exigiriam retrabalho de qualquer forma, então votar contra elas quando esses gaps forem significativos pode ser uma forma responsável de preservar capacidade de análise enquanto se mantém uma diligência mínima.
Exemplos dessas preocupações de alta prioridade podem incluir, mas não se limitam a:
- Falhas graves de entrega em propostas anteriormente financiadas;
- Atrasos significativos e não resolvidos em trabalhos em andamento;
- Problemas graves de reputação ou accountability dentro do ecossistema;
- Falta de capacidade crível de execução;
- Preocupações estruturais de governança ou transparência;
- Riscos severos de orçamento ou coordenação.
Quando eu não tiver tempo suficiente para uma avaliação mais profunda, e nenhum alerta significativo ou risco iminente de execução for identificado, poderei me abster em vez de emitir uma justificativa de aprovação ou rejeição pouco desenvolvida.
Isso não significa que outras dimensões da qualidade de uma proposta não sejam importantes. Significa que, sob as restrições atuais, priorizarei um escopo de revisão mais estreito, mas ainda responsável, que preserve uma diligência mínima, evite decisões apressadas e mantenha a qualidade do meu jul
- Yes260.2K ₳No rationale
- Yes245.5K ₳Rationale
The ₳5,100,781 ask is small and milestone-gated, covering performance optimization (targeting 2-10x improvements in snapshot signing and memory), node operability and observability, ecosystem support, and maintenance. The work improves a system that current production users depend on, and for a reasonable price that is conscious of the current market conditions and weak Ada value.
- Yes238.8K ₳Rationale
I typically vote No on treasury withdrawals to protect the shrinking runway (~1.51–1.62B ADA left, with the 350M NCL risking a ~21% drawdown). However, this Hydra proposal is a clear exception. Hydra is Cardano’s flagship Layer 2 solution and one of the most important pieces for real scalability and adoption. Strong L2 support will drive significantly higher transaction volume, which directly increases protocol fees and brings meaningful long-term revenue back into the treasury. Unlike many general infrastructure asks, this directly addresses a core bottleneck (throughput and low-cost execution) while positioning Cardano for revenue-generating use cases. Given Hydra’s proven progress and its potential to multiply on-chain activity, I’m supporting this targeted investment.
- Yes234.2K ₳No rationale
- Yes233.2K ₳No rationale
- Yes232.7K ₳No rationale
- Yes215.5K ₳No rationale
- Yes207.6K ₳No rationale
- Yes200.5K ₳No rationale
- Yes198.3K ₳No rationale
- Yes191.1K ₳No rationale
- Yes182.4K ₳No rationale
- Yes182.2K ₳No rationale
- Yes178.9K ₳No rationale
- Yes171.1K ₳No rationale
- Yes142.5K ₳No rationale
- Yes131.9K ₳No rationale
- Yes129.1K ₳No rationale
- Yes107.2K ₳No rationale
- Yes92.6K ₳Rationale
I voted YES because Hydra is critical scaling infrastructure for Cardano.
Cardano needs more than just a secure Layer 1 if it wants to compete for high-performance use cases like DeFi, gaming, AI agent payments, micropayments, point-of-sale, and institutional applications. Hydra helps solve major issues around speed, transaction cost, and user experience by enabling sub-second finality, near-zero fees, and higher throughput while still settling back to Cardano L1.
This proposal supports production hardening, performance improvements, operational tools, developer experience, and ecosystem support for Hydra v2. That matters because real projects are already building on or evaluating Hydra, and Cardano needs to keep those builders instead of losing them to faster competing ecosystems.
I also support the milestone-gated structure, third-party assurance, and oversight through Intersect. The funding ask is significant, but if properly managed and delivered, this is the type of infrastructure investment that can grow Cardano’s utility, transaction activity, TVL, developer adoption, and long-term competitiveness.
For those reasons, I voted YES.
- Yes79.9K ₳No rationale
- Yes72.1K ₳No rationale
- Yes71.3K ₳Rationale
YES. I support continued investment in Hydra due to its strategic importance and current level of maturity. I expect future milestones to include measurable minimum KPI commitments and transparent public reporting to ensure accountability to the community.
- Yes69.4K ₳No rationale
- Yes64.4K ₳No rationale
- Yes59.8K ₳No rationale
- Yes55.9K ₳No rationale
- No50.5K ₳No rationale
- Abstain45.2K ₳No rationale
- Yes29.3K ₳No rationale
- Yes15.5K ₳No rationale
- No15.3K ₳No rationale
- Abstain10.8K ₳No rationale
- Yes10.7K ₳No rationale
- Yes8.1K ₳No rationale
- No6.7K ₳No rationale
- Yes4.8K ₳No rationale
- Yes2K ₳No rationale
- Yes682 ₳No rationale
- Yes11.9 ₳No rationale
- No0 ₳No rationale
- Yes0 ₳No rationale