Skip to main content

Hydra development moves to BlockPQR

Cover image for Hydra decentralization move

Key points

  • Hydra development is moving from IO Labs to BlockPQR on December 1, 2026, extending Cardano's network of specialist engineering partners.
  • BlockPQR already works on Cardano's ledger and core infrastructure. That experience is relevant to Hydra, which reuses Cardano transaction formats and ledger validation off-chain.
  • Hydra heads let a group of participants transact among themselves, with funds ultimately settled on Cardano.
  • Hydra 2.4.2 includes improvements to transaction batching, partial fanout, and recovery, alongside a Windows build of hydra-node.
  • The move follows earlier transitions to Teragone, ICAN Group, and Serokell with more of Cardano's engineering based in independent organizations.

Hydra lets a group of people make repeated transactions without sending each one through Cardano's main chain. For someone building a game or a payment application, that opens up a different way to handle the activity between participants while still settling funds on Cardano.

Hydra development is moving from Input Output (IO) Labs to BlockPQR on December 1, 2026. The connection is unusually direct: BlockPQR already works on Cardano's ledger, and Hydra uses that ledger's transaction formats and validation off-chain. The move brings those related areas of engineering into the same organization.

Why the ledger connection matters

Inside a Hydra head, a group of participants transacts using familiar Cardano formats and validation rules. The head has its own parameters and limitations, so developers still need to understand how their application will behave there. They can use Cardano's transaction model while processing frequent activity, such as moves in a game or payments between participants, off-chain.

When participants close a head, they begin a process that allows time to contest an outdated state. The resulting outputs are then distributed on Cardano. That route back to the main chain is part of the protocol's design.

For the engineers, the connection runs through the code: the ledger defines which transactions are valid and how state changes; Hydra uses that validation inside each head. Working within one specialist organization gives the teams more scope to address the boundary between the two.

BlockPQR brings experience with Cardano's ledger and blockchain indexer, alongside formal methods and high-availability engineering. Its engineers have worked on proof-of-stake systems from research through to production, including the tools operators use to run them. That background is relevant whenever Hydra developers need to reason about a participant disconnecting, a process restarting, or funds returning to the main chain.

The team's method starts with a specification and a model of how the system should behave. Engineers test the implementation against that model, using formal proofs where appropriate and testing and measurement elsewhere. Those habits matter for software that handles people's funds, as well as for the performance work that tends to get more attention.

What builders can use today

Hydra 2.4.2, released on October 22, includes larger snapshot batches to improve throughput and faster partial fanout. There's also a Windows build of hydra-node. The release fixes deposit handling and snapshot consistency, along with recovery from network stalls and restarts.

Some of these changes help an application handle more activity; others make the software easier to run or recover. Both affect whether Hydra fits something a developer intends to put in front of users. Transaction speed alone doesn't answer that question.

A developer evaluating Hydra needs to know how it runs day to day. The public repository offers that detail: release notes explain compatibility and upgrade requirements, and issues and pull requests show the work under discussion. Alongside the documentation, they give builders a way to assess the software against their own application, including what happens when they need to recover from a failure.

A growing network of engineering partners

Hydra joins a program that has already seen Mithril move to Teragone, engineering functions move to ICAN Group, and core protocol work move to BlockPQR. These independent organizations work alongside IO Labs, with Intersect coordinating across the partner network. For Hydra, the choice of partner puts its development close to the ledger expertise the protocol draws on.

Explore the Hydra documentation and public repository to see how heads work and follow development. You can also learn more about IO Labs and the specialist partners working on Cardano.

Related articles

radial blurry background

Evolving the future

Where the world sees broken systems, we see opportunity. Input Output Group was created to rebuild trust with science, purpose, and scale. Our mission has never been about chasing short-term wins. From the beginning, it has been about designing systems that endure.

radial image