Input Output, the development company behind the Cardano blockchain, is transferring control of its core components — including the Haskell node, the Plutus smart contract platform, and the Hydra scaling solution — to outside teams. Founder Charles Hoskinson has said the network needs to change and start growing again, signaling a major shift in how the project's technical infrastructure is managed.
What's being handed over
The move covers some of the most critical pieces of Cardano's technology stack. The Haskell node is the reference implementation that runs the network. Plutus is the programming language and platform used to build smart contracts on Cardano. Hydra is the layer-2 scaling protocol designed to increase transaction throughput. By handing these off, Input Output is effectively decentralizing the development and maintenance of its core software.
It's not just these three. The company said it will also transfer control of other components, though it didn't name all of them. The goal is to reduce Input Output's role as the central gatekeeper of Cardano's codebase.
Why the change now
Hoskinson has been vocal about the need for Cardano to evolve. The network has faced criticism for slow development timelines and a lack of real-world adoption compared to rivals like Ethereum. In a recent statement, he said the network must change and start growing again. The handover is the clearest sign yet that Input Output is serious about letting go of the reins.
The company has long promoted a vision of decentralized governance for Cardano. But until now, most of the core development has remained under Input Output's direct control. This transfer is a concrete step toward that vision — though it also raises questions about who will step up to maintain the code and whether the outside teams have the resources and expertise to do so.
Who's taking over
Input Output did not name the specific teams that will assume control of the Haskell node, Plutus, and Hydra. The company said only that the components will be transferred to "outside teams." That could include independent developer groups, community-run organizations, or other entities already involved in the Cardano ecosystem. The lack of named recipients means the transition is still taking shape, and details are likely to emerge in the coming weeks.
The move is part of a broader push to decentralize Cardano's development. The network already has a formal on-chain governance system, introduced in the Chang hard fork, but the software side has lagged behind. This transfer aims to close that gap.
What happens next
Input Output hasn't set a public deadline for the full handover. The transition is expected to happen gradually, with the outside teams taking over maintenance and future development of each component. For now, the company will continue to support the network, but its role will shrink over time.
One unresolved question: how will the outside teams coordinate their work? Cardano's core software is complex, and the Haskell node, Plutus, and Hydra are deeply interconnected. Without a central coordinator, there's a risk of fragmentation. But that's the trade-off Input Output is making — betting that a looser, more distributed structure will ultimately help Cardano grow faster than it has under the company's sole stewardship.
