Cardano decentralization—IOG hands core code to outside teams
Cardano decentralization advances as Input Output hands its Haskell node, Plutus and Hydra to outside teams—testing if the network survives without founder.
In Brief
- Input Output will hand control of Cardano’s Haskell node, Plutus, Daedalus and Hydra to outside teams starting in August, with the transfer running into 2027.
- The move spins the Haskell node out to community curation, testing whether a network can run without the company that wrote it.
- Se7en Labs and Teragone take responsibility for some components, while Intersect and Pragma oversee formal specifications subject to community voting.
Input Output is giving away the keys to Cardano. The company that wrote the blockchain’s software is handing core development to outside teams, betting that “decentralization” means more than a slogan.
The transition begins in August and stretches into 2027, covering the Haskell node, the Plutus smart-contract platform, the Daedalus wallet, the Hydra scaling layer and developer relations, according to CoinDesk. Input Output said the shift is the next phase of Cardano’s long-promised Voltaire-era handoff.
Cardano already moved protocol governance to its community. Now the question is whether independent shops can maintain the code without the founder’s lab steering every release.
Cardano decentralization reaches the codebase
The headline change is the Haskell node, the reference implementation almost every Cardano user depends on. Input Output said IO Labs is spinning that node out to “community curation and control,” the final stage of what founder Charles Hoskinson calls the Voltaire era.
Exactly which team owns which piece is not fully spelled out. CoinDesk reported that Se7en Labs—a firm known for Solana infrastructure—and Teragone, which already leads the Mithril signature protocol, will take responsibility for “some of the components.” Intersect and Pragma are tasked with formal specifications, with development open to community review and voting.
Hoskinson, who argued this year that AI agents will reshape the open internet, framed the handover as overdue. Per Input Output, he said the ecosystem “now has many diverse options” and that the network had stopped expanding without specialized teams setting targets.
Why the handoff matters now
Cardano is not handing off from a position of strength. The network holds about $70 million in total value locked, a fraction of the $4 billion-plus on rivals like Tron and Solana, CoinDesk reported. The wider market is also tightening—the UK recently proposed caps on crypto ETN holdings in funds.
The timing doubles as a survival move. Hoskinson acknowledged the network’s “growing pains” in a video, warning that “failures have to occur to build confidence in the system.” Input Output will refocus on research and new ventures through IO Labs and IO Ventures, keeping the science but shedding day-to-day maintenance.
The experiment’s verdict will come from the code itself. If independent teams keep three separate implementations—in Haskell, Rust and Go—running without coordination breakdowns, Cardano’s decentralization claim gets its first real proof; Input Output said the arrangement is designed to reduce reliance on a single company that built the chain.
FAQ
What is Cardano’s core development handoff?
Input Output is transferring control of Cardano’s Haskell node, Plutus smart-contract platform, Daedalus wallet and Hydra scaling layer to outside teams, starting in August and continuing into 2027, per CoinDesk.
Why is Cardano decentralizing its codebase now?
The network trails rivals on activity, with roughly $70 million in TVL against more than $4 billion on chains like Tron and Solana. Input Output said shifting maintenance to independent teams reduces dependence on the company that built the chain.
Which teams take over Cardano development?
Se7en Labs and Teragone will own some components, while Intersect and Pragma oversee formal specifications under community review. The Haskell node moves to community curation via IO Labs, though exact team assignments were not fully detailed.