IO: Hydra
196 DReps voted · 60 with a rationale · 1 changed their vote · 3 re-voted unchanged
Open a row to read the rationale.
Changed votes: 1 to yes, together voting with 923.1K ₳ of voting power.
- Yes1.5M ₳No rationale
- Yes1.4M ₳No rationale
- Yes1.4M ₳No rationale
- Yes1.4M ₳No rationale
- Yes1.3M ₳No rationale
- Yes1.3M ₳No rationale
- Yes1.2M ₳Rationale
I vote YES on IO: Hydra because Hydra is critical Cardano scaling infrastructure with real production use and a clear path to improving finality, fees, throughput, and developer adoption. I recognize concerns around the size of the ask and the need for better budget transparency from major ecosystem vendors, but in this case I give the proposal the benefit of the doubt because Hydra is one of the few Layer 2 systems already supporting live Cardano workloads. The milestone-gated funding, independent assurance, and Intersect administration make the treasury risk more acceptable. I expect public reporting on benchmarks, active integrations, reliability, usage, and the long-term maintenance path so future support can be judged on evidence, not trust alone.
- Yes1.2M ₳No rationale
- No1.2M ₳No rationale
- Yes1.1M ₳No rationale
- Yes1.1M ₳Rationale
Cardano's L1 faces issues like slow finality, high fees, and bottlenecks hindering adoption in DeFi, gaming, and micropayments. Hydra’s Layer 2 solution offers sub-second finality and L1-grade security, expanding the ecosystem without draining L1 liquidity.
However, ₳5M is a substantial request. While the proposal outlines milestone gating and oversight, it lacks detailed risk mitigation and deliverables. The budget leans heavily on development, but ecosystem support is crucial for Hydra's mainstream success. The governance framework is robust, but the community needs regular progress updates to avoid past issues of delays.
While Hydra addresses the scaling trilemma effectively, it's not a complete solution. Upcoming L1 upgrades will enhance performance, but Hydra is vital for high-throughput use cases. Alternatives compromise security, underscoring Hydra’s necessity. Execution and builder adoption will dictate whether this investment leads to real growth.
I am cautiously optimistic about whether funding will boost adoption without straining IO’s resources or duplicating efforts. If managed well, Hydra could be Cardano's advantage in scaling, but mismanagement could harm community trust and treasury stability. Discipline and tangible results are essential for Hydra's strategic success.
- Yes987.4K ₳No rationale
- Yes984.8K ₳No rationale
- Yes966.3K ₳No rationale
- Yes951.2K ₳No rationale
- Yes929.9K ₳Rationale
We vote YES on this proposal because Hydra is the most important Layer 2 technology currently available in the Cardano ecosystem and a critical building block for real-world adoption.
Cardano needs a scalable execution layer that can support fast, low-cost and high-throughput applications while still settling back to Cardano L1. Hydra can provide sub-second finality, near-zero fees and strong settlement guarantees, which are essential for use cases such as DeFi, micropayments, AI agent commerce, gaming, point-of-sale systems and other applications that need to interact with the real world.
We also see strong value in the projects already mentioned in the proposal. Delta DeFi, Masumi, Blockfrost, Intersect voting infrastructure and other Hydra-based initiatives show that this is not only theoretical research, but infrastructure with real users, real experimentation and meaningful application potential.
In our view, supporting Hydra is a strategic investment into Cardano’s ability to compete as a high-performance blockchain ecosystem. We need this technology as a practical bridge between Cardano’s secure base layer and real-world applications.
- Yes927.7K ₳No rationale
- YesChanged926K ₳History
Earlier votes
No2mo agoSuperseded
- Yes920.9K ₳No rationale
- Yes884.5K ₳No rationale
- Yes870.3K ₳No rationale
- Yes866.3K ₳No rationale
- Yes829.9K ₳Rationale
As a representative committed to safeguarding user trust, decentralization, and the long-term scalability of Cardano, a YES vote is the objectively sound decision for the network's architectural development. Mainnet transaction velocity and dApp competitiveness rely directly on robust Layer 2 throughput. Hydra represents a peer-reviewed, structurally secure mechanism to handle web-scale throughput while keeping transaction costs low and accessible.
The financial request of ₳5.1M is highly disciplined, well-aligned with the Intersect 2026 Budget Framework, and does not threaten or breach our active Constitutional Net Change Limit (NCL) boundaries. Allowing core scaling progress to stall would negatively affect ecosystem retention and infrastructure maturity during a pivotal market phase.
Latin American Ecosystem Impact Statement:
This governance action directly empowers the Latin American Cardano community by lowering the economic barriers to entry. For builders and users in regions characterized by volatile local economies, low-fee micro-transactions via localized Hydra heads make real-world web3 adoption, localized dApp development, and remittance pilots financially viable, effectively driving socio-economic inclusion across LatAm. - Yes796.1K ₳No rationale
- Yes792.3K ₳No rationale
- Yes737.8K ₳No rationale
- Yes622K ₳No rationale
- Yes604.7K ₳Rationale
Voting YES. Unbundling resolved the prior objection. Hydra is Cardano's only production L2 with real users, Delta DeFi, Masumi agent commerce, both solving the pre-selection problem. Concerns on milestones and scope are covered in oversight, not a blockers to approval.
A PDF version of this rationale is also made available.
I vote yes. The community's rejection of the bundled Hydra+Midgard proposal was the right call, and IO's response, with the unbundling and resubmitting Hydra on its own merits, is equally the right outcome. The structural objection is resolved. What remains is a focused hardening proposal for Cardano's only production-grade L2, backed by live users who depend on the improvements being requested.
The core case I voted YES on in the combined proposal hasn't changed. Cardano has a pre-selection problem: L1 finality measured in hours and fees measured in fractions of a dollar degrades Cardano’s competitiveness before builders ever reach its genuine advantages. Hydra addresses this with live production proof, Delta DeFi has staked its entire perpetual DEX product on Hydra, Masumi is running live agent-to-agent commerce at sub-second finality, and the Midnight Glacier Drop validated the infrastructure at genuine scale. These are not demonstrations or proofs of concept; they are real businesses that would need to migrate to competing chains if this hardening doesn't happen.
The Masumi case in particular remains the clearest expression of why Hydra funding serves Cardano's long-term position. TradFi like Citi projects hundreds of billions in agent-driven transaction value by 2030. Circle launched Nanopayments on testnet in March 2026 specifically for this market with a centralized, custodial, USDC-only, payment-only solution. Masumi on Hydra is a full programmable commerce layer: escrow, dispute resolution, continuous micropayments, with Plutus contracts, completely non-custodial and on any asset. That's a differentiated position, a unique value proposition and it runs today. Declining to fund the infrastructure those builders depend on hands that position to a competitor with centralized alternatives.
The open concerns I carry into this, the milestone opacity, the wide performance target range, the missing personnel breakdown, and the question of whether this is a one-time hardening or the first installment of an ongoing maintenance baseline, can belong in the oversight and reporting process, not as blockers to this governance action. IO's track record, the production evidence, and the focused scope of this resubmission all clear the bar, making it better and leaner. - Yes591.1K ₳Rationale
IO proposes something to benefit Cardano: I vote yes
- Yes582.9K ₳No rationale
- Yes579.1K ₳No rationale
- Yes573.2K ₳No rationale
- Yes568K ₳Rationale
Push Hydra forward. With Cardano's scale comes real utility. Security and decentralization were the right things to focus on to begin with and continue to be. But Scalability is in sight and should get pushed through fast.
- Yes481.2K ₳No rationale
- Yes466.2K ₳No rationale
- Yes438.6K ₳No rationale
- Yes435.4K ₳No rationale
- Yes433.2K ₳No rationale
- Yes393.6K ₳No rationale
- No379.5K ₳No rationale
- Yes366.6K ₳No rationale
- Yes356.1K ₳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.
- No342.8K ₳No rationale
- Yes330.6K ₳No rationale
- Yes321.6K ₳No rationale
- Abstain318.1K ₳Rationale
Abstaining, as I’m part of the Cardano Constitution Committee Tingvard.
Reading proposals and staying updated, just like you.
Thanks to all fellow DReps who are also doing the hard work.
Follow and DM me on X: @kenerik if you have any questions. - Yes297K ₳Rationale
Voting YES on IO: Hydra
Summary
IO is requesting just over ₳5M to fund four workstreams focused on taking Hydra to the next level.
Conclusion
This is an easy YES for me. In the Cardano ecosystem, nobody has a better track record than IO. Hydra allows Cardano to swallow the world. The core advantage is unlimited scalability while keeping everything compatible with the Cardano ledger. The same smart contract running on Cardano can be run on Hydra. I'm looking forward to seeing Hydra reach its full potential.
Signed,
William DoyleYour friendly neighbourhood DRep!
$computerman
drep1yfpgzfymq...pzw3nt
@william00000010 on 𝕏
contact@williamdoyle.ca - No285.2K ₳No rationale
- YesRevoted280.5K ₳History
Earlier votes
Yes2mo agoSuperseded
Yes3mo agoSuperseded
- Yes275.2K ₳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.